soffice.bin crashed with SIGSEGV in SalDisplay::addXineramaScreenUnique()

[Kyrill]

Description: Ubuntu oneiric (development branch)
Release: 11.10

Version: 1:3.4.3-1ubuntu3

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libreoffice-core 1:3.4.3-1ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Thu Sep 29 13:04:31 2011
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer --splash-pipe=7
ProcEnviron:
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x81d5286 <_ZN10SalDisplay23addXineramaScreenUniqueEillll+198>: mov %ecx,(%eax,%edx,4)
 PC (0x081d5286) ok
 source "%ecx" ok
 destination "(%eax,%edx,4)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 SalDisplay::addXineramaScreenUnique(int, long, long, long, long) () from /usr/lib/libreoffice/basis3.4/program/libvclplug_genli.so
 ?? () from /usr/lib/libreoffice/basis3.4/program/libvclplug_gtkli.so
 g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: soffice.bin crashed with SIGSEGV in SalDisplay::addXineramaScreenUnique()
UpgradeStatus: Upgraded to oneiric on 2011-09-28 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin netdev 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 #861886, 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.