soffice.bin crashed with SIGSEGV in desktop::CommandLineArgs::ParseCommandLine_Impl()

Bug #881296 reported by Zanko Ralenekov
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Libreoffice crashes every time soon after showing the splash screen (oosplash.bin).
Ubuntu: 11.10 (upgraded from 11.04)
Libreoffice: 1:3.4.3-3ubuntu2

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libreoffice-core 1:3.4.3-3ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Tue Oct 25 11:08:35 2011
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=7
ProcCwd: /home/zankor
SegvAnalysis:
 Segfault happened at: 0x7f664df25aba <desktop::CommandLineArgs::ParseCommandLine_Impl(desktop::CommandLineArgs::Supplier&)+266>: mov (%rdx),%rax
 PC (0x7f664df25aba) ok
 source "(%rdx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 desktop::CommandLineArgs::ParseCommandLine_Impl (this=0x85fbc0, supplier=...) at /build/buildd/libreoffice-3.4.3/libreoffice-build/build/libreoffice-3.4.3.2/desktop/source/app/cmdlineargs.cxx:145
 desktop::CommandLineArgs::CommandLineArgs (this=0x85fbc0) at /build/buildd/libreoffice-3.4.3/libreoffice-build/build/libreoffice-3.4.3.2/desktop/source/app/cmdlineargs.cxx:125
 desktop::Desktop::GetCommandLineArgs () at /build/buildd/libreoffice-3.4.3/libreoffice-build/build/libreoffice-3.4.3.2/desktop/source/app/app.cxx:325
 soffice_main () at /build/buildd/libreoffice-3.4.3/libreoffice-build/build/libreoffice-3.4.3.2/desktop/source/app/sofficemain.cxx:56
 sal_main () at main.c:36
Title: soffice.bin crashed with SIGSEGV in desktop::CommandLineArgs::ParseCommandLine_Impl()
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (11 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Zanko Ralenekov (zanko-ralenekov) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 desktop::CommandLineArgs::ParseCommandLine_Impl (this=0x85fbc0, supplier=...) at /build/buildd/libreoffice-3.4.3/libreoffice-build/build/libreoffice-3.4.3.2/desktop/source/app/cmdlineargs.cxx:145
 desktop::CommandLineArgs::CommandLineArgs (this=0x85fbc0) at /build/buildd/libreoffice-3.4.3/libreoffice-build/build/libreoffice-3.4.3.2/desktop/source/app/cmdlineargs.cxx:125
 desktop::Desktop::GetCommandLineArgs () at /build/buildd/libreoffice-3.4.3/libreoffice-build/build/libreoffice-3.4.3.2/desktop/source/app/app.cxx:325
 soffice_main () at /build/buildd/libreoffice-3.4.3/libreoffice-build/build/libreoffice-3.4.3.2/desktop/source/app/sofficemain.cxx:56
 sal_main () at main.c:36

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in libreoffice (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libreoffice (Ubuntu):
status: New → Confirmed
Revision history for this message
methane (songofacandy) wrote :

I faces same problem.
libreoffice runs after reinstalling.

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

Thank you for reporting this bug to Ubuntu. This Ubuntu release has reached EOL for Desktops.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

It hasn't been reported again on a more recent Ubuntu release.. I f you still see it on 14.04, please reopen this bug.

Changed in libreoffice (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.