soffice.bin crashed with SIGSEGV

[Fedor Dikarev]

root@t34:~# env LC_ALL=C lsb_release -r
Release: 12.04
root@t34:~# env LC_ALL=C apt-cache policy libreoffice
libreoffice:
  Installed: 1:3.5.0~beta2-2ubuntu4
  Candidate: 1:3.5.0~beta2-2ubuntu4
  Version table:
 *** 1:3.5.0~beta2-2ubuntu4 0
        500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

I press "Print preview", writer shows me that and hangs up after that.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libreoffice-core 1:3.5.0~beta2-2ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Jan 24 15:45:36 2012
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer /home/username/Документы/Rambler/сетевой\ инженер/24-01-12/Виноградов\ Максим.rtf --splash-pipe=6
ProcEnviron:
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? () from /usr/lib/libreoffice/program/../share/extensions/menubar/Linux_x86_64/menubar.uno.so
 ?? () from /usr/lib/libreoffice/program/../share/extensions/menubar/Linux_x86_64/menubar.uno.so
 ?? () from /usr/lib/libreoffice/program/libsfxlo.so
 ?? () from /usr/lib/libreoffice/program/libsfxlo.so
 ?? () from /usr/lib/libreoffice/program/libsfxlo.so
Title: soffice.bin crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-01-24 (0 days ago)
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 this software better. This particular crash has already been reported and is a duplicate of bug #907967, 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.