<snip> > > 1. As non-root Trinity seems to completely honor $KDEHOME. There is no > ~/.kde3 directory created and Trinity uses my existing ~/.kde directory. > > As root Trinity does not fully honor $KDEHOME. > <snip> Quick comment here. The above was very important. ;-) Trinity expects to see KDEROOTHOME set, not KDEHOME, when run as root. Maybe you can help here; is this a Debian-only distinction, or do other Linux systems also use KDEROOTHOME? > > =========================================================== > > 4. The existing startkde is Debianized and causes breakage on Slackware > systems. I am submitting a proposed new startkde script. The proposed > script avoids certain presumptions and adds some tests before running > various commands. The proposed script also adds additional echo messages > to help debugging efforts. Can you attach it please? I would like to look at it/get it in SVN ASAP as we have already run past the feature freeze and these types of major changes need to be tested thoroughly prior to release. > > =========================================================== > > 5. As root, the .xsession-error log shows the following errors: > > ... > startkde: Starting KDE. (message is from my proposed startkde script) > KDE_FULL_SESSION: true (message is from my proposed startkde script) > KDE_SESSION_UID: 0 (message is from my proposed startkde script) > kbuildsycoca running... > Reusing existing ksycoca > Invalid entry (missing '=') at /tmp/kde-root/kconf_updatea8Qi7b.tmp:1 > Invalid entry (missing '=') at /tmp/kde-root/kconf_updateBSSSOa.tmp:1 > startkde: Looks like kdeinit started. (message is from my proposed > startkde script) > Warning: connect() failed: : No such file or directory > QObject::connect: No such signal Kicker::settingsChanged(SettingsCategory) > QObject::connect: (sender name: 'kicker') > QObject::connect: (receiver name: 'animtt') > kbuildsycoca running... > Reusing existing ksycoca > ... > > As non-root: the .xsession-error log shows the following errors: > > QObject::connect: No such signal Kicker::settingsChanged(SettingsCategory) > QObject::connect: (sender name: 'kicker') > QObject::connect: (receiver name: 'animtt') > /usr/bin/xmodmap: unable to open file > '/usr/share/apps/kxkb/ubuntu.xmodmap' for reading > /usr/bin/xmodmap: 1 error encountered, aborting. > /usr/bin/xmodmap: unable to open file '/home/users/tester/.Xmodmap' for > reading > /usr/bin/xmodmap: 1 error encountered, aborting. > > Ubuntu.xmodmap? This is Slackware. :) I can stop those error messages when > I disable the related keyboard options in kcontrol. Regardless, I don't > use an xmodmap file here. Users should not be bothered with such related > messages. The messages might be caused by xmodmap,but I never have seen > any such errors before until running Trinity. I have the same X packages > installed on my virtual system as my actual system. > > I saw these additional error messages as non-root: > > WARNING: DCOPReply<QString>: cast to 'TQString' error > QObject::connect: No such signal > ConnectionManager::statusChanged(NetworkStatus::EnumStatus) > QObject::connect: (sender name: 'connection_manager') > QObject::connect: (receiver name: 'networkstatusindicator') > QObject::connect: No such signal > ConnectionManager::statusChanged(NetworkStatus::EnumStatus) > QObject::connect: (sender name: 'connection_manager') > QObject::connect: (receiver name: 'networkstatusindicator') > > So again, seems there is some kind of Debianization here looking for some > kind of network manager that does not exist on Slackware. That looks more like OpenSUSE code IMHO. I'm not going to spend a lot of time tracking them down right now, as they are pretty much harmless and fall into the irritant category. > > =========================================================== > > 6. Something is trying access samba config files. I have seen such > messages before when testing Debian Lenny. Therefore I suspect some kind > of Trinity/Debian hook into a network manager of some sort. > > params.c:OpenConfFile() - Unable to open configuration file > "/root/.smb/smb.conf.append": > No such file or directory > Using netbios name {HOSTNAME}. > Using workgroup {WORKGROUP}. That might be Debian, or it might be the Samba kioslave. > > =========================================================== > > 7. Trinity seems to be ignoring ~/.config/autostart. In that directory I > have a hplip-systray.desktop with the following [Desktop Entry] directive: > Hidden=true. That directive should prevent hplip-systray from starting. An > hplip-systray.desktop file is found in /etc/xdg/autostart, but the Hidden > directive should override starting that app. I don't have this problem on > 3.5.10. This one is more serious and will need to be looked into. > > [35;01mwarning: hp-systray should not be run as root/superuser.[0m > [31;01merror: hp-systray cannot be run as root. Exiting.[0m > > [01mHP Linux Imaging and Printing System (ver. 2.8.10)[0m > [01mSystem Tray Status Service ver. 2.0[0m > > Copyright (c) 2001-8 Hewlett-Packard Development Company, LP > This software comes with ABSOLUTELY NO WARRANTY. > This is free software, and you are welcome to distribute it > under certain conditions. See COPYING file for more details. > > In addition to the hplip-systray errors, running as non-root produces two > additional lines: > > [31;01merror: PyQt not installed. GUI not available. Exiting.[0m > [35;01mwarning: Qt/PyQt 3 initialization failed.[0m > > True, I do not have PyQT compiled or installed. Irritant. > > =========================================================== > > 8. In the shutdown sequence there are messages about creating a link: > > Creating link /root/.kde/socket-{hostname}. > Created link from "/root/.kde/socket-{hostname}" to "/tmp/ksocket-root" > > The messages seem to be generated from kdelibs/kinit/lnusertemp.c. I don't > know why those links are created at shutdown. Some people maintain those > links in tmpfs and by intent, are lost on power down. I'll look into it. Might be a Debian change that needs to be reverted. > > =========================================================== > > 9. Something is creating a .directory file at the top root level of my > file system. Yes, this is possible only because I am running the tests as > root, but running as root tends to reveal these kinds of quirks. :) > > As non-root I saw the following related error message: > > cp: cannot create regular file `//.directory': Permission denied Needs to be fixed ASAP. > > =========================================================== > > 10. Trinity displays desktop folder icons for every directory in the top > root level of my files system. I don't know where these icons are from or > how to stop them. This probably is something trivial, which epxlains why I > don't see the solution. :) However, my original desktop icons no longer > are available. See my previous message; the fix is in SVN. > > =========================================================== > > 11. Something is overriding my konsole settings. I run konsole with a > black background. This changes to white when running Trinity. I have seen > this behavior before when testing Debian Lenny. Hence I suspect some kind > of Debian remnant in Trinity. This happens with both root and non-root. Weird! Is the black Konsole some kind of system default or did you try to save it that way under your profile? > > =========================================================== > > 12. Please consider changing the default mouse pointer to "No busy > cursor." The bouncing cursor is annoying and always has been. Will do. > > =========================================================== > > > I hope this information helps. <snip> Yes it does. Very few of these issues show up under Debian, so your feedback is essential to getting Trinity working properly. Tim