Red Hat Bugzilla – Bug 810451
Logging out crashes i686 LiveCD system
Last modified: 2012-06-15 20:16:31 EDT
Description of problem:
I booted F17 Beta RC3 i686 LiveCD system in virt-manager and wanted to re-login. My use case was to force fallback mode, which needs logging out and in again. After logging out, there was a brief flash of new X/gdm spawning (black screen with rotating cursor) and then X probably crashed (graphics errors displayed for a short time) and the whole VM shut down. I reproduced it many times. The VM either shuts down completely, or X/gdm crashes several times and then I appear logged in again on display :1. There is a selinux error displayed, bug 810447. I never logged out correctly.
I tried the same on x86_64 LiveCD and logging out worked flawlessly there. It means it's a problem of i686 only.
I can't collect any logs when the VM shuts down completely. So I at least collected some logs when X/gdm crashed repeatedly, but then logged me again.
I tried both qxl+spice and cirrus+vnc, happens in both. I didn't test on bare metal machine, I'll try to do that.
Version-Release number of selected component (if applicable):
Fedora 17 Beta RC3 LiveCd *i686*
Steps to Reproduce:
1. boot i686 livecd
2. select Log out
3. see either VM shut off or X crashes and then automatic log-in again
Created attachment 575654 [details]
Created attachment 575655 [details]
Created attachment 575656 [details]
Created attachment 575657 [details]
Created attachment 575658 [details]
Created attachment 575659 [details]
Created attachment 575660 [details]
Created attachment 575661 [details]
Created attachment 575662 [details]
Created attachment 575663 [details]
Created attachment 575664 [details]
Created attachment 575665 [details]
Created attachment 575666 [details]
What I see in the logs:
[ 51.077447] gnome-shell: segfault at 0 ip 01df70dd sp bffcdb00 error 4 in libaccountsservice.so.0.0.0[1de4000+39000]
[ 52.805] Server terminated successfully (0). Closing log file.
Server terminated successfully (0). Closing log file.
gdm-autologin]: pam_unix(gdm-autologin:session): session closed for user liveuser
gdm-simple-slave: WARNING: Child process 1052 was already dead.
gdm-simple-slave: WARNING: Unable to kill session worker process
Proposing as Beta blocker due to criterion:
"All release-blocking desktops' offered mechanisms (if any) for shutting down, logging out and rebooting must work"
This is confirmed to be broken just on the LiveCD system, I haven't tested on installed system (I'll try that soon). But I believe there are valid use cases even on livecd system to log out (e.g. changing desktop to fallback mode if there are some rendering problems). LiveCDs are often used for fixing broken systems, therefore hard shutdown without unmounting disks correctly could be potentially harmful.
This *does not* happen in an installed system in the exactly same VM from that particular LiveCD, only in the live environment itself.
I can reproduce this on bare-metal machine with i686 LiveCD dd'd to USB stick. However, it never powered-off hard for me, it always just respawned another desktop session with liveuser automatically logged in.
It has one further drawback however - you can't power off the system, if you don't know the hidden Alt key in GNOME's user menu. Logging out doesn't work -> no poweroff/restart options visible.
I can confirm this. I've got the same result with liveCD in KVM.
I reproduced this as well. If I add 'selinux=0' to the boot args, I can logout of the live session without issue.
re-assigning to selinux-policy.
Fedora Bugzappers volunteer triage team
The AVC for this has been reported as https://bugzilla.redhat.com/show_bug.cgi?id=810447 . Marking that as a dupe of this.
*** Bug 810447 has been marked as a duplicate of this bug. ***
Is this really SELinux issue? I am not able to reproduce it. I am able to log out/in in either enforcing or permissive mode.
I see the same AVC msg. This tells me that gdb is executed by xdm_t because of a crash.
(In reply to comment #23)
> Is this really SELinux issue? I am not able to reproduce it. I am able to log
> out/in in either enforcing or permissive mode.
Which livecd are you using? This only seems to affect i686, not x86_64.
When I try with the F17 beta RC3 Desktop i686 livecd, I see the problem almost every time I log out unless I used 'selinux=0' at boot time.
I use the same from
could you boot with enforcing=0 and then
$ semodule -DB
$ ausearch -m avc -ts recent |audit2allow
Created attachment 575843 [details]
syslog when error on logout causes machine restart
(In reply to comment #25)
> could you boot with enforcing=0 and then
> $ semodule -DB
> $ ausearch -m avc -ts recent |audit2allow
I tried this the livecd with enforcing=0 and ran semodule -DB. Every time I logged out, the VM that the livecd is in restarted and I can't run the second command.
I tried again, tailing the system log on a serial console when I logged out and was able to capture a gdm crash.
Ok, I see it now.
My observation is the following:
This happens either enforcing or permissive mode. This does not happen with selinux=disabled.
Could this be accountsservice or gdm doing a libselinux call and crashing?
A little late but:
This bug was discussed at the 2012-04-06 Fedora 17 beta blocker review meeting.
We agreed to accept this as a blocker for Fedora 17 beta due to conditional
violation (i686 Live CD) of the following Fedora 17 beta release criterion 
All release-blocking desktops' offered mechanisms (if any) for shutting down,
logging out and rebooting must work
(In reply to comment #29)
> Could this be accountsservice or gdm doing a libselinux call and crashing?
Yes, this is also my suspect.
We have found the problem in gdm, totally unrelated to SELinux. The problem arises from the move from consolekit to systemd-login for discovering the seats associated with a logged in user. Ray is fixing it now.
gdm-188.8.131.52-4.fc17 has been submitted as an update for Fedora 17.
I built a test live image with the new gdm, and it still appears to be broken. Ray is investigating further.
Fedora Bugzappers volunteer triage team
(In reply to comment #32)
> We have found the problem in gdm, totally unrelated to SELinux.
Maybe that's a different problem? Because this one is supposed to be influenced by selinux=disabled.
The gdm problem is random since he was walking off into memory, perhaps changing the SELinux settings changed the way memory was layed out and you don't hit the problem. But I believe this issue has nothing to do with SELinux.
gdm-184.108.40.206-5.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gdm-220.127.116.11-5.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
fixed the issue here (can log out and back in on the live cd).
I added karma on bodhi, just posting here as this bug is listed as a Beta blocking bug.
Fedora Bugzappers volunteer triage team
Just commenting that I upgraded an installed F17 i686 (with selinux disabled) to gdm-18.104.22.168-4.fc17 and it crashed at login. I had to downgrade back to gdm-22.214.171.124-1.fc17
I'm waiting now for gdm-126.96.36.199-5.fc17 to be available here.
gdm-188.8.131.52-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 810137 has been marked as a duplicate of this bug. ***
gdm-3.4.1-1.fc17 has been submitted as an update for Fedora 17.
gdm-3.4.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
This actually happened when I logged in to Fedora 17 64 bit on a regular systems. Please let me know if I can get additional information for you.