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
Created attachment 758009 [details] File: backtrace
Created attachment 758010 [details] File: cgroup
Created attachment 758011 [details] File: core_backtrace
Created attachment 758012 [details] File: dso_list
Created attachment 758013 [details] File: environ
Created attachment 758014 [details] File: limits
Created attachment 758016 [details] File: maps
Created attachment 758017 [details] File: open_fds
Created attachment 758018 [details] File: proc_pid_status
Created attachment 758019 [details] File: var_log_messages
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.
"yum downgrade harfbuzz\*" is the work-around. *** This bug has been marked as a duplicate of bug 971230 ***
*** This bug has been marked as a duplicate of bug 971795 ***