Version-Release number of selected component: libreoffice-core-4.1.3.2-5.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --calc smb://frank@homer/frank/Dokumente/Haushaltsb%C3%BCcher/2013.ods --splash-pipe=5 crash_function: rtl_uString_acquire executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.11.9-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 rtl_uString_acquire at /usr/src/debug/libreoffice-4.1.3.2/sal/rtl/strtmpl.cxx:1079 #1 String::String at /usr/src/debug/libreoffice-4.1.3.2/tools/source/string/strimp.cxx:126 #2 ImplDevFontAttributes at /usr/src/debug/libreoffice-4.1.3.2/vcl/inc/outfont.hxx:95 #3 PhysicalFontFace::PhysicalFontFace at /usr/src/debug/libreoffice-4.1.3.2/vcl/source/gdi/outdev3.cxx:694 #4 ImplFTSFontData at /usr/src/debug/libreoffice-4.1.3.2/vcl/generic/glyphs/gcach_ftyp.cxx:631 #5 FtFontInfo::AnnounceFont at /usr/src/debug/libreoffice-4.1.3.2/vcl/generic/glyphs/gcach_ftyp.cxx:472 #6 FreetypeManager::AnnounceFonts at /usr/src/debug/libreoffice-4.1.3.2/vcl/generic/glyphs/gcach_ftyp.cxx:591 #7 GlyphCache::AnnounceFonts at /usr/src/debug/libreoffice-4.1.3.2/vcl/generic/glyphs/glyphcache.cxx:167 #8 X11SalGraphics::GetDevFontList at /usr/src/debug/libreoffice-4.1.3.2/vcl/unx/generic/gdi/salgdi3.cxx:610 #9 OutputDevice::ImplUpdateFontData at /usr/src/debug/libreoffice-4.1.3.2/vcl/source/gdi/outdev3.cxx:217
Created attachment 832317 [details] File: backtrace
Created attachment 832318 [details] File: cgroup
Created attachment 832319 [details] File: core_backtrace
Created attachment 832320 [details] File: dso_list
Created attachment 832321 [details] File: environ
Created attachment 832322 [details] File: exploitable
Created attachment 832323 [details] File: limits
Created attachment 832324 [details] File: maps
Created attachment 832325 [details] File: open_fds
Created attachment 832326 [details] File: proc_pid_status
Created attachment 832327 [details] File: var_log_messages
*** This bug has been marked as a duplicate of bug 1009850 ***