soffice.bin crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libreoffice (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Using Ubuntu 12.10 Beta 2 (Quantal), updated as of about 12 hours ago, and libreoffice 1:3.6.1~
What Happened: I had a spreadsheet open in LibreOffice (LO). I closed it, which sent me to the "main screen" (I don't really know what to call it -- it's the screen that displays a menu with a green LibreOffice banner at the top and the options for opening a Text Document, a Drawing, a Spreadsheet, etc.). At the main screen, I clicked on "Spreadsheet." LibreOffice stopped responding for a few seconds, and then the program crashed entirely, resulting in this bug report.
What I Expected: I expected that a spreadsheet would open in Calc when I clicked on "Spreadsheet."
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: libreoffice-core 1:3.6.1~
ProcVersionSign
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Tue Oct 9 09:01:03 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120925)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f30260ca481: cmpq $0x0,0x20(%rdi)
PC (0x7f30260ca481) ok
source "$0x0" ok
destination "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
g_main_
Title: soffice.bin crashed with SIGSEGV in g_main_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1042070, 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.