27 Jan
2024
27 Jan
'24
10:10 a.m.
Anno domini 2024 Sat, 27 Jan 00:37:40 +0100
deloptes via tde-users scripsit:
Dr. Nikolaus Klepp via tde-users wrote:
But you use a systemd based distribution, not sysv. As dcopserver leaves it's imprint
in the users home directory I wonder if it gets started for TDM for root and is left over
when your user session starts (that "seat" thingie).
I have a different situation: two instances of dcopserver are running, the
"footprint" in the users home directory is:
.DCOPserver_neo_:0 -> /home/nik/.DCOPserver_neo__0
.DCOPserver_neo__0
.DCOPserver_neo_:1 -> /home/nik/.DCOPserver_neo__1
.DCOPserver_neo__1
.. where the "0" links are created before the "1" links, but the
"0" dcopserver is nonresponsive till the "1" has finished it's
startup. twm talks to the "1", but mouse+keyboard talk to the "0"
--> everything works but mouse and keyboard - which is kind of bad.
Nik
Well, tdm is configured as autologon. When the
live image starts and tdm
starts it runs starttde in the user context which spawn 2 instances of
dcop. As this only happens in VirtualBox+live image (the "original" runs
inside of Virtualbox without live image and is working perfectly fine) I
meanwile suspect a side effect of VirtualBox ... but what causes it?
I see it on the PC, on the VBox and in VMWare. the parent is started by root
and the child is running as the logged in user. To me it looks like the
parent process is started by root, so that it can run the child process as
the logged in user (like sshd or apache2 or any other application that
needs spawning child as a common user)
I couldn't find the place in the code where it does that (under 3min).
BR
____________________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...