![](https://seccdn.libravatar.org/avatar/27d96fee259c5dea6186876d57942595.jpg?s=120&d=mm&r=g)
8.0 Pro, KDE 3.0.4. Long time ago back when I was using 3.0.0, My 'kdesu konqueror' got broke and doing so wouldn't do anything. Everything was fine after I reformatted my hard drive till recently. Last that I remember was logging into X as root that could have broken this again. I don't recall doing anything weird in X that could have broken my KDE. One guy replied to the bug that I had posted to KDE project. Following the advice the the forwarded e-mail, if I simply do a: export LOGNAME=root kdesu konqueror in a shell window, it seems to work just fine. Anyone got any ideas what this LOGNAME crap is? FORWARDED E-MAIL ============== 45883@bugs.kde.org It seems that setting the env variable LOGNAME to root solves this issue. I also had the same problem: KDE 3.0.2, since I cleaned my /tmp directory by removing kde-*/, ksocket-*/, mcop-*/ and .ICE-unix/ I couldn't start kdesu konqueror anymore. Now I'm starting 'kdesu konqueror-root', where 'konqueror-root' is a script as follows: #!/bin/bash export KDEHOME=/root/.kde3 export USER=root export BASH_ENV=/root/.bashrc export GTK_RC_FILES=/etc/gtk/gtkrc:/root/.gtkrc:/root/.gtkrc-kde export GS_LIB=/root/.kde3/share/fonts export LOGNAME=root # <-- THIS IS WHAT IS REALLY NEEDED! exec /opt/kde3/bin/konqueror 2>/dev/null >/dev/null I specified all the other variables because I noticed that some apps started by kdesu were chowning the settings in my ~/.kde3/share/config directory, so that they couldn't read and modify their own settings when I tried to run them as user (i.e: kppp started with only the button "cancel" active, kedit didn't start at all). Hope this will be useful. Bye - Mau
participants (1)
-
Salman Khilji