Created attachment 842168 [details] output of journalctl -x Description of problem: Hard stop when I select a session after logging into XFCE. Same happened even when I selected "New Session" and typed in its name. Version-Release number of selected component (if applicable): kernel-3.12.6-200.fc19.x86_64 How reproducible: Intermittent. Seems to happen after shutting down for an hour or two, or more. Switching back to kernel-3.12.5-200.fc19.x86_64.debug #1 SMP Steps to Reproduce: 1. Boot and try to log into existing or new XFCE session Actual results: Hard stop, CTRL-ALT-DEL has no effect. Expected results: Normal boot. Additional info: output of journalctl-x, /var/log/messages, and dmesg
Created attachment 842169 [details] /var/log/messages showing hang in kernel
Created attachment 842170 [details] dmesg output on entering single mode after powering off and on after hang
Created attachment 845764 [details] dmesg output for kernel-3.12.6-300.fc20 Tried kernel-3.12.6-300.fc20. Yes I know one is not supposed to mix Fedora versions. After logging in, system seemed hung selecting existing XFCE version. After waiting for a minute or so, I was able to CTRL-ALT-F2 and get dmesg and /var/log/messages.
Created attachment 845766 [details] /var/log/messages
Created attachment 845777 [details] dmesg output for kernel-3.12.6-300.fc20 with nomodeset Tried again, setting nomodeset in command boot command line. Booted, logged in and shut down normally. The blue progress bar during startup showed the text "Fedora 19", and not "Fedora 20", as I had expected. Presumably, this text does not come from the kernel.
Created attachment 845778 [details] /var/log/messages for kernel-3.12.6-300.fc20.x86_64 with nomodeset
Still have the bug with kernel-3.12.7-200.fc19.x86_64. I've configured to use kernel-debug-3.12.7-200.fc19.x86_64, and I'll post more info.
Created attachment 851784 [details] /var/log/messages, replaced 2311 nulls with "<2311 nulls>" Booted kernel-3.12.7-200.fc19.x86_64 and system hung after I logged in and selected a session. Mouse did not move, and CTRL-ALT-Fn and CTRL-ALT-DEL had no effect. Pressed Power, producing the nulls in the original /var/log/messages near line 1320. Booted again in 3.12.7-200.fc19.x86_64.debug, and system is running normally.
Created attachment 851785 [details] Xorg.9.log when the system hung
Created attachment 851786 [details] Xorg.0.log when the system booted normally with 3.12.7-200.fc19.x86_64.debug
Created attachment 851787 [details] diff of Xorg.N.log's This diff shows significant differences between the Xorg.N.log files. I got it by doing "%s/[^]]*]//" to get rid of the timing at the start of each line. That's why the filenames have a ".t" at the end of their names. I'm surprised at how different the files are.
What's the most recent kernel that for sure didn't have this behavior? Can you test the last 3.11 kernel instead of 3.12? I'm seeing some weird oom problems with 3.12 and (possibly) XFCE, and oom can make things appear to freeze. Can you: grep oom-killer /var/log/messages* Sorry if this barking up the wrong tree, my bug may be completely unrelated, but best to rule it out.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.13.5-100.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.