Description of problem: Xorg hangs when on libre office when trying to copy/paste a document Version-Release number of selected component (if applicable): kernel-3.18.9-100.fc20.x86_64 kernel-3.18.7-100.fc20.x86_64 xorg-x11-drv-nouveau-1.0.9-2.fc20.x86_64 How reproducible: always Steps to Reproduce: 1.load libre office 2.type some words 3.highlight and select copy, then click a menu option. Actual results: xorg hangs, no alternate consoles. Mouse cursor still moves. Expected results: normal operation Additional info: kernel-3.17.x works fine
Created attachment 1006465 [details] xorg.0.log from crash Doesn't log the crash, but should provide info about Xorg
Probably duplicate of bug #1203023 (so it's in F21 too) (P.S. I couldn't reproduce this bug on my setup)
Just checked kernel-3.19.4. Still broken. Last working kernel is 3.17.7-200. lspci from 64-bit laptop that fails with recent kernels: 01:00.0 VGA compatible controller: NVIDIA Corporation G98M [Quadro NVS 160M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device 024f Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at f5000000 (32-bit, non-prefetchable) [size=16M] Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f2000000 (64-bit, non-prefetchable) [size=32M] I/O ports at df00 [size=128] [virtual] Expansion ROM at f4000000 [disabled] [size=128K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Kernel driver in use: nouveau Kernel modules: nouveau I tested on a 32-bit desktop with nvidia, and it did not fail. lspci on the desktop: 01:00.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev a1) (prog-if 00 [VGA controller]) Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16 Memory at fc000000 (32-bit, non-prefetchable) [size=16M] Memory at e0000000 (32-bit, prefetchable) [size=256M] Memory at fd000000 (32-bit, non-prefetchable) [size=16M] Expansion ROM at fea00000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: nouveau Kernel modules: nouveau
I tested highlighting just a single line of text - that was insufficient to cause the failure. I need to highlight at least a paragraph, then click on the menu to cause the failure.
I set the severity to HIGH because the laptop is unusable with this bug. The only workaround is to keep running kernel-3.17.7, and that is getting long in the tooth.
journalctl -b -1 around time of clicking menu with a paragraph highlighted (11:35:25): Apr 24 11:33:52 gail.gathman.org gnome-session[1687]: Window manager warning: Log level 16: STACK_OP_RAISE_ABOVE: sibling window 0x1200001 not in stack Apr 24 11:34:31 gail.gathman.org gnome-session[1687]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Apr 24 11:34:55 gail.gathman.org gnome-session[1687]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Apr 24 11:35:25 gail.gathman.org kernel: nouveau E[ PFIFO][0000:01:00.0] still angry after 101 spins, halt Apr 24 11:35:25 gail.gathman.org kernel: nouveau E[ PFIFO][0000:01:00.0] still angry after 101 spins, halt Apr 24 11:35:25 gail.gathman.org kernel: nouveau E[ PFIFO][0000:01:00.0] still angry after 101 spins, halt Apr 24 11:35:25 gail.gathman.org kernel: nouveau E[ PFIFO][0000:01:00.0] still angry after 101 spins, halt Apr 24 11:35:25 gail.gathman.org kernel: nouveau E[ PFIFO][0000:01:00.0] still angry after 101 spins, halt Apr 24 11:35:32 gail.gathman.org kernel: nouveau E[ PFIFO][0000:01:00.0] still angry after 101 spins, halt Apr 24 11:35:32 gail.gathman.org kernel: nouveau E[ PFIFO][0000:01:00.0] still angry after 101 spins, halt Apr 24 11:35:32 gail.gathman.org kernel: nouveau E[ PFIFO][0000:01:00.0] still angry after 101 spins, halt Apr 24 11:35:44 gail.gathman.org sh[812]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input Apr 24 11:35:46 gail.gathman.org sh[812]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input Apr 24 11:35:48 gail.gathman.org sh[812]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input Apr 24 11:35:50 gail.gathman.org sh[812]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input Apr 24 11:35:55 gail.gathman.org sh[812]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input Apr 24 11:35:57 gail.gathman.org sh[812]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input Apr 24 11:35:59 gail.gathman.org sh[812]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input
Another difference: the non-working system is using gnome-shell, the working nvidia desktop is running MATE. Although the problem is clearly kernel related (goes away with 3.17.x kernels), there could be an interaction with the window manager as well.
I get this freeze almost once a day, always when using Libreoffice, really bad. Kernel 3.19.5-100, F20, 64-bit. Any workaround besides replacing with nvidia driver?
(In reply to TL from comment #8) > I get this freeze almost once a day, always when using Libreoffice, really > bad. Kernel 3.19.5-100, F20, 64-bit. Any workaround besides replacing with > nvidia driver? Use a 3.17.x kernel. That is my work around. Disappointing that such a major regression has continued through so many kernel releases. If only I had encountered that problem in time to block release of the 3.18 kernels. But I was too excited about the intel driver problems made less bad by 3.18. :-)
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.