oosplash.bin crashed with SIGSEGV in XSetForeground()

[Tobias Gauster]

I just started a .ods file from a samba share and this dialog poped up, saying "oosplash.bin crashed with SIGSEGV in XSetForeground()" but as far as it seems, everything is ok. The file is opened and editable.

I can't reproduce this error, from now on, all the files open fine. It takes about 20 seconds for every ods file to open, which is quite long.

That's my first bug report, I don't really know what I do... ;-) So if you need further information please let me know.

Description: Ubuntu oneiric (development branch)
Release: 11.10

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libreoffice-core 1:3.4.2-2ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Tue Aug 30 08:59:25 2011
ExecutablePath: /usr/lib/libreoffice/program/oosplash.bin
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
ProcCmdline: /usr/lib/libreoffice/program/oosplash.bin --calc /home/User Name/.gvfs/homes\ on\ xaver/Verwaltung/Packlisten/klaffer.ods
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f205e182e56 <XSetForeground+22>: mov 0x968(%rdi),%rax
 PC (0x7f205e182e56) ok
 source "0x968(%rdi)" (0x00000968) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 XSetForeground () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 splash_draw_progress ()
 ?? ()
 main ()
Title: oosplash.bin crashed with SIGSEGV in XSetForeground()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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 #835153, 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.