Description of problem: I pressed ctrl + s. Version-Release number of selected component: libreoffice-core-4.1.5.3-1.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --splash-pipe=5 crash_function: GetMetricText(long, SfxMapUnit, SfxMapUnit, IntlWrapper const*) executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.13.3-201.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (1 frames) #0 GetMetricText(long, SfxMapUnit, SfxMapUnit, IntlWrapper const*) at /usr/lib64/libreoffice/program/../program/libeditenglo.so
Created attachment 873856 [details] File: backtrace
Created attachment 873857 [details] File: cgroup
Created attachment 873858 [details] File: core_backtrace
Created attachment 873859 [details] File: dso_list
Created attachment 873860 [details] File: environ
Another user experienced a similar problem: I pressed ctrl + s reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --splash-pipe=5 crash_function: GetMetricText(long, SfxMapUnit, SfxMapUnit, IntlWrapper const*) executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.13.3-201.fc20.x86_64 package: libreoffice-core-4.1.5.3-1.fc20 reason: soffice.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
Created attachment 873861 [details] File: exploitable
Created attachment 873862 [details] File: limits
Created attachment 873863 [details] File: maps
Created attachment 873864 [details] File: open_fds
Created attachment 873865 [details] File: proc_pid_status
Created attachment 873866 [details] File: var_log_messages
The backtrace is unfortunately completely mangled and of no use. Can you reproduce this problem, and if so how ?
I'm not sure; yesterday morning it happened 4-5 times in succession (I'd open libreoffice, recover the files that were not closed properly due to the previous crash, edit them, try to save, and *crash*). By the time I'd gotten the bug reports submitted, the problem no longer occurred (and hasn't occurred since).
https://retrace.fedoraproject.org/faf/reports/371375/ points here but has a different backrace in it. That one suggests a crash in the rtf export (which is related to copy and paste as well)
Committed http://cgit.freedesktop.org/libreoffice/core/commit/?id=7d53f81f0a88afcff0f60bbd066a5645ac2e6a8b upstream which might help. Without a reproducer I'll close this as closed->upstream
This happened again just now: multiple times trying to edit an RTF, ctrl+s caused the program to crash. I finally was able to save by going to "file -> save", and after that, had no problem with ctrl + s. Unfortunately, the automatic bug reporter won't gather any new data since the bug has already been reported.
libreoffice-4.2.3.2-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/libreoffice-4.2.3.2-3.fc20
libreoffice-4.2.3.2-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.