Hi all!
I jus ran into an interesting problem when running inside VirtualBox: I created a installation that works perfectly fine. Then I created a live iso from this installation using refractasnapshot. Booting that iso seads to two instances of dcopserver beeing started --> mouse an keyboard are non operational. When I remove ~/.DCOP* and then "killall dcopserver" then Xorg testarts and I end with a perfectly working TDE.
So, does anybody have any idea what causes dcopseerver to spawn twice? Or better said, why $TDEDIR/bin/dcopserver_shutdown in starttde does leave a running dcopserver instance?
Nik
-- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Dr. Nikolaus Klepp via tde-users wrote:
I jus ran into an interesting problem when running inside VirtualBox: I created a installation that works perfectly fine. Then I created a live iso from this installation using refractasnapshot. Booting that iso seads to two instances of dcopserver beeing started --> mouse an keyboard are non operational. When I remove ~/.DCOP* and then "killall dcopserver" then Xorg testarts and I end with a perfectly working TDE.
I have also two instances - the one is started by root and the other by the user.
Anno domini 2024 Thu, 25 Jan 09:15:00 +0100 deloptes via tde-users scripsit:
Dr. Nikolaus Klepp via tde-users wrote:
I jus ran into an interesting problem when running inside VirtualBox: I created a installation that works perfectly fine. Then I created a live iso from this installation using refractasnapshot. Booting that iso seads to two instances of dcopserver beeing started --> mouse an keyboard are non operational. When I remove ~/.DCOP* and then "killall dcopserver" then Xorg testarts and I end with a perfectly working TDE.
I have also two instances - the one is started by root and the other by the user.
Interesting. I have only one for my user - exept when things don't work, then I have two for my user.
-- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Dr. Nikolaus Klepp via tde-users wrote:
I have also two instances - the one is started by root and the other by the user.
Interesting. I have only one for my user - exept when things don't work, then I have two for my user.
may be it is so because I did xhost +local:0 recently to run something as root
Anno domini 2024 Fri, 26 Jan 00:49:15 +0100 deloptes via tde-users scripsit:
may be it is so because I did xhost +local:0 recently to run something as root
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?
Nik
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
-- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Dr. Nikolaus Klepp via tde-users wrote:
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
Anno domini 2024 Sat, 27 Jan 00:37:40 +0100 deloptes via tde-users scripsit:
Dr. Nikolaus Klepp via tde-users wrote:
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).
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
BR
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
-- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Dr. Nikolaus Klepp via tde-users wrote:
.. 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.
And did you try to remove them? I mean logout remove then and login?
Also is not 0 the local DISPLAY?
Very strange indeed
Here it says $ export | grep DISPL declare -x DISPLAY=":0"
I don't know, but if it is VBox, that you are using, what is the situation with the display - perhaps it is worth checking something using :0 and TDE spawns a new one.
Anno domini 2024 Sat, 27 Jan 22:24:35 +0100 deloptes via tde-users scripsit:
Dr. Nikolaus Klepp via tde-users wrote:
.. 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.
And did you try to remove them? I mean logout remove then and login?
I can remove them (I put them on the not-to-be-included-list for refractasnapshop, too), but they get recreated when the two dcopserver-instances start. Sometimes (1/10) I get ine instance and everything works fine, so it's not 100% deterministic.
Also is not 0 the local DISPLAY?
Very strange indeed
Here it says $ export | grep DISPL declare -x DISPLAY=":0"
I don't think they have anything to do with the display variable. The number increases with each onstance of dcopserver.
I don't know, but if it is VBox, that you are using, what is the situation with the display - perhaps it is worth checking something using :0 and TDE spawns a new one.
TDE is running iside the guest, but that's isolated. And it's running on the host, too, but they don't see each other.
Nik
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
-- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
On 2024-27-01 16:55:34 Dr. Nikolaus Klepp via tde-users wrote:
Anno domini 2024 Sat, 27 Jan 22:24:35 +0100
deloptes via tde-users scripsit:
Dr. Nikolaus Klepp via tde-users wrote:
.. 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.
And did you try to remove them? I mean logout remove then and login?
I can remove them (I put them on the not-to-be-included-list for refractasnapshop, too), but they get recreated when the two dcopserver-instances start. Sometimes (1/10) I get ine instance and everything works fine, so it's not 100% deterministic.
Also is not 0 the local DISPLAY?
Very strange indeed
Here it says $ export | grep DISPL declare -x DISPLAY=":0"
I don't think they have anything to do with the display variable. The number increases with each onstance of dcopserver.
I don't know, but if it is VBox, that you are using, what is the situation with the display - perhaps it is worth checking something using :0 and TDE spawns a new one.
TDE is running iside the guest, but that's isolated. And it's running on the host, too, but they don't see each other.
Nik
I have had this problem off and on (mostly on) for a long time (see my prior posts about DCOP usage), but never had a resolution. I am not running any VMs, so I think that is a red herring.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.4 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.1 tde-config: 1.0
Anno domini 2024 Tue, 30 Jan 12:16:47 -0600 Leslie Turriff via tde-users scripsit:
I don't know, but if it is VBox, that you are using, what is the situation with the display - perhaps it is worth checking something using :0 and TDE spawns a new one.
TDE is running iside the guest, but that's isolated. And it's running on the host, too, but they don't see each other.
Nik
I have had this problem off and on (mostly on) for a long time (see my prior posts about DCOP usage), but never had a resolution. I am not running any VMs, so I think that is a red herring.
Here it's only happening inside the VM Guest when it's booting a live iso - so quite mysterious. Unfortunately I did not succeed with further investigation.
Nik
Leslie
Platform: Linux Distribution: openSUSE Leap 15.4 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.1 tde-config: 1.0
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
-- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
-
deloptes -
Dr. Nikolaus Klepp -
Leslie Turriff