On Wednesday 22 December 2021 17:28:23 awaco@free.fr wrote:
On 2021/12/13 07:09 PM, ajh-valmer wrote:
Hello Michele, What does it mean, the messages above ? When I boot Bullseye, I'm in command-line mode (no Xorg, no graphic), invited to connect in root (and password). I have to type "killall tdm" to be connected on the trinity desktop. So, what to do to be directly on the trinity desktop ? André
Hi André, not sure of the details of the error message, would have to check them out. But it's the rest that caught my attention. Normally a TDE system should boot up and present you the tdm login screen. But you mentioned you are in command prompted and "invited" to login as root. Do you have some errors and a message asking you to provide the root password to login to rectify the issue or pressing Ctrl+D to continue ?
I have Ctrl+D to continue in recovery mode or type root passwd. Only one solution, type "killall tdm" to connect to tde-desktop.
If you see this message, give it a Ctrl+D first (without logging in) and see what happens and if you get the tdm login screen afterwards or not. Cheers Michele
Hi Michele, /var/log/tdm.log exists but empty. /var/log/tdm.1.log : "info: Cannot open master configuration file /etc/trinity/tdm/tdmdistrc". tdmdistrc doesn't exist in this folder. I can login to tde-desktop with lightdm, not with tdm-trinity. (even after a dpkg-reconfigure tdm-trinity).
Now I have a clear understanding what happens without to be able to repair. The file /run/user/1000/ICEauthority is : -rw------- 1 andre andre 205 22 déc. 17:18 ICEauthority It becomes automatically quickly : -rw------- 1 root root 205 22 déc. 17:18 ICEauthority, after I receive the error messages allready indicated, DCOPserver and /home/andre./.Xauthority not writable : -rw------- 1 andre andre 59 22 déc. 17:18 .Xauthority
It seems that there is a conflict between two users, root and andre. Thanks. Bye, cheers, André
On 2021/12/23 01:51 AM, ajh-valmer wrote:
"info: Cannot open master configuration file /etc/trinity/tdm/tdmdistrc".
Hi André, This is also weird. It should be "/etc/trinity/tdm/tdmrc" not, tdmdistrc. There is definitely something not quite right in your system setup. It may be worth doing a clean reinstall as we mentioned some days ago. Cheers Michele
On Thursday 23 of December 2021 03:28:47 Michele Calgaro via tde-users wrote:
On 2021/12/23 01:51 AM, ajh-valmer wrote:
"info: Cannot open master configuration file /etc/trinity/tdm/tdmdistrc".
Hi André, This is also weird. It should be "/etc/trinity/tdm/tdmrc" not, tdmdistrc. There is definitely something not quite right in your system setup. It may be worth doing a clean reinstall as we mentioned some days ago. Cheers Michele
Hi André, Michele, all,
the absence of tdmdistc is "okay". This is an optional file that can override default values in tdmrc specifically for distribution.
It is first needed to solve why tdm blocks the boot process on your system. This is not normal to block it and require a root password for an emergency console. You can find out some other information about the tdm process? Are there any information in syslog? Are there any information in the XOrg log file?
Cheers
On Thursday 23 December 2021 03:28:47 Michele Calgaro and Slavek wrote:
Hi André, This is also weird. It should be "/etc/trinity/tdm/tdmrc" not, tdmdistrc. There is definitely something not quite right in your system setup. It may be worth doing a clean reinstall as we mentioned some days ago. Michele
Hi André, Michele, all, the absence of tdmdistc is "okay". This is an optional file that can override default values in tdmrc specifically for distribution. It is first needed to solve why tdm blocks the boot process on your system. This is not normal to block it and require a root password for an emergency console. You can find out some other information about the tdm process? Are there any information in syslog? Are there any information in the XOrg log file?
Hello Michele and Slavek,
I made a complete new reinstallation of Bullseye 64 bits, excepted of course my home/. The problem seemed resolved.
But when I declared my home/ in fstab (sda3 ext4 partition), immediately exactly the same problem DCOP came back. Also, always this folder "/run/user/1000/" with these rights and impossible to delete it : d????? ????? ???? gvfs So, a virus, a bad file in my /home ?
Cheers, Happy Christmas !
André
On Friday 24 December 2021 13:45:25 ajh-valmer wrote:
Hello Michele and Slavek, I made a complete new reinstallation of Bullseye 64 bits, excepted of course my home/. The problem seemed resolved. But when I declared my home/ in fstab (sda3 ext4 partition), immediately exactly the same problem DCOP came back. Also, always this folder "/run/user/1000/" with these rights and impossible to delete it : d????? ????? ???? gvfs So, a virus, a bad file in my /home ?
New information : I reboot the system, with a new /home/ empty, I removed (purge) gvfs, deleted the folder /run/user/1000/gvfs/ and the message DCOP came back too with : /run/user/1000/ICEauthority : rw------- root.root ICEauthority, instead : /run/user/1000/ICEauthority : rw------- andre.andre ICEauthority
So, this problem does'nt comme from my /home, but from what ? Why the system puts /run/user/1000/ICEauthority : rw------- root.root ICEauthority ?
On this ML-list, I'm alone to get the message DCOP-server. Why me ? :-(
Cheers, André
On Friday 24 December 2021 09:27:10 am ajh-valmer wrote:
On Friday 24 December 2021 13:45:25 ajh-valmer wrote:
Hello Michele and Slavek, I made a complete new reinstallation of Bullseye 64 bits, excepted of course my home/. The problem seemed resolved. But when I declared my home/ in fstab (sda3 ext4 partition), immediately exactly the same problem DCOP came back. Also, always this folder "/run/user/1000/" with these rights and impossible to delete it : d????? ????? ???? gvfs So, a virus, a bad file in my /home ?
New information : I reboot the system, with a new /home/ empty, I removed (purge) gvfs, deleted the folder /run/user/1000/gvfs/ and the message DCOP came back too with : /run/user/1000/ICEauthority : rw------- root.root ICEauthority, instead : /run/user/1000/ICEauthority : rw------- andre.andre ICEauthority
So, this problem does'nt comme from my /home, but from what ? Why the system puts /run/user/1000/ICEauthority : rw------- root.root ICEauthority ?
On this ML-list, I'm alone to get the message DCOP-server. Why me ? :-(
Cheers, André ____________________________________________________
Hi André
Try downgrading (if you can) your ICE packages. That's what I did to resolve the same problem. There's a bug in the latest ICE that makes the DCOP error happen on some distros.
I hope this helps,
Kate
On Friday 24 December 2021 16:34:30 Borg Labs wrote:
Hi André Try downgrading (if you can) your ICE packages. That's what I did to resolve the same problem. There's a bug in the latest ICE that makes the DCOP error happen on some distros. I hope this helps, Kate
Hello Kate,
I hope too...
apt-cache search ICE or DCOP, doesn't give me the packages to reinstall. Can you give me the packages.
Happy Christmas day.
André
On Friday 24 December 2021 16:34:30 Borg Labs wrote:
Hi André Try downgrading (if you can) your ICE packages. That's what I did to resolve the same problem. There's a bug in the latest ICE that makes the DCOP error happen on some distros. I hope this helps, Kate
How did you do to find a downgraded version of ICE ?
Can you give me the operating mode.
Thanks, André
Hello Michele and Slavek,
I made a complete new reinstallation of Bullseye 64 bits, excepted of course my home/. The problem seemed resolved.
But when I declared my home/ in fstab (sda3 ext4 partition), immediately exactly the same problem DCOP came back. Also, always this folder "/run/user/1000/" with these rights and impossible to delete it : d????? ????? ???? gvfs So, a virus, a bad file in my /home ?
Cheers, Happy Christmas !
André
Hi André, first of all Merry Christmas to you and everyone on the ML. Based on what you mentioned above, I would proceed as follow:
1) since the basic installation is working fine, I would first create a new user and double check a TDE session works fine with that (you may have done this already)
2) after that, *without* copying over your home folder, I would create a new "andre" user (I believe that's the name of your user) with ID 1000. Make sure a TDE session works fine with that (it should because it is no difference from point 1.)
3) then I would progressively copy over some of your old home configuration, logout, reboot, login and check when things breaks again. Make sure to make a backup of the working new user home folder before any iteration, so you can easily repeat a test if necessary.
This process will take some time but should lead you to discover what in your existing config is causing the problem.
Cheers Michele
Hello, Best Year best wishes for everybody !
I made a complete reinstallation of Debian-Bullseye and tde-trinity.
Always this problem DCOP_SERVER when "/run/user/1000/" has this line : -rw------- 1 root root 410 7 janv. 18:04 ICEauthority and not with line as user : -rw------- 1 andre andre 410 7 janv. 18:10 ICEauthority
So, permanently to not have that, I must type in root : chown andre.andre /run/user/1000/
Who among you with Debian-Bullseye have this message DCOP_SERVER ?
I don't understand how to correct, avoid this error message.
If I cannot find a solution, I must use another desktop... and wait the migration for my two others computers.
Cheers, André
On 2022/01/08 03:08 AM, ajh-valmer wrote:
Hello, Best Year best wishes for everybody !
I made a complete reinstallation of Debian-Bullseye and tde-trinity.
Always this problem DCOP_SERVER when "/run/user/1000/" has this line : -rw------- 1 root root 410 7 janv. 18:04 ICEauthority and not with line as user : -rw------- 1 andre andre 410 7 janv. 18:10 ICEauthority
So, permanently to not have that, I must type in root : chown andre.andre /run/user/1000/
Who among you with Debian-Bullseye have this message DCOP_SERVER ?
I don't understand how to correct, avoid this error message.
If I cannot find a solution, I must use another desktop... and wait the migration for my two others computers.
Cheers, André
Hi André, I used Bullseye with TDE for as long as bullseye was testing, so for quite a while. I also think there are a number of other users on bullseye without this issue.
I remember that you mentioned with a new user this problem does not happen. Am I right? If so, as I suggested in one of my previous emails, you can do as so: 1) backup your home folder 2) remove your andre user 3) create new andre user, don't copy any of your existing settings. Verify a TDE session works fine with this new user. Again my understand is that you did this already before. 4) if all works fine, progressively copy over some of your setup to the user, verify everything is working fine. Save a backup of your $HOME and repeat the process copying over more and more things or installing more packages.
Cheers Michele
One thing I found, for me, was that this behavior gets triggered by using the icon for the konqueror file browser, for browsing the file system as the root user, when logged in as the regular user.
It does happen on opensuse Tumbleweed. So i ended up trying to find a different file browser to use as root, and although it does not trigger the issue for me, i can't copy paste into that alternative browser.
So, if i need to administrate i log out as regular user, log in as root user.
You will have to do that to change ownership of the files in the run directory.
On Fri, Jan 7, 2022, 6:40 PM Michele Calgaro via tde-users < users@trinitydesktop.org> wrote:
On 2022/01/08 03:08 AM, ajh-valmer wrote:
Hello, Best Year best wishes for everybody !
I made a complete reinstallation of Debian-Bullseye and tde-trinity.
Always this problem DCOP_SERVER when "/run/user/1000/" has this line : -rw------- 1 root root 410 7 janv. 18:04 ICEauthority and not with line as user : -rw------- 1 andre andre 410 7 janv. 18:10 ICEauthority
So, permanently to not have that, I must type in root : chown andre.andre /run/user/1000/
Who among you with Debian-Bullseye have this message DCOP_SERVER ?
I don't understand how to correct, avoid this error message.
If I cannot find a solution, I must use another desktop... and wait the migration for my two others computers.
Cheers, André
Hi André, I used Bullseye with TDE for as long as bullseye was testing, so for quite a while. I also think there are a number of other users on bullseye without this issue.
I remember that you mentioned with a new user this problem does not happen. Am I right? If so, as I suggested in one of my previous emails, you can do as so:
- backup your home folder
- remove your andre user
- create new andre user, don't copy any of your existing settings. Verify
a TDE session works fine with this new user. Again my understand is that you did this already before. 4) if all works fine, progressively copy over some of your setup to the user, verify everything is working fine. Save a backup of your $HOME and repeat the process copying over more and more things or installing more packages.
Cheers Michele ____________________________________________________ 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...
said James Leone:
| One thing I found, for me, was that this behavior gets triggered by | using the icon for the konqueror file browser, for browsing the file | system as the root user, when logged in as the regular user. | | It does happen on opensuse Tumbleweed. So i ended up trying to find a | different file browser to use as root, and although it does not trigger | the issue for me, i can't copy paste into that alternative browser. | | So, if i need to administrate i log out as regular user, log in as root | user. | | You will have to do that to change ownership of the files in the run | directory.
Have you tried Krusader and Krusader-SU? -- dep
Pictures: http://www.ipernity.com/doc/depscribe/album Column: https://ofb.biz/author/dep/
On 2022-01-07 20:52:37 James Leone wrote:
One thing I found, for me, was that this behavior gets triggered by using the icon for the konqueror file browser, for browsing the file system as the root user, when logged in as the regular user.
It does happen on opensuse Tumbleweed. So i ended up trying to find a different file browser to use as root, and although it does not trigger the issue for me, i can't copy paste into that alternative browser.
So, if i need to administrate i log out as regular user, log in as root user.
You will have to do that to change ownership of the files in the run directory.
If you prefer using Konqueror (as I do), you might try invoking it from a Konsole root session. (Start Konsole, click and hold the 'new session' button at bottom left and select Root Shell.) I do 90+% of the things I need to do as root through a Konsole root session, and when I want to start YaST2 or a root Konqueror instance I do it from that Konsole session.
Leslie -- Operating System: Linux Distribution: openSUSE Leap 15.3 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.10 tde-config: 1.0
On 2022/01/08 11:52 AM, James Leone wrote:
One thing I found, for me, was that this behavior gets triggered by using the icon for the konqueror file browser, for browsing the file system as the root user, when logged in as the regular user.
It does happen on opensuse Tumbleweed So i ended up trying to find a different file browser to use as root, and although it does not trigger the issue for me, i can't copy paste into that alternative browser.
So, if i need to administrate i log out as regular user, log in as root user.
You will have to do that to change ownership of the files in the run directory.
I can confirm this and I think this is the same issue described by another user when switching to root inside TCC login manager page.
@André: can you let us know if the problem on your system happens in similar fashion?
In any case, it is definitely something that needs to be fixed before the next release. Cheers Michele
On Saturday 08 January 2022 03:39:14 Michele Calgaro via tde-users wrote:
On 2022/01/08 03:08 AM, ajh-valmer wrote:
I made a complete reinstallation of Debian-Bullseye and tde-trinity. Always this problem DCOP_SERVER when "/run/user/1000/" has this line : -rw------- 1 root root 410 7 janv. 18:04 ICEauthority and not with line as user : -rw------- 1 andre andre 410 7 janv. 18:10 ICEauthority So, permanently to not have that, I must type in root : chown andre.andre /run/user/1000/ Who among you with Debian-Bullseye have this message DCOP_SERVER ?
Hi André, I used Bullseye with TDE for as long as bullseye was testing, so for quite a while. I also think there are a number of other users on bullseye without this issue. I remember that you mentioned with a new user this problem does not happen. Am I right? If so, as I suggested in one of my previous emails, you can do as so:
- backup your home folder
- remove your andre user
- create new andre user, don't copy any of your existing settings.
Verify a TDE session works fine with this new user. Again my understand is that you did this already before. 4) if all works fine, progressively copy over some of your setup to the user, verify everything is working fine. Save a backup of your $HOME and repeat the process copying over more and more things or installing more packages. Michele
Hi Michele,
I created a new user, so with a /home/<user>/ almost virgin. Idem, the dcopserver error messages are always there. Thoses messages appears when I click on an icon that ask a program in root mode (gparted, konqueror, konsole in root...). Just after, I have these rights in "/run/user/1000/" : -rw------- 1 root root 410 7 janv. 17:12 ICEauthority that cause the message.
A solution : to stop the icon that ask the root mode. But why you and others have not this message ? Michele, can you make a test by creating an icon in root mode, (I suggest Gparted) and tell me if you receive the same behaviour.
Cheers, André
On Saturday 08 January 2022 17.32:36 ajh-valmer wrote:
Always this problem DCOP_SERVER when "/run/user/1000/" has this line : -rw------- 1 root root 410 7 janv. 18:04 ICEauthority and not with line as user : -rw------- 1 andre andre 410 7 janv. 18:10 ICEauthority So, permanently to not have that, I must type in root : chown andre.andre /run/user/1000/ Who among you with Debian-Bullseye have this message DCOP_SERVER ?
I just got it after upgrading Raspbian to bullseye. Seems to have disappeared after changing the permissions on ICEauthority.
Thierry
Michele, can you make a test by creating an icon in root mode, (I suggest Gparted) and tell me if you receive the same behaviour.
Hi André yes, as I mentioned in another email yestwrday I can reproduce a similar issue. Whether or not you get it, it depends on your modus operandi. If you only do admin staff from a root console or a root session, you don't get this issue :-) Anyway we are going to have a look at it, since it seems it affects a number of users, all in similar ways. Will report back once fixed, hopefully it won't take too long. Cheers Michele
Hi Michele,
I created a new user, so with a /home/<user>/ almost virgin. Idem, the dcopserver error messages are always there. Thoses messages appears when I click on an icon that ask a program in root mode (gparted, konqueror, konsole in root...). Just after, I have these rights in "/run/user/1000/" : -rw------- 1 root root 410 7 janv. 17:12 ICEauthority that cause the message.
A solution : to stop the icon that ask the root mode. But why you and others have not this message ? Michele, can you make a test by creating an icon in root mode, (I suggest Gparted) and tell me if you receive the same behaviour.
Cheers, André
Hi André, the issue with ICEauthority ownership when using tdesu has now been fixed. I seem to recall you are using PSB. IF so, would you be able to test with the updated tdelibs and confirm whether it works for you as well?
@other users who reported the same issue (or recent problems with starting DCOP or other programs after launching something as root): if you can test and feedback as well, it would be great.
Cheers Michele
On Friday 04 February 2022 15:19:45 Michele Calgaro via tde-users wrote:
Hi Michele, I created a new user, so with a /home/<user>/ almost virgin. Idem, the dcopserver error messages are always there. Thoses messages appears when I click on an icon that ask a program in root mode (gparted, konqueror, konsole in root...). Just after, I have these rights in "/run/user/1000/" : -rw------- 1 root root 410 7 janv. 17:12 ICEauthority that cause the message.
Hi André, the issue with ICEauthority ownership when using tdesu has now been fixed. I seem to recall you are using PSB. IF so, would you be able to test with the updated tdelibs and confirm whether it works for you as well? @other users who reported the same issue (or recent problems with starting DCOP or other programs after launching something as root): if you can test and feedback as well, it would be great.
Hello Michele,
Before testing, what is PSB ? Which files I have to update ?
Thanks, cheers,
André
Hello Michele,
Before testing, what is PSB ? Which files I have to update ?
Thanks, cheers,
André
Hi André, PSB is the Preliminary Stable Builds repository, see here: https://wiki.trinitydesktop.org/Preliminary_Stable_Builds Basically a rolling pre-build of the next stable R14.0.x release. I thought you were using it, but may be I am mistaken with some other user.
The update is part of tdelibs, so there will be an updated package in that case. Cheers Michele
On 2022-02-04 09:20:19 Michele Calgaro via tde-users wrote:
Hello Michele,
Before testing, what is PSB ? Which files I have to update ?
Thanks, cheers,
André
Hi André, PSB is the Preliminary Stable Builds repository, see here: https://wiki.trinitydesktop.org/Preliminary_Stable_Builds Basically a rolling pre-build of the next stable R14.0.x release. I thought you were using it, but may be I am mistaken with some other user.
The update is part of tdelibs, so there will be an updated package in that case. Cheers Michele
Is there a way for non-Ubuntu users to access PSB resources?
Leslie --
On Friday 04 February 2022 19:20:54 J Leslie Turriff wrote:
Is there a way for non-Ubuntu users to access PSB resources?
Leslie
Just for clarification of what I said: In my own experience, those features (compress, move to, copy to) disappeared from the menu sometime during when I was using the PSB or PTB repos. They were there when I used the main TDE repositories.
This could have been due to my own mistakes, although I don't see how, since the plugins were already installed and I only changes the repos in my sources list, then updated and upgraded. The plugins, too, ought to have been upgraded, but seemed to be missing from one or both of those repos.
Now that I am back to using the main repository (having changed machines, and moved from i386 to amd64, upgraded from Devuan Beowulf to Chimaera), those features have come back. I don't know if any of this is relevant to your situation; I'm just reporting what happened.
Bill
Anno domini 2022 Fri, 4 Feb 21:20:54 -0600 J Leslie Turriff scripsit:
On 2022-02-04 09:20:19 Michele Calgaro via tde-users wrote:
Hello Michele,
Before testing, what is PSB ? Which files I have to update ?
Thanks, cheers,
André
Hi André, PSB is the Preliminary Stable Builds repository, see here: https://wiki.trinitydesktop.org/Preliminary_Stable_Builds Basically a rolling pre-build of the next stable R14.0.x release. I thought you were using it, but may be I am mistaken with some other user.
The update is part of tdelibs, so there will be an updated package in that case. Cheers Michele
Is there a way for non-Ubuntu users to access PSB resources?
Leslie
I use PBS on devuan since ages ... and IMO it's the TDE repo to use :)
Nik
On Friday 04 February 2022 16:20:19 Michele Calgaro via tde-users wrote:
Hi André, PSB is the Preliminary Stable Builds repository, see here: https://wiki.trinitydesktop.org/Preliminary_Stable_Builds Basically a rolling pre-build of the next stable R14.0.x release. I thought you were using it, but may be I am mistaken with some other user. The update is part of tdelibs, so there will be an updated package in that case.
Hi Michele,
I upgraded tdelibs-trinity, the problem dcopserver seems resolved, hoping definitively, I keep you inform if the bug comes back.
Many thanks for your help and for the Trinity team.
Cheers
André
I upgraded tdelibs-trinity, the problem dcopserver seems resolved, hoping definitively, I keep you inform if the bug comes back.
Many thanks for your help and for the Trinity team.
Cheers
André
Hi André, thanks for the feedback, good to hear you are not seeing the issue any more!! Cheers Michele
-
ajh-valmer -
Borg Labs -
dep -
Dr. Nikolaus Klepp -
J Leslie Turriff -
James Leone -
Michele Calgaro -
Slávek Banko -
Thierry de Coulon -
William Morder