DCOP server changes ~/.ICEAuthority permissions to root:root instead for security reasons. Reproducible: Always Steps to Reproduce: 1. emerge k3b 2. login to user account 3. sudo k3b 3. close k3b 4. logout of gnome 5. login Actual Results: When user logs back in, the session stops and the following error is logged "** WARNING **: Unable to lock ICE authority file: /home/shane/.ICEauthority" at closer inspection, as detailed in http://dbforums.com/arch/126/2003/5/790706 , it seems that the permissions of the file had changed to root:root. This forum posting suggests dcop accessing ICE is to blame. Expected Results: logged into the gnome session without a hitch Numerous discussions have raised this issue. http://mail.gnome.org/archives/gnome-list/2000-February/msg00554.html
Ok, and wouldn't: ICEAUTHORITY="~root/.ICEauthority" sudo k3b fix the problem?
yeah, should/could that be added to the ~root/.bash_profile via an ebuild?
It could be added, but I'm not sure how many people run k3b with sudo. seems to me like adding a message to the ebuild about it would be a good compromise.
I think this may happen with running any KDE program that uses DCOP/ICE.
could we hack this into a kde eclass, so the message is displayed whenever a KDE application is merged?
I think that's a bit overkill. It should be pretty obvious that running programs under sudo is always a bit more volatile than directly running them.
Can we get a deciding decision on this problem?
I guess I'm not all that inclined to do much about it. I think it's something that's good to know, but I don't see it as a problem that will affect a lot of people. Have you tried out kdesu? It's a bit like sudo, and I think it may handle the permission stuff better.
closing per above comment.
