Scrolling in LibreOffice Calc causes hang

[Steven Keys]

On my ThinkPad X220 with a Sandy Bridge i7 processor and Xubuntu 11.10 64-bit, LibreOffice always crashes when scrolling vertically on the attached file's charts (third sheet). I suspect that this is actually an issue with the kernel and Sandy Bridge graphics and NOT a problem with LibreOffice Calc. This behavior only occurs with kernel 3.2.0-17.26-rc6notrc6p (http://kernel.ubuntu.com/~sarvatt/rc6/) and with kernel 3.2.5-tunerc6v1 (http://people.canonical.com/~ogasawara/eugeni/rc6/). This issue does NOT happen on prior kernels.
---
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
DistroRelease: Ubuntu 11.10
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
Package: linux (not installed)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: oneiric
Uname: Linux 3.2.5-tunerc6v1-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape vboxusers video

[Steven Keys (steevven1)]

This bug was originally discovered when trying fixes for another bug (more discussion about it there): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/940771

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 940771

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Steven Keys (steevven1)]

It's been apport-collected. Changing to confirmed.

[Seth Forshee (sforshee)]

I suspect this is a duplicate of bug 938770, and I'm beginning to suspect it's related to touchpad/gesture support. I don't really think it's related to i915, and I'm skeptical that it's even a kernel problem. I was able to reproduce exactly the hang I've been seeing using your file.

To confirm this is a duplicate, can you answer the following questions?

1. Can you describe exactly what you see when this happens? What I see is a completely unresponsive desktop -- the mouse pointer moves, but nothing responds to clicks or keyboard input.

2. If your behavior is as I describe it, is the machine generally alive other than the desktop being responsive? Can you switch to a virtual terminal (i.e. press Ctrl+Alt+F1), log in, and run 'sudo service lightdm restart' to return to a functional desktop?

3. How are you scrolling when this happens? E.g., using a mouse or a touchpad, using a scroll wheel or touchpad gestures (two-finger or edge scrolling) or the scroll bar.

[Steven Keys (steevven1)]

Thanks for inquiring. In response to your questions:

1) I see the exact same thing as you: Mouse moves, but no response to anything (except what I'm about to mention in answer 2...

2) I am NOT able to switch to a virtual terminal using Alt + Ctrl + F1/2/3/4/5/etc. The only thing I can do is reboot with SysRq + R-E-I-S-U-B.

3) I have tested this scrolling with a scroll wheel on a USB mouse and scrolling by dragging the scroll bar on the right hand side of the window with an IBM TrackPoint mouse (built-in to my laptop). I have not used a TouchPad at all.

[Steven Keys (steevven1)]

It may not be a problem with i915, but I'm pretty sure it's a kernel issue, since when I revert to kernel 3.0, the problem disappears.

[Seth Forshee (sforshee)]

I can go back to 3.2.0-3.9 from early December and still create the problem though, and I'm certain I was not seeing it back then. So it's not as clear-cut as you make it; there's likely an interaction between the kernel and userspace that's to blame, but who is at fault isn't entirely clear at this point.

That's assuming you and I are seeing the same issue, which I still suspect is the case, but I'm not 100% convinced at this point.

[Steven Keys (steevven1)]

I have tested the current upstream kernel from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc5-precise/ (3.3-rc5), and this issue is not reproducible on the same machine with the same file. For now, it appears that the issue does not exist for that kernel.

[Seth Forshee (sforshee)]

Steven: It would be really helpful if you could boot into the 3.2.0-17.27 kernel and run 'apport-collect 940771' to attach logs and hardware information to this bug. Thanks!

[Steven Keys (steevven1)]

Someone from ubuntuforums reports that disabling hardware acceleration and anti-aliasing in Tools/options/Libreoffice/view fixes the problem. I have not yet tested this.

[penalvch (penalvch)]

Steven Keys, thank you for reporting this and helping make Ubuntu better. As per your Bug Description:
>"LibreOffice always crashes..."

This is a crash bug. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. One may execute at the Terminal:
sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install libreoffice-dbg uno-libs3-dbg ure-dbg && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. Please follow https://wiki.ubuntu.com/LibreOfficeBugWrangling when you file this crash report so the necessary information is provided.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Helpful Bug Reporting Links:Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug