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:
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.
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
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