Description of problem: While working in Calc. Click on tab of current spreadsheet to move it to a different position. System freezes. Mouse still moves, but no action possible. Had to power down and restart. Version-Release number of selected component (if applicable): Version: 4.1.2.3 Build ID: 4.1.2.3-3.fc19 How reproducible: Appears to be reproducible. Happened twice in a row to me. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Sounds more like an X or Window manager problem if the entire GUI appears to freeze. An application shouldn't be able to do that. Is it really reproducible, always, or always only with a specific document?
I tested it with an empty new spreadsheet, added a tab and then moved it. Same thing. The little tab symbol attaches to the mouse cursor and that is the end of the story. Mouse still moves but you cannot "click" the tab in a new place. I wonder if this could be related to Bug 983834. (No real insights though, I am just a simple Linux user who gave up on Windows a dew years ago.) I will also upload a video taken with my phone (all else failed since I needed to shut PC off)
I tested it with an empty new spreadsheet, added a tab and then moved it. Same thing. The little tab symbol attaches to the mouse cursor and that is the end of the story. Mouse still moves but you cannot "click" the tab in a new place. I wonder if this could be related to Bug 983834. (No real insights though, I am just a simple Linux user who gave up on Windows a dew years ago.) I also uploaded a video taken with my phone (all else failed since I needed to shut PC off) to a public dropbox folder: https://dl.dropboxusercontent.com/u/16233879/20131017_124716.mp4
I tested this same problem on Fedora 19 and 20 Rawhide with HD7870 running RadeonSI driver and could replicate the OP comment. I note that calc is slower to start than usual as well. I then tested under Fedora 19 with AMD Catalyst (proprietary) driver and note that start times for calc improved along with tab manipulation. I think that in my case, something is amiss with the RadeonSI drivers as I have been able to replicate this to other distros with the RadeonSI driver.
As at 1 December, after a full update on Fedora 20 Rawhide (amd64 architecture), this problem remains. Probably could do with a way-ahead from the assigned developer since release is not far away. - Damien
My colleague is also having severe problems with libreoffice and radeonsi. - Covering part of a sheet and exposing it can take 10-20 seconds to "repaint". - calc takes many times as long to open as it should. Booting with module.blacklist=radeon on the kernel cmd line makes the problems go away, but the dual monitors are stuck in "mirror" mode so it's not a viable workaround. Also found: in gnome settings panel, some panels show black areas instead of background & title bar. Chipset is (from Xorg.0.log): [ 37.632] (--) RADEON(0): Chipset: "VERDE" (ChipID = 0x683d) Willing to do any experimenting to get to the bottom of this.
And I can confirm what was stated in comment#4: all problems disappear using catalyst driver. see https://fedoraproject.org/wiki/Fglrx
I see no such resolution by adding module.blacklist=radeon on the kernel cmd line. I suspect David Mansfield had the fglrx driver also installed, thereby having using the fglrx driver once the module.blacklist=radeon option had been executed.
I mistyped it, actually. It's modprobe.blacklist=radeon Sorry. fglrx was 100% for sure not installed at the time. FYI Blacklisting radeon had 3 effects: 1) blue one-line progress bar in text mode during boot (if you don't see this, it didn't get blacklisted) 2) no dual head support 3) no slowness problems in oocalc or graphical articfacts in control center
David, Thanks for the update; I will take a look at this later today. Did you find that you get the correct native resolution for the monitor? Can you give the result of (as a normal user in X): glxinfo |grep -i opengl
I have done this myself and found: glxinfo |grep -i opengl OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 256 bits) OpenGL version string: 2.1 Mesa 9.2.4 OpenGL shading language version string: 1.30 OpenGL extensions: Also, latency has gone with Calc, but at the expense of hardware accelerated 3D rendering as indicated above by llvmpipe which is the just in time software renderer.
Also note with the above workaround, that kernel modesetting is unavailable.
I would like to clone this bug for Fedora 20. Any advice? I have seen the clone link. However, the response is that I need to select a classification.
I have also this problem (or a very similar problem) in Fedora 20 KDE with kernel 3.12.7 in a computer with Intel HD4000. But for me it isn't necessary pressing the power button for reboot, I can switch to tty and only waiting a minute or two the system returns to normal.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.