| Summary: | ssytem-config-authentication can't open display (?!) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Horst H. von Brand <vonbrand> | ||||||
| Component: | xfce4-session | Assignee: | Kevin Fenzi <kevin> | ||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | jones.peter.busi, kevin, tmraz | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-03-12 23:30:10 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
There is hardly anything really related to authconfig in this bug. The glitch is probably related either to XFCE or usermode but the "permissions problems" seem like to be the source of the problems. How did you login to Xfce? Is this f14 branched or rawhide? what does ck-list-sessions show? (In reply to comment #2) > How did you login to Xfce? Via XDM, had selected XFCE via switchdesk (Gnome et al busted right now; GDM doesn't work at all). > Is this f14 branched or rawhide? Rawhide [Perhaps need to add "Branched" to the distro version selection?] > what does ck-list-sessions show? $ ck-list-sessions Session1: unix-user = '501' realname = 'Horst H. von Brand' seat = 'Seat2' session-type = '' active = FALSE x11-display = ':0' x11-display-device = '/dev/tty2' display-device = '' remote-host-name = '' is-local = FALSE on-since = '2011-02-23T12:01:37.601885Z' login-session-id = '2' Yeah, so consolekit isn't showing you as local. I wonder if it's some xdm issue? Try stopping xdm and all gui, then just do a 'startx' from a vty. Does that work? Created attachment 480568 [details]
Output from startx
Went to runlevel 3, and as myself I ran startx. No dice, startx failed with the attached output.
(In reply to comment #5) > Created attachment 480568 [details] > Output from startx > > Went to runlevel 3, and as myself I ran startx. No dice, startx failed with the > attached output. There us no /bin/dbus-launch here, it is in /usr/bin; "rpm -V dbus dbus-x11" comes up clean (dbus-1.4.0-3.fc15.x86_64, dbus-x11-1.4.0-3.fc15.x86_64). (In reply to comment #1) > There is hardly anything really related to authconfig in this bug. The glitch > is probably related either to XFCE or usermode but the "permissions problems" > seem like to be the source of the problems. Yep, usermode-1.106.1-3.fc15.x86_64 and ConsoleKit-0.4.3-3.fc15.x86_64 install date matches the start of my troubles. Then again, I was out for a week, so that was a monster update :-( Thats... deeply odd. Is selinux enabled? If you create a new user and login as them and run startx does it work? (In reply to comment #8) > Thats... deeply odd. ;-) > Is selinux enabled? Yes. I disabled it and rebooted. Now system-config-authentication works. The other stuff that is shot (NetworkManager, mounting USB pendrives) is still kaputt. $ ck-list-sessions Session3: unix-user = '501' realname = 'Horst H. von Brand' seat = 'Seat4' session-type = '' active = FALSE x11-display = ':0' x11-display-device = '/dev/tty3' display-device = '' remote-host-name = '' is-local = FALSE on-since = '2011-02-24T00:28:30.592273Z' login-session-id = '3' > If you create a new user and login as them and run startx does it work? (In reply to comment #8) > Thats... deeply odd. ;-) I ran "rpm -Va", found a few packages that had problems: gnome-themes openvpn sbcl filesystem smolt hal plymouth mdadm gdm flac "yum -y reinstall" all those didn't fix all the reported problems (none that looked relevant), and it didn't fix the current mess either. > Is selinux enabled? Yes. I disabled it and rebooted. Now system-config-authentication works. The other stuff that is shot (NetworkManager, mounting USB pendrives) is still kaputt. $ ck-list-sessions Session3: unix-user = '501' realname = 'Horst H. von Brand' seat = 'Seat4' session-type = '' active = FALSE x11-display = ':0' x11-display-device = '/dev/tty3' display-device = '' remote-host-name = '' is-local = FALSE on-since = '2011-02-24T00:28:30.592273Z' login-session-id = '3' > If you create a new user and login as them and run startx does it work? Created a new user, same results as with my account, both with Gnome (starts fallback) and XFCE. ck-list-sessions also says it isn't local. This is driving me nuts. I'm seriously considering reinstalling... BTW, for some unfathomable reason there are no VTs on this machine, I've to run openvt from a root shell under X to get some. Makes futzing around painful... After updating some stuff I had to relabel for SELinux, after that I'm back at square one: SELinux definitely stops s-c-a from working (that is rather secondary for me) but doesn't affect NetworkManager or a lot of other brokeness (presumably since I'm not local). Just tried booting the exact same machine with gfx_test_week_20110221_x86-64.iso (to check whether this is a problem with the machine), there ch-list-sessions says the user is local. Huh. So somehow your local install has a messed up consolekit or config that consolekit reads. ;( Try reinstalling or downgrading ConsokeKit? OK, did run "rpm -V ConsoleKit", is clean (not even configuration file changes). Reinstalled anyway, still the same. BTW, my VT problems were due to a somehow botched systemd install. Fixed that one. Created attachment 480883 [details]
File .xsession-errors from last login
(In reply to comment #13) > Huh. So somehow your local install has a messed up consolekit or config that > consolekit reads. ;( > > Try reinstalling or downgrading ConsokeKit? No downgrade available for ConsoleKit. Those are the versions I've got here since February 24...
# rpm -q ConsoleKit{,-libs,-x11}
ConsoleKit-0.4.3-3.fc15.x86_64
ConsoleKit-libs-0.4.3-3.fc15.x86_64
ConsoleKit-x11-0.4.3-3.fc15.x86_64
(In reply to comment #19) > Those are the versions I've got here since February 24... Sorry, make that February 12 (or so), I reinstalled CK yesterday. "rpm -V ConsoleKit{,-libs,-x11}" comes up clean. Try a: yum --enablerepo=updates-testing update ConsoleKit\* and see if it helps any? (In reply to comment #21) > Try a: > > yum --enablerepo=updates-testing update ConsoleKit\* > > and see if it helps any? # yum --enablerepo=updates-testing update ConsoleKit\* Loaded plugins: presto updates-testing/metalink | 18 kB 00:00 Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=updates-testing-f16&arch=x86_64 error was No repomd file Error: Cannot retrieve repository metadata (repomd.xml) for repository: updates-testing. Please verify its path and try again So, nope ;-) Just got 0.4.4-1.fc15 from koji, will try that one for size. *** Bug 679392 has been marked as a duplicate of this bug. *** More random experiments... Went to runlevel 3: #telinit 3 Logged into a VT as myself, tried startx. That one spews errors on "No protocol" (or some such). Tried startxfce4 (dimly remembered from _way_ back). Success!! Now I'm a local user (sort of): ]$ ck-list-sessions Session1: unix-user = '501' realname = 'Horst H. von Brand' seat = 'Seat1' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/tty2' remote-host-name = '' is-local = TRUE on-since = '2011-02-26T01:40:55.275771Z' login-session-id = '2' idle-since-hint = '2011-02-26T01:48:22.055863Z' Session2: unix-user = '0' realname = 'root' seat = 'Seat1' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/tty3' remote-host-name = '' is-local = TRUE on-since = '2011-02-26T01:42:11.846793Z' login-session-id = '3' idle-since-hint = '2011-02-26T01:46:51.056276Z' NetworkManager works as it should, etc. Well, startxfce4 will use xinit if needed... but I still have no idea why startx or gdm is failing in this way for you. ;( (In reply to comment #25) > Well, startxfce4 will use xinit if needed... but I still have no idea why > startx or gdm is failing in this way for you. ;( gdm is busted on that machine, it just gives a black screen. That's why I'm using XDM. I'll have to try with the newest xorg driver and stuff. Re #24: NM works "sort of", I can't select e.g.System eth0 (the default eth0 is configured manually for work), but it gets wlan0 automatically without a hitch (and it seems I can configure connections). At this point I am going to just suggest a clean install... there's clearly some config or the like lingering there thats just breaking consolekit. ;( I'm not sure how to track down the issue further... (In reply to comment #27) > At this point I am going to just suggest a clean install... there's clearly > some config or the like lingering there thats just breaking consolekit. ;( > > I'm not sure how to track down the issue further... Too bad this is after the branch, so there are no LiveCDs available for rawhide ('net install is just too slow/unreliable here). Any areas where I could compare this machine with another, working one? Thanks! Are you wanting to end up on rawhide? or branched 15? Reading back you are on rawhide/f16? I wonder if thats part of the issue, as some builds are getting done only for f15 and only inherit into rawhide when they reach stable, which they have not done lately since we are in alpha freeze. ;( So, perhaps as soon as things unfreeze and you get the big update after that things will go back to more normal... (In reply to comment #29) > Are you wanting to end up on rawhide? or branched 15? > > Reading back you are on rawhide/f16? Yes > I wonder if thats part of the issue, as > some builds are getting done only for f15 and only inherit into rawhide when > they reach stable, which they have not done lately since we are in alpha > freeze. ;( So, perhaps as soon as things unfreeze and you get the big update > after that things will go back to more normal... OK, will sit it out a few more days... trying to create rawhide install images fails currently (Bz #681003). (In reply to comment #22) > (In reply to comment #21) > > Try a: > > > > yum --enablerepo=updates-testing update ConsoleKit\* Just noticed that this should have been # yum --releasever=15 --enablerepo=updates-testing update ConsoleKit\* Yeah, if you are on rawhide. ;( I missed that and thought you were on f15. ;( Now it works in XFCE4 started via startxfce4, ck-list-sessions shows me as local, and NetworkManager is able to handle the network. Still broken the exact same way in Gnome, though. Bit the bullet and just installed Fedora 15 alpha from scratch on that machine. This nonsense is gone now. Thanks, and sorry for wasting your time. No problem. Sorry this was such a puzzler. ;( Glad it's all working with a fresh install... I have no idea what was messed up. ;( |
Description of problem: Running system-config-authentication in a Terminal under XCFE gives: $ system-config-authentication Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyTraceback (most recent call last): File "/usr/share/authconfig/authconfig-gtk.py", line 27, in <module> import msgarea File "/usr/share/authconfig/msgarea.py", line 19, in <module> import gtk, gobject File "/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 64, in <module> _init() File "/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 52, in _init _gtk.init_check() RuntimeError: could not open display Version-Release number of selected component (if applicable): authconfig-gtk-6.1.13-1.fc15.x86_64 How reproducible: Tried once via menu, then in a Terminal Steps to Reproduce: 1. system-config-authentication 2. Give root password 3. Actual results: Traceback Expected results: Configure authentication... Additional info: This account seems to have some permissions problems (NetworkManager doesn't configure interfaces, wodim can't open /dev/cdrw, system-config-users shows similar problems)