I've been doing a lot of customizing on my new Devuan machine from the root account. When I tried to switch users to my unprivileged account I was unable to login because of a DCOP: | There was an error setting up inter-process communications for TDE. The message returned by the system was: | | Could not read network connection list. | /home/leslie/.DCOPserver_palomino__1 | | Please check that the "dcopserver" program is running! ps aux|grep -i dcop shows |root 15175 0.0 0.1 49316 10244 ? S 04:42 0:00 dcopserver [tdeinit] --nosid --suicide I also see that root has .DCOPserver_<HOST>__0 and a symlink, .DCOPserver_<HOST>_:0 pointing to it; these are missing in account leslie. Is there a way to recover from this, or do I have to recreate the account?
Leslie -- Operating System: Linux Distribution: openSUSE Leap 15.4 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.12 tde-config: 1.0
Anno domini 2022 Wed, 14 Sep 18:18:25 -0500 J Leslie Turriff scripsit:
I've been doing a lot of customizing on my new Devuan machine from the root account. When I tried to switch users to my unprivileged account I was unable to login because of a DCOP: | There was an error setting up inter-process communications for TDE. The message returned by the system was: | | Could not read network connection list. | /home/leslie/.DCOPserver_palomino__1 | | Please check that the "dcopserver" program is running! ps aux|grep -i dcop shows |root 15175 0.0 0.1 49316 10244 ? S 04:42 0:00 dcopserver [tdeinit] --nosid --suicide I also see that root has .DCOPserver_<HOST>__0 and a symlink, .DCOPserver_<HOST>_:0 pointing to it; these are missing in account leslie. Is there a way to recover from this, or do I have to recreate the account?
# service tde stop # killall dcopserver # <--- just in case it survived # chown leslie:leslie ~leslie -R # service tde start
And don't do this - use tdm to start yout tde session:
# su leslie $ startde
Nik
Leslie
Operating System: Linux Distribution: openSUSE Leap 15.4 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.12 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 ...
On 2022-09-15 04:10:47 Dr. Nikolaus Klepp wrote:
# service tde stop # killall dcopserver # <--- just in case it survived # chown leslie:leslie ~leslie -R # service tde start
And don't do this - use tdm to start yout tde session:
# su leslie $ startde
Nik
This doesn't seem to have fixed it; I still get the same error message and failure during login. I should have said, the message appears twice: once after entering username and password, with 'DCOP communications error (kdetcompmgr)' in the message title bar, then again while the splash menu progress starts (stuck at 'Setting up interprocess communication') where the message title bar says, 'DCOP communications error (The TDE Session Manager)'. I didn't notice the message title bar info before.
Leslie
On Wednesday 14 September 2022 06:18:25 pm J Leslie Turriff wrote:
I also see that root has .DCOPserver_<HOST>__0 and a symlink, .DCOPserver_<HOST>_:0 pointing to it; these are missing in account leslie. Is there a way to recover from this, or do I have to recreate the account?
Did you try creating a test/temp account to see if it does the same thing there?
If test/temp works, I'd just recreate the leslie account?
HTH, Michael
PS: Do backups first ;)
On 2022-09-15 09:09:53 Michael wrote:
Did you try creating a test/temp account to see if it does the same thing there?
Yes, I just created such an account, and it works.
If test/temp works, I'd just recreate the leslie account?
Looks like that's the only solution. Fortunately, the only data to recover is the configuration of TDE itself in the account; a niusance, but hardly a disaster.
HTH, Michael
Leslie --