Bug 971703

Summary: [abrt] libreoffice-core-4.1.0.0-6.beta1.fc19: Process /usr/lib64/libreoffice/program/soffice.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Martin Kočí <mkoci>
Component: libreofficeAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: bugs.michael, caolanm, dtardon, erack, ltinkl, mstahl, sbergman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5f787784e4b01a4ec3734d82729606a86c0fceb6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-07 06:35:32 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Martin Kočí 2013-06-07 03:37:56 EDT
Description of problem:
I have tried to open .docx document which was caused this issue. Before I did an update of libreoffice. 

Version-Release number of selected component:
libreoffice-core-4.1.0.0-6.beta1.fc19

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/lib64/libreoffice/program/soffice.bin --writer file:///var/tmp/Konkuren%C4%8Dn%C3%AD%20v%C3%BDhody.docx --splash-pipe=5
executable:     /usr/lib64/libreoffice/program/soffice.bin
kernel:         3.9.4-301.fc19.x86_64
runlevel:       N 5
uid:            1000
xsession_errors: 

Truncated backtrace:
Thread no. 1 (0 frames)

Potential duplicate: bug 841321
Comment 1 Martin Kočí 2013-06-07 03:38:01 EDT
Created attachment 758009 [details]
File: backtrace
Comment 2 Martin Kočí 2013-06-07 03:38:07 EDT
Created attachment 758010 [details]
File: cgroup
Comment 3 Martin Kočí 2013-06-07 03:38:11 EDT
Created attachment 758011 [details]
File: core_backtrace
Comment 4 Martin Kočí 2013-06-07 03:38:15 EDT
Created attachment 758012 [details]
File: dso_list
Comment 5 Martin Kočí 2013-06-07 03:38:20 EDT
Created attachment 758013 [details]
File: environ
Comment 6 Martin Kočí 2013-06-07 03:38:23 EDT
Created attachment 758014 [details]
File: limits
Comment 7 Martin Kočí 2013-06-07 03:38:28 EDT
Created attachment 758016 [details]
File: maps
Comment 8 Martin Kočí 2013-06-07 03:38:35 EDT
Created attachment 758017 [details]
File: open_fds
Comment 9 Martin Kočí 2013-06-07 03:38:39 EDT
Created attachment 758018 [details]
File: proc_pid_status
Comment 10 Martin Kočí 2013-06-07 03:38:42 EDT
Created attachment 758019 [details]
File: var_log_messages
Comment 11 Martin Kočí 2013-06-07 03:42:56 EDT
At this moment I can't provide you the document which is most likely causing this seg. fault, because I don't know if there are some confidential data. Once I'm able to open it in some other environment I can attach to it.
Comment 12 Michael Schwendt 2013-06-07 06:35:32 EDT
"yum downgrade harfbuzz\*" is the work-around.

*** This bug has been marked as a duplicate of bug 971230 ***
Comment 13 David Tardon 2013-06-07 08:23:36 EDT

*** This bug has been marked as a duplicate of bug 971795 ***