-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 . Thanks, but in konsolesu: hydra:/opt/kde3/bin # sux -c ./konqueror -s bash root No matches found, authority file "/dev/fd/62" not written xauth: (argv):1: unable to read any entries from file "(stdin)" Xlib: connection to ":0.0" refused by server Xlib: No protocol specified konqueror: cannot connect to X server :0 hydra:/opt/kde3/bin # And in konsole: hydra@hydra:/opt/kde3/bin$ sux -c ./konqueror root Password: mcop warning: user defined signal handler found for SIG_PIPE, overriding /tmp/mcop-hydra is not owned by user zone still contained 2 blocks hydra@hydra:/opt/kde3/bin$ On Tuesday 30 April 2002 10:01, Tor Sigurdsson wrote:

In Konsole use "sux" instead of "su" or "kdesu". It adds your cookie to roots cookiejar ( ~/.Xauthority )

AnonymousCoward (þriðjudagur 30. apríl 2002 14:51)

...

. I can't seem to get subscribed to the kde list (never get confirm), so I'll ask here.

Running Suse8 with all current updates. It has always been my practice to run as a user, and to invoke Konq & Konsole in superuser mode when I need them thus.

But with Suse8 I can no longer (as a user) launch X-based programs from these windows. Logged in as root I can, but not when as a user and launching from these programs. For instance in Konq I cannot right-click|OpenWith|Advanced Editor a file: "KDEInit could not launch 'kwrite'". And from the su konsole # konqueror and I get: Xlib: connection to ":0.0" refused by server Xlib: No protocol specified

konqueror: cannot connect to X server :0

In user konsole $ kdesu konqueror yields nothing.

This looks alot like a security issue. Maybe the X server is intentionally disabled from accepting root commands from a user. Or maybe it's one missing setup step. Anyone know the answer?

- -- Neckties strangle clear thinking. -- Lin Yutang -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8zrbbnQ18+PFcZJsRAhMZAJ0Yv1u+NLSF5b7JgCrvDV8QDXKWWwCdECzh 6ef7vqudkeNjcRD3v59CCbE= =+uXL -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 01 May 2002 08:26, Philipp Thomas wrote:

AnonymousCoward <quantum@ultra2k.com> [ 30.04.2002 10:23:00 -0500]:

...

hydra:/opt/kde3/bin # sux -c ./konqueror -s bash root No matches found, authority file "/dev/fd/62" not written xauth: (argv):1: unable to read any entries from file "(stdin)" Xlib: connection to ":0.0" refused by server Xlib: No protocol specified

konqueror: cannot connect to X server :0 hydra:/opt/kde3/bin #

Seems you're running sux as root, ain't you? That of course won't work. Sux is meant to be run as normal user.

If you want to have a permanent root shell, start 'xterm for superuser' from the KDE menu or do 'ssh -X root@localhost'. Both will give you a root shell with access to the display for X apps.

Philipp

PS It's common courtesy to at least sign with your real name.

Thanks Philipp. But that was only one way I was trying. From user konsole it fails like this: hydra@hydra:/opt/kde3/bin$ sux -c ./konqueror -s bash root Password: mcop warning: user defined signal handler found for SIG_PIPE, overriding /tmp/mcop-hydra is not owned by user zone still contained 3 blocks hydra@hydra:/opt/kde3/bin$ But this is not the major problem. Main problem is in Konq superuser I cannot right-click files & AdvancedEditor, when logged in as a user. As a rule, I'm logged in as a user, and do admin functions in Konq superuser. There is a problem with that in Suse8 now. But I don't hear anyone else complaining about it. One thing I'll look in to is, alot of system files have invalid owner/group. (65535/65525, etc) Maybe there's a communication problem due to this. Bill -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE80AQDnQ18+PFcZJsRAvdzAJ0SSD45liz2+jNRd1eeAOH2Zlp+qwCfZtGP KJIIYeb1VHOr1Z7qWcyiFIc= =sr6q -----END PGP SIGNATURE-----