Version-Release number of selected component: libreoffice-core-4.1.4.2-4.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --impress --splash-pipe=5 crash_function: ServerFont::Release executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.12.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ServerFont::Release at /usr/src/debug/libreoffice-4.1.4.2/vcl/generic/glyphs/glyphcache.cxx:341 #1 GlyphCache::UncacheFont at /usr/src/debug/libreoffice-4.1.4.2/vcl/generic/glyphs/glyphcache.cxx:236 #2 X11SalGraphics::setFont at /usr/src/debug/libreoffice-4.1.4.2/vcl/unx/generic/gdi/salgdi3.cxx:166 #3 X11SalGraphics::SetFont at /usr/src/debug/libreoffice-4.1.4.2/vcl/unx/generic/gdi/salgdi3.cxx:508 #4 ReleaseFonts at /usr/src/debug/libreoffice-4.1.4.2/vcl/inc/salgdi.hxx:224 #5 OutputDevice::ImplUpdateFontData at /usr/src/debug/libreoffice-4.1.4.2/vcl/source/gdi/outdev3.cxx:186 #7 OutputDevice::ImplUpdateAllFontData at /usr/src/debug/libreoffice-4.1.4.2/vcl/source/gdi/outdev3.cxx:262 #8 ImplHandleSalSettings at /usr/src/debug/libreoffice-4.1.4.2/vcl/source/window/winproc.cxx:2216 #9 ImplWindowFrameProc at /usr/src/debug/libreoffice-4.1.4.2/vcl/source/window/winproc.cxx:2597 #10 CallCallback at /usr/src/debug/libreoffice-4.1.4.2/vcl/inc/salframe.hxx:243 Potential duplicate: bug 1045497
Created attachment 855640 [details] File: backtrace
Created attachment 855641 [details] File: cgroup
Created attachment 855642 [details] File: core_backtrace
Created attachment 855643 [details] File: dso_list
Created attachment 855644 [details] File: environ
Created attachment 855645 [details] File: exploitable
Created attachment 855646 [details] File: limits
Created attachment 855647 [details] File: maps
Created attachment 855648 [details] File: open_fds
Created attachment 855649 [details] File: proc_pid_status
Created attachment 855650 [details] File: var_log_messages
It is not reproducible, I presume?
No, it doesn't seem reproducible. I don't know if this is relevant, but I should add that I was updating the system with yum when this happened, and looking at yum history, that day at that time the following packages were updated: rpm yum yum-metadata-parser gnome-shell google-crosextra-caladea-fonts rtkittigervnc-license tigervnc-server-minimal webkitgtk webkitgtk3 Yum history info says: Begin time : Sun Jan 26 10:12:47 2014 End time : 10:12:55 2014 (8 seconds) According to comment #12, the crash happened gen 26 10:12:53
I suppose it was reinstallation of google-crosextra-caladea-fonts that caused this. Trying that locally, with the font used in an opened document, does not lead to any crash, but valgrind is not happy about it...
fixed upstream
*** Bug 1070497 has been marked as a duplicate of this bug. ***
libreoffice-4.1.5.3-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/libreoffice-4.1.5.3-4.fc19
Package libreoffice-4.1.5.3-4.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libreoffice-4.1.5.3-4.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-3458/libreoffice-4.1.5.3-4.fc19 then log in and leave karma (feedback).
bodhi failed to close this bug for some reason...