After setting WIPE_TMP="yes" in /etc/conf.d/bootmisc, I discovered that .ICE-unix and .X11-unix have wrong ownership (=> KDE refuses to start). This happens, because those directories are only created in the WIPE_TMP!="yes" branch in bootmisc. While this behaviour might be intended, it is rather surprising and IMHO a real bug. Reproducible: Always Steps to Reproduce: 1. Set WIPE_TMP="yes" 2. reboot 3. start X11/KDM/... 4. Do "ls -la /tmp" OR Try to start KDE Actual Results: Files are owned by the user who started X11. Expected Results: Files should be owned by root.
Created attachment 63890 [details, diff] Make creation of *-unix directories unconditional
fixed in svn, thanks
*** Bug 100950 has been marked as a duplicate of this bug. ***
*** Bug 101012 has been marked as a duplicate of this bug. ***
*** Bug 102065 has been marked as a duplicate of this bug. ***
Whoever maintains baselayout or KDE: Could you please add some hint into /etc/conf.d/bootmisc that states: cleaning /tmp might prevent KDE from starting up ?? One week ago, I updated my kernel, compiler, several libs, unsplit&updated most of KDE and changed that variable at once. Then rebooted and KDE showed errors like KWrited
Whoever maintains baselayout or KDE: Could you please add some hint into /etc/conf.d/bootmisc that states: cleaning /tmp might prevent KDE from starting up ?? One week ago, I updated my kernel, compiler, several libs, unsplit&updated most of KDE and changed that variable at once. Then rebooted and KDE showed errors like KWrited überwacht Gerät /dev/pts/3 kdecore (KLibLoader): WARNING: KLibrary: /usr/kde/3.4/lib/kde3/kcm_kdnssd.so: undefined symbol: init_kdnssd _IceTransmkdir: ERROR: Owner of /tmp/.ICE-unix must be set to root _IceTransSocketUNIXCreateListener: mkdir(/tmp/.ICE-unix) failed, errno = 1 _IceTransMakeAllCOTSServerListeners: failed to create listener for local KSMServer: Error listening for connections: Cannot establish any listening socke It took several days to re-emerge stuff just to trace it down to *that* cause. That was very annoying, because I focused on kcm_kdnssd.so, which was the first error that ocurred. I guessed that was the cause for the next error but it is appearently not. Even if the other change is in the portage tree somewhere, I did not find good documentation on the KDE breakdown. I do like gentoo in general, but at that point I think, the documentation must urgently be updated.
*** Bug 105666 has been marked as a duplicate of this bug. ***
*** Bug 105975 has been marked as a duplicate of this bug. ***
*** Bug 107632 has been marked as a duplicate of this bug. ***
*** Bug 107847 has been marked as a duplicate of this bug. ***
*** Bug 108670 has been marked as a duplicate of this bug. ***
I don't understand why if this was fixed back in July, there are still new reports coming in with the same problem, and I still see the same problem on my system. Should this bug be re-opened?
Yeah, definitely. It's still remains unfixed with me too.
*** Bug 114738 has been marked as a duplicate of this bug. ***
For me too.
It does not happen any more with me. To wich package ist this bug related?
(In reply to comment #16) /etc/init.d/bootmisc does the damage. sys-apps/baselayout owns that script.
Ok, it still happens on my other machine. The have nearly the same config. What is the fix for this problem?
1.11.14 has already been released, why dont you try updating your tree
*** Bug 116395 has been marked as a duplicate of this bug. ***
baselayout-1.11.14 seems to work fine -- when will it go stable? :) Hmmm... according to [1] is also the directory /tmp/.font-unix affected and should probably created, too. Actually, I still think this should be done by the xdm startup scripts :) [1] http://wiki.x.org/X11R6.8.0/doc/RELNOTES5.html#39
