Very soon after I started to use the TDE 14.0.11 version I began receiving DCOP error messages, having the effect of preventing use of various applications like Firefox and LibreOffice. After online research and experimentation on my part I discovered that I could solve such preventions if before opening TDE I ran in a tty as root the following three commands: 'dcopserver -- serverid', which returned nothing, then 'dropserver' and finally again 'dcopserver -- serverid'. This time however that command returned something like the following: '[dcopserver] local/Morcom:/tmp/.ICE-unix/dcop5698-1636014592'
From this point on there were no longer any more DCOP error messages. I
had full use of the TDE and various applications until when I next closed completely the computer.
It is consequently my understanding that running the 'dcopserver' command is presumably required as part of the initial boot-up. If such is usually the case I would appreciate knowing what I need to do to have my computer, named Morcom, do so as well. Can anyone tell me?
Regards, Ken
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Sat, 13 Nov 2021 21:05:47 +0700 Ken Heard kenslists@teksavvy.com wrote:
First things first: Please switch to the new mailing list. This one has been deprecated and could shut down at any time.
It is consequently my understanding that running the 'dcopserver' command is presumably required as part of the initial boot-up. If such is usually the case I would appreciate knowing what I need to do to have my computer, named Morcom, do so as well. Can anyone tell me?
Normally, the starttde script calls tdeinit, which then forks off a dcopserver instance. I believe this should happen when a TDE XSession is loaded. Apparently some part of this chain isn't working properly on your machine.
What's your distro? Are there any errors in your X logs?
E. Liddell
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 2021/11/14 12:36 AM, E. Liddell wrote:
On Sat, 13 Nov 2021 21:05:47 +0700 Ken Heard kenslists@teksavvy.com wrote:
First things first: Please switch to the new mailing list. This one has been deprecated and could shut down at any time.
It is consequently my understanding that running the 'dcopserver' command is presumably required as part of the initial boot-up. If such is usually the case I would appreciate knowing what I need to do to have my computer, named Morcom, do so as well. Can anyone tell me?
Normally, the starttde script calls tdeinit, which then forks off a dcopserver instance. I believe this should happen when a TDE XSession is loaded. Apparently some part of this chain isn't working properly on your machine.
What's your distro? Are there any errors in your X logs?
E. Liddell
And are you running a full TDE session or try to run apps inside another DE?
Cheers Michele
I have a preliminary answer to your questions.
On 2021-11-14 2:23 p.m., Michele Calgaro via tde-users wrote:
On 2021/11/14 12:36 AM, E. Liddell wrote:
On Sat, 13 Nov 2021 21:05:47 +0700 Ken Heard kenslists@teksavvy.com wrote:
First things first: Please switch to the new mailing list. This one has been deprecated and could shut down at any time.
Yes indeed first things first. Thank you for the heads up on the mailing list; I now am using trinity-users instead of tde-users.
<snip>
What's your distro?
Debian Bullseye, original installation in a new computer, not an upgrade. I did not install any of the DEs available from Debian.
Are there any errors in your X logs?
Not sure yet but I am working on it.
And are you running a full TDE session or try to run apps inside another DE?
Yes for the full Trinity Desktop Environment. There is no other OS or DE in the machine.
I am learning much from my researches which may or may not have positive results. Stay tuned.
Regards, Ken
On 2021-11-13 10:36 p.m., E. Liddell wrote:
On Sat, 13 Nov 2021 21:05:47 +0700 Ken Heard kenslists@teksavvy.com wrote:
It is consequently my understanding that running the 'dcopserver' command is presumably required as part of the initial boot-up. If such is usually the case I would appreciate knowing what I need to do to have my computer, named Morcom, do so as well.
After major surgery I am now well enough to answer emails to me about some of the difficulties I encountered with TDE 14.0.11. My original installation of TDE on 2021-10-05 had to use Slávik’s ‘unofficial’ preliminary stable build, version R14.0.11, the only TDE one available then for Debian Bullseye. By the way this was a full TDE session; it was not run from inside another desktop environment.
Very soon after the installation I frequently had to reboot because of problems with dcopserver. After considerable experimentation I found that the best way to solve them was right after each boot to open my user in tty1. I then ran command ‘dcopserver –serverid’; no response was received. Next I ran ‘dcopserver’ first alone and then again as ‘dcopserver –serverid’. This time I received confirmation that dcopserver had an ID Bullseye and quoted it. It was at this point that on 2021-11-13 I raised this issue on the Trinity user list.
Sometime after, but I am not sure exactly when, I discovered that some of the other minor irritants in TDE which I discovered since I started using it had disappeared. It consequently occurred to me to check to see whether the dcopserver irritant disappeared as well. It had. After checking various upgrades since 2021-10-05 I confirmed on 2021-11-12 that the TDE version for the preliminary stable build changed from R14.0.11 to R14.0.12 [DEVELOPMENT].
From that point on I no longer had to to do at every boot the procedure
described in the second paragraph. I don’t know what exactly was changed and how, but whatever it was it worked. I also noticed that the time stamp for two DCOPserver entries in my home directory are the date and time of the latest boot. It does seem however that on closing the computer these entries are deleted and then reopened when the computer is next opened.
Regards and Merry Christmas, Ken Heard
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi Ken, apologies from replying from the web interface HyperKitty.... and for duplicating a response given also to another user (Andre').
This issues should now be solved and since you wrote in your post you are using preliminary stable build, it would be good if you could test and report. The update is on tdelibs.
Cheers Michele
-
E. Liddell -
Ken Heard -
Ken Heard
-
Michele Calgaro -
michele.calgaro＠yahoo.it