Red Hat Bugzilla – Bug 490460
liveinst not starting in graphical mode
Last modified: 2014-06-18 05:11:02 EDT
Description of problem: When trying to start liveinst through it's menu icon I receive this error in my .xsession-errors: kdeinit4: preparing to launch /usr/bin/liveinst 0 logical volume(s) in volume group "Volg1" now active 15:33:22 Starting graphical installation... No protocol specified 15:33:23 Exception starting GUI installer: could not open display 15:33:23 GUI installer startup failed, falling back to text mode. TERM environment variable needs set. Version-Release number of selected component (if applicable): anaconda-11.5.0.30-1.x86_64 How reproducible: ever Steps to Reproduce: 1. create recent KDE live image 2. boot this image 3. start liveinst through the menu or desktop icon Actual results: liveinst fails to start Expected results: liveinst starts Additional info: I've also tried to start "liveinst --graphical" in a terminal. One time it succeeds to start (and the it was also possible to start it through the desktop icon). The other 5-6 times it fails and started the text mode instead. I wasn't able to find out why it started this one time only.
If you su to root in a terminal, can you (eg) launch an xterm?
Mhh, I can't: [root@work liveuser]# xterm No protocol specified Warning: This program is an suid-root program or is being run by the root user. The full text of the error or warning message cannot be safely formatted in this environment. You may get a more descriptive message by running the program as a non-root user or by removing the suid bit on the executable. xterm Xt error: Can't open display: %s
Happening also with the desktop live image. Reassigning to libXau as it changed last week and sounds like it could suspiciously be related. The actual component to be fixed, though, might be that pam_xauth needs updating for the libXau changes so also cc'ing tmraz
pam_xauth does not call libXau directly. It execs xauth to copy the cookie.
Adam -- any thoughts?
So, that change was put in to work around networkmanager enthusiastically changing the hostname out from under you. But I think the change implements the wrong thing; it should really only do the sloppy (non-hostname-sentitive) match if it couldn't find a strict match. Maybe. Need to think about it more. Reverted in 1.0.4-5 at any rate.
Tested with the new bits on Friday and installs work again. Thanks ajax
Cannot confirm this with a KDE live image. I'm still unable to start graphical apps as root. The changes from friday were mostly gdm related. So does kdm also needs to be fixed?
The change was in libXau, not gdm. So it should be applicable for both. Does your image have libXau-1.0.4-5?
Just built a kde live image and it worked fine (with libXau-1.0.4-5)
Yes, libXau-1.0.4-5 is included (for all included packages see: http://www.deadbabylon.de/fedora/livecd/packagelists/f11/long-F11-KDE-053-i686.txt). I've also created a Desktop spin and there it works, but not on the kde one.
Mhh. Strange. It does work if I boot from a cd. It does not work If I boot from a local partition or an usb stick. But the same usb stick is working fine on my EEE.
sebastian, can you check this again? it's on the preview release blocker list. you could test with the Snapshot image, I think. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Sure, sorry for the delay: It's fixed now (tested with a live image from yesterday).