walt wrote:
On 04/26/2010 03:11 PM, Dale wrote:
Alex Schuster wrote:
Dale writes:
Again, I am using Konsole for this. This may be a KDE thing. I know
it worked fine in KDE3 but then again, a LOT of things worked fine in
KDE3.
It's probably not a KDE thing. I'm also using konsole in KDE4, and
after
becoming root (via su or su -) I have no Problems starting X
applications.
I'm no expert at X authorization stuff. But I know that in the past
I also
had trouble when becoming root. Why it works for me and not for you - I
don't know.
Workarounds you might try:
- Emerge sux, and use sux instead of su. Worked for me in the past.
- ssh -Y r...@localhost
Wonko
I don't use su. When I open the Konsole, it asks for a password.
Does that mean you are not using the standard konsole, rather a special
icon intended to open a root terminal? Must be, otherwise it wouldn't
ask for the root password.
Try opening a standard user konsole and just use su instead. (Or even,
heaven forbid, an xterm instead of konsole.) That should detect a KDE
problem if it exists.
The way I did was this. The entry you have but I edited it to run as
root when it is clicked on. I have a couple things that are set that
way. Kbackup is set that way. It can't access some files I want to
backup if it is set to run as a user. You can edit this by clicking the
advanced tab in the menu editor. I also have konqueror set as my file
manager and it is set to run as root. It is running on another desktop
right now. It works fine. I can run Kbackup, as root, and it connects
just fine. I just tried it to make sure. Since I can go to my /root
directory, I know it is running as root.
Weird things always happen to me. Why can't something weird like
winning the lottery happen to me? lol
Dale
:-) :-)