I set up the TMPDIR in my environment, so that temporary files go in ~/tmp instead of /tmp. This causes some errors and strange behavior in the KDE session. From the .xsession-errors: kbuildsycoca running... Error: "/home/mgiann/.kde/socket-makis" points to "/home/mgiann/tmp/ksocket-mgiann" instead of "/tmp/ksocket-mgiann". Error: "/home/mgiann/.kde/socket-makis" points to "/home/mgiann/tmp/ksocket-mgiann" instead of "/tmp/ksocket-mgiann". Warning: connect() failed: : No such file or directory There are already artsd objects registered, looking if they are active... Error: Can't add object reference (probably artsd is already running). If you are sure it is not already running, remove the relevant files: /tmp/ksocket-mgiann/Arts_SoundServerV2 /tmp/ksocket-mgiann/Arts_SoundServer /tmp/ksocket-mgiann/Arts_SimpleSoundServer /tmp/ksocket-mgiann/Arts_PlayObjectFactory /tmp/ksocket-mgiann/Arts_AudioManager See errors about wrong paths to tmp directories. The TMPDIR variable has as a result that the first KDE session I start has no knotify running. The next session i start, finds that the last knotity execution failed and starts it up with a warning. Later, when I try to close such session, it takes longer than expected (close to 1min instead of 2-3 seconds). Finally, the temporary data seem to be shared among my ~/tmp (where I want them) and /tmp. KDE: 3.5.5 kdelibs version installed: 3.5.5-r9 kdebase version installed: 3.5.5-r3 Reproducible: Always Steps to Reproduce: 1.in .tcshrc: setenv TMPDIR /home/mgiann/tmp 2. 3.
Please try to reproduce this problem in KDE 3.5.7 if you can. 3.5.7 is scheduled to go to stable soon anyway.
Please test with 3.5.7 which is now stable and provide your emerge --info if the problem persists.
Created attachment 129205 [details] output of emerge --info
Comment on attachment 129205 [details] output of emerge --info I updated the complete system( emerge -N --deep world), not without problems... The problem still persists, as it was describe in the initial report.
provide the information requested.
Please see if this bug still persists in kde-3.5.10
(In reply to comment #6) > Please see if this bug still persists in kde-3.5.10 > Unable to upgrade to kde-3.5.10 and test. Sorry.
OK, since there was no other user with similar problem and given the state of kde3.5, i'll have to close this. Euxaristo :)