soffice.bin crashed with SIGSEGV in SalDisplay::addXineramaScreenUnique()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libreoffice (Ubuntu) |
Fix Released
|
High
|
Björn Michaelsen |
Bug Description
Opened Writer from the launcher. Splash displayed, progress bar filled, then splash disappeared and apport popped up.
Running on Virtualbox, and I was resizing my virtual monitor at the time. Given that this crash occurred in a Xinerama-related function, this seems suspicious. May actually be a bug in the VirtualBox guest additions?
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libreoffice-core 1:3.4.3-1ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Sat Sep 17 16:15:02 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x8ddc286 <_ZN10SalDispla
PC (0x08ddc286) ok
source "%ecx" ok
destination "(%eax,%edx,4)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
SalDisplay:
?? () from /usr/lib/
g_cclosure_
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
Title: soffice.bin crashed with SIGSEGV in SalDisplay:
UpgradeStatus: Upgraded to oneiric on 2011-08-12 (35 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Changed in libreoffice (Ubuntu): | |
milestone: | none → ubuntu-11.10 |
assignee: | nobody → Björn Michaelsen (bjoern-michaelsen) |
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #835861, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.