Created attachment 861228 [details] First crash systemd log Description of problem: install/uninstall of samba triggers system crash Version-Release number of selected component (if applicable): Not sure what component this bug is really due to. Here are the ones that are mentioned in the system log yum-3.4.3-132.fc20.src.rpm systemd-208-9.fc20.src.rpm PackageKit-0.8.16-1.fc20.src.rpm How reproducible: Very Steps to Reproduce: 1. sudo yum -y install samba or 1. sudo yum remove samba Actual results: System crash after samba installed or removed. Expected results: Samba installed or removed without system crash Additional info: I installed samba, system crashed. Posted to fedora users mailing list asking for help, 2 days later, no suggestions other than it could be systemd. I did yum remove samba so I could then install it again and see if it would repro, but the system crashed in just about the same way on uninstall, and I considered that was enough reproing. Ctrl-alt-f2 did not work to bring up a terminal and I had to hold the power button down to shutdown the machine. I know this bug is a big sparse, I'm not sure how to debug this issue, which is why I asked on the fedora users list, but got no help. I'd like to help figure out the root cause of this. I can only add 1 attachment when filing the bug, but I am uploading the second log and pictures.
Created attachment 861229 [details] Second crash. yum remove samba
Created attachment 861230 [details] display on first crash Bad pictures, but I thought it worth noting that the display was different each time.
Created attachment 861231 [details] display on second crash
Created attachment 861666 [details] 3rd crash after installing ntp
It seems this is unrelated to samba, as the next package I installed, ntp, triggered the same system freeze, and I've attached the log.
Note, between the first 2 freezes, I installed some packages without a problem. I'm going to make a separate fedora install on a different partition so that hopefully with someone here's help I can use this messed up one to investigate further.
I have a suspicion that because I am running Xmonad, the system freezes, where it may have recovered to the login screen otherwise, like in this bug I recently filed: https://bugzilla.redhat.com/show_bug.cgi?id=1064741 Using the Xmonad quit function also causes a system freeze. Installing/removing packages seems to intermitendly cause this bug, so I can't reliably repro it.
Hi Ian, what do you mean by "crash"? I don't see anything interesting in the logs you attached.
Hi Zbigniew. By crash, I mean that the screen becomes locked in a static image like those attached to the bug, and the only way out is to hold down the power button / physically cut the power then restore it to do a reboot. Can you suggest a different log file which might be helpful, or some steps / approach I could take to investigate this further?
Does the magic sysreq stuff still work if it hangs like you describe?
It's been long enough that I can't remember. I will be sure to document that it in the future. I did repro it on 2 separate installs when I filed htis, albeit the same machine. I went to repro it again over the weekend, 2 installs, no repro. So, closing this, and back to using fedora 20 again.