for some reason "su/sudo/kdesu konqueror" doesn't work

**the dsc** · 08-11-2007

I simply don't understand it. For all other applications, kdesu will work... but with konqueror it has being difficult these days. I still haven't perceived any pattern...

Konqueror actually runs, it's shown as a process on ksysguard, and it was run by root since I can't kill it unless I use kdesu ksysguard (which works) - buy konqueror's GUI simply doesn't appear ...

The weird thing is that it isn't always like this... if I restart the PC, it will probably work if I run kdesu>konqueror as one of the first things I do... something in between, perhaps some process, locks its GUI for some reason, I think.

The situation is similar with sudo, from a terminal. The "output" is that:

Code:

d@kubuntu:~$ sudo konqueror
Password:
X Error: BadDevice, invalid or uninitialized input device 154
  Major opcode:  143
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 154
  Major opcode:  143
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
ScimInputContextPlugin()

And it just stays there, I can type "enter" and it will make blank lines appear at the end, without the preceding terminal prompt ("d@kubuntu:", in my case).

These "invalid whatever" lines appear also with the "regular" konqueror being called from a command line, so it's not an issue, I think. Even the "Failed to open device" appear, and a non-su konqueror will run.

I've tried to call konqueror from a kdesu>konsole, to see if it would "inherit" the SU status, but also won't work, no GUI is shown.

If I call a regular terminal, type SU, the password, and then "konqueror", it won't be able to "connect to the X server".

The problem shouldn't be with simultaneous su-processes since I can open more than one su-ksysguard at once... I also have no other non-su konqueror running, just in case it would be an issue...

Is this whole situation expected to be "normal" or I've already managed to make my installation all buggy?

I think I did, since I don't recall having this issue earlier... but may have been due to coincidentally using kdesu>konqueror only within the brief window of opportunity that it works... I don't know.

**devils casper** · 08-12-2007

You should not use sudo to gain root privileges in GUI application. Use kdesu only. sudo throws errors and could corrupt .ICEauthority file. You will have login problems later on.

**the dsc** · 08-13-2007

Wow. Weird.

Thanks for the tip anyway.

Right now, kdesu>konqueror worked....

Is there some way to check if this .ICEauthority file is okay right now?

**devils casper** · 08-13-2007

If you dont have any Login Problems like Login Screen doesn't appear, takes too much time to appear on loggiing out or dont let you login again then .ICEauthority file is okay.

**the dsc** · 08-18-2007

Thanks for the reply!

(I missed it earlier for some reason)

Now I'm in another installation, but the advice still applies.

Thread Tools

Display

for some reason "su/sudo/kdesu konqueror" doesn't work

Posting Permissions