soffice.bin crashed with SIGSEGV in SetFormatIgnoreStart()

Bug #1232634 reported by Osanda
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10

libreoffice-writer:
  Installed: 1:4.1.2~rc2-0ubuntu1
  Candidate: 1:4.1.2~rc2-0ubuntu1
  Version table:
 *** 1:4.1.2~rc2-0ubuntu1 0

libreoffice writer crashed while trying to delete words with backspace continuously, It froze for a while then suddenly closed itself.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: libreoffice-core 1:4.1.2~rc2-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Sun Sep 29 13:24:18 2013
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2013-09-27 (1 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer --splash-pipe=5
SegvAnalysis:
 Segfault happened at: 0x7fdad89d51a9: orb $0x2,0x13(%rax)
 PC (0x7fdad89d51a9) ok
 source "$0x2" ok
 destination "0x13(%rax)" (0x00000013) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? () from /usr/lib/libreoffice/program/../program/libswlo.so
 ?? () from /usr/lib/libreoffice/program/../program/libswlo.so
 ?? () from /usr/lib/libreoffice/program/../program/libswlo.so
 ?? () from /usr/lib/libreoffice/program/../program/libswlo.so
 SfxListUndoAction::UndoWithContext(SfxUndoContext&) () from /usr/lib/libreoffice/program/libmergedlo.so
Title: soffice.bin crashed with SIGSEGV in SfxListUndoAction::UndoWithContext()
UpgradeStatus: Upgraded to saucy on 2013-09-28 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Osanda (osanda) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 SetFormatIgnoreStart (bFlag=true, this=0x0) at /build/buildd/libreoffice-4.1.2~rc2/sw/inc/txatbase.hxx:101
 SwHistorySetTxt::SetInDoc (this=0x39abb70, pDoc=0x2c0a7b0) at /build/buildd/libreoffice-4.1.2~rc2/sw/source/core/undo/rolbck.cxx:246
 SwHistory::TmpRollback (this=0x41a8130, pDoc=0x2c0a7b0, nStart=<optimized out>, bToFirst=<optimized out>) at /build/buildd/libreoffice-4.1.2~rc2/sw/source/core/undo/rolbck.cxx:1158
 SwUndoSplitNode::UndoImpl (this=0x42bc750, rContext=...) at /build/buildd/libreoffice-4.1.2~rc2/sw/source/core/undo/unspnd.cxx:136
 SwUndo::UndoWithContext (this=0x42bc750, rContext=...) at /build/buildd/libreoffice-4.1.2~rc2/sw/source/core/undo/undobj.cxx:230

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in libreoffice (Ubuntu):
importance: Undecided → Medium
summary: - soffice.bin crashed with SIGSEGV in SfxListUndoAction::UndoWithContext()
+ soffice.bin crashed with SIGSEGV in SetFormatIgnoreStart()
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
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in libreoffice (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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