On Tue, 2016-10-04 at 21:54 +0100, Tom Hughes wrote: > > It only ever happens on one of my machines, so it's obviously something > about the environment, possibly the graphics card as that's the only > machine I do this on that has nvidia graphics? > > The weird thing is that there was nothing particularly X related in the > update that caused it this morning. In fact systemd was probably about > the most low level thing that was in the update. We've pretty much pinned it down, now. The recipe is: hybrid graphics + systemd-udev update == X crash. That is, if there's a systemd-udev update in the dnf transaction, and the system has hybrid graphics, and X is running while the update runs, X will crash. If you're running the update in a VT, X will crash but the update will complete OK. If you run the update inside X, the update process will die when X crashes and your system will be left messed up. I'm gonna write up a blog post and spread the word about this a bit, I'll send the link shortly; if people could spread it around that'd be great. The bug reports are https://bugzilla.redhat.com/show_bug.cgi?id=1341327 ;(for the X side) and https://bugzilla.redhat.com/show_bug.cgi?id=1378974 ;(for the systemd side). We are going to try and ensure the bug doesn't affect F25 Beta installs. An update is pending for F24, but ironically (since the service restart is in %postun not %post), the transaction to apply the update will *suffer from* the problem; the update will only ensure that *subsequent* updates no longer trigger the problem. Thanks for the data everyone! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
