8 Aug
2023
8 Aug
'23
10:05 a.m.
On Tuesday 08 August 2023 11:47:22 you wrote:
(1) Which user(s) have dcopservers running ("ps
uax | grep '[d]cop'")?
(2) Do they have any files open below /tmp/ (see "lsof -p pid")?
(3) What are the owners and permissions of those files and all their
parent directories?
(4) What are the mount options of all relevant filesystems (probably
just /)?
(5) This says you are using Bookworm. Which version
of TDE please?
(6) Are you able to run things from command line? Menu?
(7) Is the problem with icons on the desktop? Elsewhere?
(8) Are you starting TDE normally via tdm?
(9) Do you have any other window managers or desktops installed?
(10) Can you provide an example of a .desktop which fails in this way?
(11) What happened with the "Impossible to boot on trinity" issue?
Hello,
1) andre 885 0.0 0.3 41948 9964 ? S 11:34 0:00 dcopserver
[tdeinit] --nosid --suicide
(what means "suicide" ?)
2) lsof -p pid
lsof: illegal process ID: pid
3) The good owners permission
4) filesystems = / and /home/
5) The last version of TDE.
6) If message dcopserver, I cannot open a terminal
7) Yes, icon on the desktop
8) Yes, starting normally with tdm
9) lightdm, and XFCE desktop
10) No problem with XFCE
11) It was another subject, resolved, with a complete reinstallation of
Bookworm.
The error message "tdelauncher dcoperver " comes from the directory :
"/run/user/1000/ICEauthority" rights rw, if the owner of this file becomes
root:root. It must be "andre:andre".
If I change it, the error message disappears.
Thanks, cheers.
Andre
8 Aug
8 Aug
10:10 a.m.
New subject: tdelauncher DCOPserver, again
My sources.list :
deb http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.1.x bookworm
main deps
# Optional sources
deb-src http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.1.x
bookworm main deps
Andre
10:42 a.m.
New subject: tdelauncher DCOPserver, again
I have two pid, andre and root :
ps aux|grep dcop
andre 885 0.0 0.3 41948 9964 ? S 11:34 0:00 dcopserver
[tdeinit] --nosid --suicide
root 1964 0.0 0.2 41620 8452 ? S 11:59 0:00 dcopserver
[tdeinit] --nosid --suicide
11:27 a.m.
New subject: tdelauncher DCOPserver, again
On Tue, 8 Aug 2023 12:05:36 +0200
ajh-valmer-free via tde-users <users(a)trinitydesktop.org> wrote:
1) andre 885 0.0 0.3 41948 9964 ? S 11:34 0:00
dcopserver
[tdeinit] --nosid --suicide
(what means "suicide" ?)
From https://manpages.org/dcopserver :
"--suicide
Tell dcopserver to automatically terminate if no transactions are made within 10
seconds. "
It's normal for that flag to be present. My instance also has it.
E. Liddell
3:56 p.m.
New subject: tdelauncher DCOPserver, again
On Tue August 8 2023 03:05:36 ajh-valmer-free via tde-users wrote:
The error message "tdelauncher dcoperver "
comes from the directory :
"/run/user/1000/ICEauthority" rights rw, if the owner of this file becomes
root:root. It must be "andre:andre".
If I change it, the error message disappears.
Hi André,
It looks like you have tracked the problem to a point where
I cannot help you much. Only a root process can change an
andre-owned directory to root-owned. TDM and X may be running
as root but all of TDE proper should be running as andre unless
and until you deliberately start something as root such as a
root konsole.
I would try to figure out whether the directory is created with
the correct owner and/or what is changing it. That's probably
not going to be easy. A couple of tricks which may or may not
help:
(1) After the directory is in a good state "chattr +i ..." it
and see if anything later complains when it tries to change
the owner. Be sure to undo this later or it may create more
problems.
(2) Create a little script to run in a loop in a konsole to
check the directory every second and alert you when the
ownership has changed.
--Mike
9:18 p.m.
New subject: tdelauncher DCOPserver, again
On Tuesday 08 August 2023 17:56:45 Mike Bird via tde-users wrote:
When an issue is resolved it is helpful to post that
fact to the thread
so that (1) people don't spend time trying to think of solutions for
you and (2) people who experience the same problem can try your solution :
Sorry for that, just after the new installation I have the problem
of "tdelauncher DCOPserver", so much work to find this sad result,
that seemed resolved since a long time.
If you obtain different results on successive installs
of the same
software to the same disks you may have a disk problem.
Hi André,
It looks like you have tracked the problem to a point where
I cannot help you much. Only a root process can change an
andre-owned directory to root-owned. TDM and X may be running
as root but all of TDE proper should be running as andre unless
and until you deliberately start something as root such as a
root konsole.
I would try to figure out whether the directory is created with
the correct owner and/or what is changing it. That's probably
not going to be easy. A couple of tricks which may or may not help:
(1) After the directory is in a good state "chattr +i ..." it
and see if anything later complains when it tries to change
the owner. Be sure to undo this later or it may create more
problems.
(2) Create a little script to run in a loop in a konsole to
check the directory every second and alert you when the
ownership has changed :
Change the owner of
"/run/user/1000/ICEauthorithy" now doesn't resolve the
message "Can't communicate with TDElauncher via DCOP".
On my 3 computers, small laptop, 2 computers on Debian-12,
everything works fine, and not on my recent Lenovo laptop.
It appears after 3 minutes after the TDM boot.
I don't know what to do to repair, do Slavek can help me...
Cheers,
André
9:55 p.m.
New subject: tdelauncher DCOPserver, again
On Tuesday 08 August 2023 21:18:54 ajh-valmer via tde-users wrote:
Change the owner of "/run/user/1000/ICEauthorithy" now doesn't resolve the
message "Can't communicate with TDElauncher via DCOP".
On my 3 computers, small laptop, 2 computers on Debian-12,
everything works fine, and not on my recent Lenovo laptop.
It appears after 3 minutes after the TDM boot.
I don't know what to do to repair, do Slavek can help me...
Cheers,
Andr�
Ah ha. I got that message, but it was a long long time ago, and I cannot
recall exactly how I got round it. It seems to me that it had something to do
with dmrc. I will look through my notes to see if I kept anything on this
matter.
Just out of curiosity, do you enable root password in Debian? If it is a
machine for a single user, I just enable shadow passwords, but do not create
a root password, as that is just a headache for a single user.
Something in your description reminds me of what I went through a few years
back, when I first switched from the 'Buntus to a Debian system. And since
then I have moved on to Devuan. Likewise the Lenovo laptop. For me, it helped
to enable legacy boot, but UEFI first, and to disable secure boot, as that
seems to be designed to prevent a successful installation of Linux.
Bill
10:15 p.m.
New subject: tdelauncher DCOPserver, again
Anno domini 2023 Tue, 8 Aug 21:55:31 +0000
William Morder via tde-users scripsit:
On Tuesday 08 August 2023 21:18:54 ajh-valmer via tde-users wrote:
I get the error when I did a stupid thing like this:
- su and then run a program as tde program as root
- kill the tde program, end root session
- log out and forget about everything
Next time I log into tde dcop dies. I need to do a "chown myusername ~myusername
-R" as root, then reboot - that usually settles things. BTW, what does this give on
your system?
$ mount|grep run
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=2448668k,mode=755,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
tmpfs on /run/user/1000 type tmpfs
(rw,nosuid,nodev,relatime,size=2448664k,nr_inodes=612166,mode=700,uid=1000,gid=1000,inode64)
Nik
Change the owner of "/run/user/1000/ICEauthorithy" now doesn't resolve the
message "Can't communicate with TDElauncher via DCOP".
On my 3 computers, small laptop, 2 computers on Debian-12,
everything works fine, and not on my recent Lenovo laptop.
It appears after 3 minutes after the TDM boot.
I don't know what to do to repair, do Slavek can help me...
Cheers,
Andr�
Ah ha. I got that message, but it was a long long time ago, and I cannot
recall exactly how I got round it. It seems to me that it had something to do
with dmrc. I will look through my notes to see if I kept anything on this
matter. Just out of curiosity, do you enable root password in
Debian? If it is a
machine for a single user, I just enable shadow passwords, but do not create
a root password, as that is just a headache for a single user.
Something in your description reminds me of what I went through a few years
back, when I first switched from the 'Buntus to a Debian system. And since
then I have moved on to Devuan. Likewise the Lenovo laptop. For me, it helped
to enable legacy boot, but UEFI first, and to disable secure boot, as that
seems to be designed to prevent a successful installation of Linux.
Bill
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
9 Aug
9 Aug
9:14 a.m.
New subject: tdelauncher DCOPserver, again
On Tuesday 08 August 2023 23:55:31 William Morder via tde-users wrote:
On Tuesday 08 August 2023 21:18:54 ajh-valmer via
tde-users wrote:
> Change the owner of "/run/user/1000/ICEauthorithy" now doesn't resolve
the
> message "Can't communicate with TDElauncher via DCOP".
> On my 3 computers, small laptop, 2 computers on Debian-12,
> everything works fine, and not on my recent Lenovo laptop.
> It appears after 3 minutes after the TDM boot.
> I don't know what to do to repair, do Slavek can help me...
Ah ha. I got that message, but it was a long long time
ago, and I cannot
recall exactly how I got round it. It seems to me that it had something to
do with dmrc. I will look through my notes to see if I kept anything on this
matter :
Hello William,
Can you tell me where is the file ".dmrc" :
/home/<user> ?
In "/run/user/1000", there is this a strange directory :
d????????? ? ? ? ? ? doc
It's impossible do delete it.
Just out of curiosity, do you enable root password in
Debian? If it is a
machine for a single user, I just enable shadow passwords, but do not create
a root password, as that is just a headache for a single user.
login in root with password with the system,
or login in root with tdm ?
André
1:01 p.m.
New subject: tdelauncher DCOPserver, again
On Wednesday 09 August 2023 09:14:07 ajh-valmer via tde-users wrote:
Others might advise you differently, but I would say that if you are the only
user on your machine, then to create a root user only makes it unnecessarily
hard for you to do many simple tasks. Just enable shadow passwords, but do
not create a root password when installing Debian or Devuan or one of their
variant distros. You will save yourself a lot of grief.
There may be other factors that affect how you decide; not only whether there
are other users on your machine, but also if you work in an environment where
you worry about other people getting into your machine, or having your
machine stolen, and so on.
Things keep changing, though, and we can all better, more secure habits.
Bill
On Tuesday 08 August 2023 23:55:31 William Morder via
tde-users wrote:
It could be that I mean .tdmrc, but I seem to remember .dmrc,
which I believe
might be a clue to the source of the problem.
On Tuesday 08 August 2023 21:18:54 ajh-valmer via
tde-users wrote:
Hello William,
Can you tell me where is the file ".dmrc" :
/home/<user> ? Change the owner of
"/run/user/1000/ICEauthorithy" now doesn't resolve
the message "Can't communicate with TDElauncher via DCOP".
On my 3 computers, small laptop, 2 computers on Debian-12,
everything works fine, and not on my recent Lenovo laptop.
It appears after 3 minutes after the TDM boot.
I don't know what to do to repair, do Slavek can help me...
Ah ha. I got that message, but it was a long long time ago, and I cannot
recall exactly how I got round it. It seems to me that it had something
to do with dmrc. I will look through my notes to see if I kept anything
on this matter :
In "/run/user/1000", there is this a strange directory :
d????????? ? ? ? ? ? doc
It's impossible do delete it.
Something in what you write here reminds me of a bug we had a few years ago
(maybe 5 years ago or more?). I thought maybe it was that xdg-update problem
that many of us experienced back then, but I just did a search of the mailing
list archives, and cannot find anything that matches.
I must call on others to jump in here, if they remember. If I find out more, I
will post again. However, I believe that .dmrc is connected to that earlier
bug, something with xdg-update in the header.
Just out of curiosity, do you enable root
password in Debian? If it is a
machine for a single user, I just enable shadow passwords, but do not
create a root password, as that is just a headache for a single user.
login in root with password with the system,
or login in root with tdm ?
André
4:49 p.m.
New subject: tdelauncher DCOPserver, again
On Wednesday 09 August 2023 15:01:16 William Morder via tde-users wrote:
Others might advise you differently, but I would say
that if you are the
only user on your machine, then to create a root user only makes it
unnecessarily
hard for you to do many simple tasks. Just enable shadow passwords, but do
not create a root password when installing Debian or Devuan or one of their
variant distros. You will save yourself a lot of grief.
There may be other factors that affect how you decide; not only whether
there
are other users on your machine, but also if you work in an environment
where
you worry about other people getting into your machine, or having your
machine stolen, and so on.
Things keep changing, though, and we can all better, more secure habits.
Thank you William for your help.
If you remember what you did before or have an idea=welcome !
Now the message no longer appears,
"I cross the fingers" (french expression) to not have it again...
Cheers,
André
8 Aug
8 Aug
3:59 p.m.
New subject: tdelauncher DCOPserver, again
On Tue August 8 2023 03:05:36 ajh-valmer-free via tde-users wrote:
11) It was another subject, resolved, with a complete
reinstallation of
Bookworm.
When an issue is resolved it is helpful to post that fact to the thread
so that (1) people don't spend time trying to think of solutions for
you and (2) people who experience the same problem can try your solution.
If you obtain different results on successive installs of the same
software to the same disks you may have a disk problem.
--Mike
501
days inactive
502
days old
11 comments
6 participants
participants (6)
-
ajh-valmer -
ajh-valmer-free
-
Dr. Nikolaus Klepp -
E. Liddell -
Mike Bird -
William Morder