oosplash.bin crashed with SIGSEGV in xcb_writev()

Bug #833054 reported by Scott Stensland
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was just reading my gmail and clicked to download a file ending in docx

 lsb_release -rd
Description: Ubuntu oneiric (development branch)
Release: 11.10

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libreoffice-core 1:3.4.1-4ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Aug 24 10:56:24 2011
ExecutablePath: /usr/lib/libreoffice/program/oosplash.bin
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110804)
ProcCmdline: /usr/lib/libreoffice/program/oosplash.bin --writer /usr/tmp/ARM\ SENIOR\ PERFORMANCE\ ANALYSIS\ ENGINEER.docx
SegvAnalysis:
 Segfault happened at: 0x277678 <xcb_writev+40>: mov (%esi),%eax
 PC (0x00277678) ok
 source "(%esi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 xcb_writev () from /usr/lib/i386-linux-gnu/libxcb.so.1
 _XSend () from /usr/lib/i386-linux-gnu/libX11.so.6
 _XFlush () from /usr/lib/i386-linux-gnu/libX11.so.6
 XFlush () from /usr/lib/i386-linux-gnu/libX11.so.6
 splash_draw_progress ()
Title: oosplash.bin crashed with SIGSEGV in xcb_writev()
UpgradeStatus: Upgraded to oneiric on 2011-08-24 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Scott Stensland (scottstensland) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #832516, 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.

visibility: private → public
tags: removed: need-i386-retrace
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.