Re: [trinity-devel] .xsession-errors is restored

Now that .xsession-errors is restored, I'll update my previous reports. All tests performed with the existing ~/.kde profiles. With the latest startkde I received this error message: /usr/bin/startkde: line 403: /usr/local/kde-mods/share/kgtk/preload: No such file or directory I'm attaching an updated startkde that includes an error check for that file. The current script does not test for the existence of the file before trying to read. As I mentioned previously, I use a second KDEDIR location and the KDEDIRS variable. There is no such file in my second KDEDIR location. Hence the error. :) ================================================================== Received these messages when running as root and non-root: QObject::connect: No such signal ConnectionManager::statusChanged(QString,NetworkStatus::EnumStatus) QObject::connect: (sender name: 'connection_manager') QObject::connect: (receiver name: 'networkstatusindicator') QObject::connect: No such signal ConnectionManager::statusChanged(QString,NetworkStatus::EnumStatus) QObject::connect: (sender name: 'connection_manager') QObject::connect: (receiver name: 'networkstatusindicator') I'll take wild guess here that I am using something that is not yet updated with the TQT interface. Which package I don't know. ================================================================== Received these messages as non-root: QClipboard::setData: Cannot set X11 selection owner for CLIPBOARD I could not repeat that error on restarting X. xmodmap: unable to open file '/opt/trinity/share/apps/kxkb/system.xmodmap &> /dev/null' for reading xmodmap: 1 error encountered, aborting. xmodmap: unable to open file '/home/users/tester/.Xmodmap &> /dev/null' for reading xmodmap: 1 error encountered, aborting. I can eliminate the xmodmap errors if I disable those options in KControl, but I never have seen the errors until testing Trinity. So something else is happening here. ================================================================== Received these messages as root: Klipper is already running! ================================================================== Still seeing /root/.kde3 being created and the duplicate cache, socket, and tmp directories. Adding the snippet in startkde to explicity set KDEROOTHOME stops the creation. Possibly the same idea can be merged into the kde source code. # Run a quick test for root. if [ -z "$KDEROOTHOME" ] && [ "$UID" = "0" ]; then echo "startkde: User ID is $UID. Setting KDEROOTHOME to $KDEHOME." export KDEROOTHOME=$KDEHOME fi ================================================================== I hope this helps! Darrell