soffice.bin crashed with SIGSEGV

[KroArtem]

1) lsb_release -rd
Description: Ubuntu 13.04
Release: 13.04

2) apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:4.0.2-0ubuntu1
  Candidate: 1:4.0.2-0ubuntu1
  Version table:
 *** 1:4.0.2-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
        100 /var/lib/dpkg/status

3) What is expected to happen in Writer via a terminal:
cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1193316/+attachment/3708847/+files/VychMat.docx && lowriter --nologo VychMat.docx

is it opens successfully.

4) What happens instead is it crashes consistently.

WORKAROUND: Use AbiWord.

apt-cache policy abiword
abiword:
  Installed: 2.9.2+svn20120603-8
  Candidate: 2.9.2+svn20120603-8
  Version table:
 *** 2.9.2+svn20120603-8 0
        500 http://archive.ubuntu.com/ubuntu/ raring/universe i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: libreoffice-core 1:4.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Fri Jun 21 15:14:36 2013
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2012-08-08 (316 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
MarkForUpload: True
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=6
SegvAnalysis:
 Segfault happened at: 0x7f67c2d8573b: movzbl 0xb9(%rax),%eax
 PC (0x7f67c2d8573b) ok
 source "0xb9(%rax)" (0x000000b9) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? () from /usr/lib/libreoffice/program/../program/libswlo.so
 ?? () from /usr/lib/libreoffice/program/../program/libswlo.so
 ?? () from /usr/lib/libreoffice/program/../program/libswlo.so
 ?? () from /usr/lib/libreoffice/program/../program/libswlo.so
 ?? () from /usr/lib/libreoffice/program/../program/libswlo.so
Title: soffice.bin crashed with SIGSEGV
UpgradeStatus: Upgraded to raring on 2013-05-03 (48 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 IsTabFrm (this=0x0) at /build/buildd/libreoffice-4.0.2/sw/source/core/inc/frame.hxx:1185
 lcl_hasTabFrm (pTxtFrm=pTxtFrm@entry=0x7f67ba2779e8) at /build/buildd/libreoffice-4.0.2/sw/source/core/layout/frmtool.cxx:1934
 SwBorderAttrs::CalcLeft (this=this@entry=0x7f67ba29b348, pCaller=pCaller@entry=0x7f67ba2779e8) at /build/buildd/libreoffice-4.0.2/sw/source/core/layout/frmtool.cxx:1967
 SwBorderAttrs::CmpLeftRight (this=this@entry=0x7f67ba29b348, rCmpAttrs=..., pCaller=pCaller@entry=0x7f67ba2779e8, pCmp=pCmp@entry=0x7f67ba2778d0) at /build/buildd/libreoffice-4.0.2/sw/source/core/layout/frmtool.cxx:2080
 SwBorderAttrs::_JoinWithCmp (this=this@entry=0x7f67ba29b348, _rCallerFrm=..., _rCmpFrm=...) at /build/buildd/libreoffice-4.0.2/sw/source/core/layout/frmtool.cxx:2095

[penalvch (penalvch)]

KroArtem, thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one. It would be nice if somebody having it could send the bug to the developers of the software by following the instructions verbatim at http://wiki.documentfoundation.org/BugReport . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about the status. Thanks in advance.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

Reproducible in:
Version: 4.1.0.1
Build ID: 1b3956717a60d6ac35b133d7b0a0f5eb55e9155
Microsoft Windows Vista Business x86 6.0.6002 Service Pack 2 Build 6002

[KroArtem (kroartem)]

Problem description:
lowriter crashed when trying to open .docx file
Steps to reproduce:
1. Goto https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1193316
2. Check all needed information

Current behavior: crashed when trying to open .docx file

Expected behavior: open it normally.

Sorry for not being very informative, but I've already created another ticket on launchpad.

Operating System: Ubuntu
Version: 4.0.2.2 release

[KroArtem (kroartem)]

Created a ticket in bugzilla - https://bugs.freedesktop.org/show_bug.cgi?id=66101

[Spam35 (spam35)]

The file in question (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1193316/+attachment/3708847/+files/VychMat.docx) opens fine for me with LO 4.1.0.1 on OS X 10.8.4.

Artem: Could you please re-try with the latest LO release and see if that works for you: http://www.libreoffice.org/download/pre-releases/

After trying please set this bug back to "unconfirmed" should it still be crashing for you. If it is fixed, please set the bug to "RESOLVED - WORKSFORME".

[KroArtem (kroartem)]

I tried to install latest libreoffice from LibreOffice_4.1.0.1_Linux_x86-64_deb and had some problems during "sudo dpkg -i *.deb":

Rebuilding /usr/share/applications/bamf-2.index...
Обрабатываются триггеры для desktop-file-utils …
Обрабатываются триггеры для gnome-menus …
Обрабатываются триггеры для shared-mime-info …
/usr/share/mime/packages/libreoffice4.1.xml:1419: parser error : EntityRef: expecting ';'
    <comment xml:lang="mn">&Microsoft Word Баримтууд</comment>
                                     ^
/usr/share/mime/packages/libreoffice4.1.xml:1439: parser error : EntityRef: expecting ';'
    <comment xml:lang="sa-IN">&Microsoft Word लेखपत्रम्</comme
                                        ^
/usr/share/mime/packages/libreoffice4.1.xml:1532: parser error : EntityRef: expecting ';'
    <comment xml:lang="mn">&Microsoft Word Баримтууд</comment>
                                     ^
/usr/share/mime/packages/libreoffice4.1.xml:1552: parser error : EntityRef: expecting ';'
    <comment xml:lang="sa-IN">&Microsoft Word लेखपत्रम्</comme
                                        ^
/usr/share/mime/packages/libreoffice4.1.xml:1645: parser error : EntityRef: expecting ';'
    <comment xml:lang="mn">&Microsoft Word Баримтууд</comment>
                                     ^
/usr/share/mime/packages/libreoffice4.1.xml:1665: parser error : EntityRef: expecting ';'
    <comment xml:lang="sa-IN">&Microsoft Word लेखपत्रम्</comme
                                        ^
/usr/share/mime/packages/libreoffice4.1.xml:4247: parser error : EntityRef: expecting ';'
    <comment xml:lang="mn">&Microsoft Word Баримтууд</comment>
                                     ^
/usr/share/mime/packages/libreoffice4.1.xml:4267: parser error : EntityRef: expecting ';'
    <comment xml:lang="sa-IN">&Microsoft Word लेखपत्रम्</comme
                                        ^
Failed to parse '/usr/share/mime/packages/libreoffice4.1.xml'
При обработке следующих пакетов произошли ошибки:
 libobasis4.1-kde-integration_4.1.0.1-1_amd64.deb
kroartem@kroartem-desktop:~/Загрузки/LibreOffice_4.1.0.1_Linux_x86-64_deb/DEBS$ cd desktop-integration
bash: cd: desktop-integration: No such file or directory

[penalvch (penalvch)]

Reproducible in:
Version: 4.1.0.1
Build ID: 1b3956717a60d6ac35b133d7b0a0f5eb55e9155
Microsoft Windows Vista Business x86 6.0.6002 Service Pack 2 Build 6002

What is expected to happen in Writer via a terminal:
cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1193316/+attachment/3708847/+files/VychMat.docx && lowriter --nologo VychMat.docx

is it opens successfully.

What happens instead is it crashes consistently.

Artem, regarding your comments:
>"Sorry for not being very informative, but I've already created another ticket on launchpad."

That's not how it works. In the future, one would want to input the same, step-by-step instructions with appropriate attachment(s), as previously requested of you in https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1193316/comments/5 , or risk the report being flagged as INCOMPLETE, or at the very least, ignored.

Thank you for your understanding.

[julien2412 (serval2412-6)]

Created attachment 81505
console + bt with symbols on master sources

On pc Debian x86-64 with master sources updated today + brand new LO profile I reproduced the crash.

I attached console logs + bt

[julien2412 (serval2412-6)]

Just for information, I submitted a patch to review, see https://gerrit.libreoffice.org/#/c/4550/

[Libreoffice-commits (libreoffice-commits)]

Julien Nabet committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=296c2af27a189e8406957ac44eb412ec3f9a74fd

fdo#66101: lowriter crashed when trying to open .docx file

The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
http://wiki.documentfoundation.org/Testing_Daily_Builds
Affected users are encouraged to test the fix and report feedback.

[Libreoffice-commits (libreoffice-commits)]

Julien Nabet committed a patch related to this issue.
It has been pushed to "libreoffice-4-1":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=7af9fea258fe9429d0ff06a705fe294eb36d1c86&h=libreoffice-4-1

fdo#66101: lowriter crashed when trying to open .docx file

It will be available in LibreOffice 4.1.

The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
http://wiki.documentfoundation.org/Testing_Daily_Builds
Affected users are encouraged to test the fix and report feedback.

[Libreoffice-commits (libreoffice-commits)]

Julien Nabet committed a patch related to this issue.
It has been pushed to "libreoffice-4-0":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=213f32fc9839fce3b01af938293eca331b544dd3&h=libreoffice-4-0

fdo#66101: lowriter crashed when trying to open .docx file

It will be available in LibreOffice 4.0.5.

The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
http://wiki.documentfoundation.org/Testing_Daily_Builds
Affected users are encouraged to test the fix and report feedback.

[Björn Michaelsen (bjoern-michaelsen)]

Fixed included in saucy as it was fixed in 4.1.0.2 upstream