oosplash.bin crashed with SIGSEGV in xcb_writev()

[Tor Harald Thorland]

appeared when libreoffice writer was opened

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libreoffice-core 1:3.4.1-4ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.13-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Aug 23 18:42:39 2011
ExecutablePath: /usr/lib/libreoffice/program/oosplash.bin
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/lib/libreoffice/program/oosplash.bin --writer /home/username/1295952888.rtf
ProcEnviron:
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 PATH=(custom, no user)
 LANG=nb_NO.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x294678 <xcb_writev+40>: mov (%esi),%eax
 PC (0x00294678) 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-14 (9 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[penalvch (penalvch)]

Tor Harald Thorland, thank you for reporting this bug and helping make Ubuntu better. As a workaround, does LibreOffice crash via the Terminal command:

lowriter -nologo

[Tor Harald Thorland (linux-strigen)]

Hi,
Libreoffice did start fine, only gave the above when it started.
Unfortunately(or fortunately) now after a restart I'm not able to reproduce the same...

[Apport retracing service (apport)]

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.