Konq & Launching External Apps
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 . Running Suse8 with all current updates. Since I've installed this I have not been able to launch apps from Konqsu. I'm logged in as a user, and it is my practice to have a root Konq window open for operations. When I right-click on a file and try to edit, it says KDEInit failed to initiate. Same problem in konsolesu. Here's an example: hydra:/usr/java/j2sdk1.4.0/demo/jfc/Notepad # java -jar Notepad.jar Xlib: connection to ":0.0" refused by server Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison) uncaught exception: java.lang.InternalError: Can't connect to X11 window server using ':0' as the value of the DISPLAY variable. java.lang.InternalError: Can't connect to X11 window server using ':0' as the value of the DISPLAY variable. at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method) at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:126) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:130) at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:62) at java.awt.Window.init(Window.java:208) at java.awt.Window.<init>(Window.java:252) at java.awt.Frame.<init>(Frame.java:398) at java.awt.Frame.<init>(Frame.java:363) at javax.swing.JFrame.<init>(JFrame.java:154) at Notepad.main(Notepad.java:100) hydra:/usr/java/j2sdk1.4.0/demo/jfc/Notepad # Looks like a security issue. Does anyone understand this error? (is anyone else _getting_ this error?) I'm quite sure this error is at the heart of the launch problem. This command works fine from a user konsole, but fails in su. I also cannot get Java's look & feel plugin, which translates K styles, to work. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE82TeSnQ18+PFcZJsRAu0oAJsGq8Afqvk+L/vZ9hATWNfOnHcn3wCfY0il 2BSc3Egxtw+XSIAtmU5YuOQ= =fQzc -----END PGP SIGNATURE-----
On Wednesday 08 May 2002 16:34, AnonymousCoward wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
. Running Suse8 with all current updates.
Since I've installed this I have not been able to launch apps from Konqsu. I'm logged in as a user, and it is my practice to have a root Konq window open for operations.
Same problem in konsolesu. Here's an example:
hydra:/usr/java/j2sdk1.4.0/demo/jfc/Notepad # java -jar Notepad.jar Xlib: connection to ":0.0" refused by server Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison) uncaught exception: java.lang.InternalError: Can't connect to X11 window server using ':0' as the value of the DISPLAY variable. java.lang.InternalError: Can't connect to X11 window server using ':0' as
If you want to run graphical applications as root (thru su), you need to execute: xhost +localhost Add it to your ~/.profile if you want to make it permanent.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 08 May 2002 10:55, you wrote:
On Wednesday 08 May 2002 16:34, AnonymousCoward wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
. Running Suse8 with all current updates.
Since I've installed this I have not been able to launch apps from Konqsu. I'm logged in as a user, and it is my practice to have a root Konq window open for operations.
Same problem in konsolesu. Here's an example:
hydra:/usr/java/j2sdk1.4.0/demo/jfc/Notepad # java -jar Notepad.jar Xlib: connection to ":0.0" refused by server Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison) uncaught exception: java.lang.InternalError: Can't connect to X11 window server using ':0' as the value of the DISPLAY variable. java.lang.InternalError: Can't connect to X11 window server using ':0' as
If you want to run graphical applications as root (thru su), you need to execute: xhost +localhost Add it to your ~/.profile if you want to make it permanent.
Thank you *very* much. You just relieved my worst headache. I put this in /etc/profile.local . (And yeah I agree, fsckMicrosoft) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE82Vq8nQ18+PFcZJsRAvHUAJ4r9SpC6OVm6KxGVYRCBL4hIjtiWACeL0qt 1n6e/jKn4wj8NjPkLgHYPHo= =vinM -----END PGP SIGNATURE-----
On Wed, 8 May 2002, Sagdalon wrote:
On Wednesday 08 May 2002 16:34, AnonymousCoward wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
. Running Suse8 with all current updates.
Since I've installed this I have not been able to launch apps from Konqsu. I'm logged in as a user, and it is my practice to have a root Konq window open for operations.
Same problem in konsolesu. Here's an example:
hydra:/usr/java/j2sdk1.4.0/demo/jfc/Notepad # java -jar Notepad.jar Xlib: connection to ":0.0" refused by server Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison) uncaught exception: java.lang.InternalError: Can't connect to X11 window server using ':0' as the value of the DISPLAY variable. java.lang.InternalError: Can't connect to X11 window server using ':0' as
If you want to run graphical applications as root (thru su), you need to execute: xhost +localhost Add it to your ~/.profile if you want to make it permanent.
Yes, and you will have to "export DISPLAY=:0.0" from the root login, as well. Another way in your root console is: # xauth merge /home/username/.Xauthority # export DISPLAY=:0.0 This will not require opening up xsessions to everyone via xhost+. Regards, Robb -- Robb Romans Linux Commando k i l l s o f t .com "so then let us not sleep as others do, but let us be alert and sober." 1 Thessalonians 5:6
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 .
Yes, and you will have to "export DISPLAY=:0.0" from the root login, as well.
Another way in your root console is: # xauth merge /home/username/.Xauthority # export DISPLAY=:0.0
This will not require opening up xsessions to everyone via xhost+.
Regards, Robb
Dude you might have lost me here. I understand these need to be entered in a root console, but I can't fathom what they do. And presumably the 'export DISPLAY' command would have to be done on every reboot? The terms "opening up xsessions" and "via xhost+" are unfamiliar. Any enlightenment appreciated. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE82XeBnQ18+PFcZJsRApAEAJ0eOEbNKrrN1fJUgnF+0T47pjO9JwCeIAyX uC5lz81ELWUySpSyFxqb3y0= =Cc8T -----END PGP SIGNATURE-----
On Wed, 8 May 2002, AnonymousCoward wrote:
Yes, and you will have to "export DISPLAY=:0.0" from the root login, as well.
Another way in your root console is: # xauth merge /home/username/.Xauthority # export DISPLAY=:0.0
This will not require opening up xsessions to everyone via xhost +.
Regards, Robb
Dude you might have lost me here.
I understand these need to be entered in a root console, but I can't fathom what they do. And presumably the 'export DISPLAY' command would have to be done on every reboot?
The first xwindows session started, whether via the startx command or on boot via xdm, kdm, etc., is almost always named 0.0 When you execute a graphical program as another user than whom started the windowmanager, you need to tell the program what display to run on - hence the "export DISPLAY=:0.0" And no, environment variables like DISPLAY do not survive a reboot unless they are picked up on login from a file like .profile. Each xsession, or more simply when you start a windowmanager, has a security token associated with it that is unique to the user who started it. The "xauth merge" command tells the xserver to combine the tokens and let the new user (root in this case) have access to the display. The reason I don't like the "xhost +localhost" command is that it lets ANY user access your screen if they know how and consequently see anything that you type. If you simply type "xhost +" as some suggest, you let ANY user on ANY machine whether local to that machine or any machine on the network (think Internet) access your display data. Better to use ssh -X (hint: rtfm) or the xauth command.
The terms "opening up xsessions" and "via xhost +" are unfamiliar. Any enlightenment appreciated.
I've tried to help and may have missed some details, so see the man pages if you want more. Regards, Robb -- Robb Romans Linux Commando k i l l s o f t .com "so then let us not sleep as others do, but let us be alert and sober." 1 Thessalonians 5:6
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 08 May 2002 15:48, Robb Romans wrote:
On Wed, 8 May 2002, AnonymousCoward wrote:
Yes, and you will have to "export DISPLAY=:0.0" from the root login, as well.
Another way in your root console is: # xauth merge /home/username/.Xauthority # export DISPLAY=:0.0
I agree with the security concern. I put the above into bash.bashrd.local, and logged off/restarted X, logged in. In konsolesu when I try to run an x proggie, I get hydra:/opt/kde3/bin # ./konqueror DCOPServer up and running. mcop warning: user defined signal handler found for SIG_PIPE, overriding /tmp/mcop-hydra is not owned by user zone still contained 10 blocks hydra:/opt/kde3/bin # Mutex destroy failure: Device or resource busy kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. kdeinit: sending SIGTERM to children. kdeinit: Exit. sh: dcopserver_shutdown: command not found (WTF?) And in konqsu when I right-click|Edit a file I get: KDEInit could not launch 'kdesu' I tried putting in bash.bashrd.local ssh -X -l root localhost but get only endless login dialogues. As I do not understand all the ins and outs, I can't diagnose. I do not understand why I could right-click and edit files with 7.2 and 7.3 . This inability is a real PITA. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE82pt1nQ18+PFcZJsRAt+8AJ46PC2eYMU2opjIVDs6uSlqg+//cgCeNf9u piA7Ss/G4CoZQOlILA8zDaI= =zy6s -----END PGP SIGNATURE-----
participants (3)
-
AnonymousCoward
-
Robb Romans
-
Sagdalon