Created attachment 115383 [details] system log from crash Description of problem: This seems kind of weird, but I can reliably trigger a hang of the GUI on my system by running geeqie and right-clicking on the file list. The context menu comes up, but the mouse and keyboard immediately become nonresponsive. I can ssh in and reboot, though. Version-Release number of selected component (if applicable): xorg-x11-drv-nouveau-1.0.11-2.fc22.x86_64 How reproducible: Seems to be always. Steps to Reproduce: 1. run geeqie in a directory with a number of jpg files 2. right click on one of those files in the list 3. boom Actual results: mouse and keyboard freeze Expected results: not that. Additional info: system log is full of lines like: Apr 24 21:26:22 system.example.org kernel: nouveau E[ PFIFO][0000:01:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x001c data 0x00001004 Apr 24 21:26:22 system.example.org systemd-journal[477]: Missed 16 kernel messages Apr 24 21:26:22 system.example.org kernel: nouveau E[ PFIFO][0000:01:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x001c data 0x00001004 Apr 24 21:26:22 system.example.org systemd-journal[477]: Missed 16 kernel messages Apr 24 21:26:22 system.example.org kernel: nouveau E[ PFIFO][0000:01:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x001c data 0x00001004 Apr 24 21:26:22 system.example.org systemd-journal[477]: Missed 19 kernel messages Apr 24 21:26:22 system.example.org kernel: nouveau E[ PFIFO][0000:01:00.0] PBDMA0: ACQUIRE And by "full", I mean about 7.6 million lines of that in a few minutes -- so much that it seems to have wiped out previous log information by sheer volume, triggering systemd's log rotation. This didn't happen with Fedora 21. I'm running under GNOME Shell -- I have not tried other environments. A bug filed in Fedora https://bugzilla.redhat.com/show_bug.cgi?id=1215329 has additional logs from another tester who was able to reproduce.
I suspect you have libdrm-2.4.60? If so, please downgrade to 2.4.59.
I do. I'll try that -- thanks.
I can confirm that the crash does not seem to occur with libdrm 2.4.59. Does that make this a libdrm bug, then?
*** This bug has been marked as a duplicate of bug 89842 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.