Description of problem: When I try to print an file. Version-Release number of selected component: libreoffice-core-3.6.3.2-8.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --quickstart --nologo --nodefault core_backtrace: crash_function: gcc3::raiseException executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.7.4-204.fc18.x86_64 remote_result: NOTFOUND uid: 1000 var_log_messages: Feb 2 09:34:04 bart abrt[3665]: Saved core dump of pid 2072 (/usr/lib64/libreoffice/program/soffice.bin) to /var/spool/abrt/ccpp-2013-02-02-09:34:02-2072 (739147776 bytes) Truncated backtrace: Thread no. 1 (10 frames) #6 gcc3::raiseException at /usr/src/debug/libreoffice-3.6.3.2/bridges/source/cpp_uno/gcc3_linux_x86-64/except.cxx:282 #7 cpp2uno_call at /usr/src/debug/libreoffice-3.6.3.2/bridges/source/cpp_uno/gcc3_linux_x86-64/cpp2uno.cxx:215 #8 cpp_vtable_call at /usr/src/debug/libreoffice-3.6.3.2/bridges/source/cpp_uno/gcc3_linux_x86-64/cpp2uno.cxx:383 #9 privateSnippetExecutor at /usr/lib64/libreoffice/ure/lib/libgcc3_uno.so #10 framework::MenuBarManager::Select at /usr/src/debug/libreoffice-3.6.3.2/framework/source/uielement/menubarmanager.cxx:1154 #11 Call at /usr/src/debug/libreoffice-3.6.3.2/solver/unxlngx6.pro/inc/tools/link.hxx:143 #12 Menu::Select at /usr/src/debug/libreoffice-3.6.3.2/vcl/source/window/menu.cxx:1135 #13 ImplCallSelect at /usr/src/debug/libreoffice-3.6.3.2/vcl/source/window/menu.cxx:2978 #14 Menu::LinkStubImplCallSelect at /usr/src/debug/libreoffice-3.6.3.2/vcl/source/window/menu.cxx:2975 #15 Call at /usr/src/debug/libreoffice-3.6.3.2/solver/unxlngx6.pro/inc/tools/link.hxx:143
Created attachment 691906 [details] File: backtrace
Created attachment 691907 [details] File: cgroup
Created attachment 691908 [details] File: dso_list
Created attachment 691909 [details] File: environ
Created attachment 691910 [details] File: limits
Created attachment 691911 [details] File: maps
Created attachment 691912 [details] File: open_fds
Created attachment 691913 [details] File: proc_pid_status
Created attachment 691914 [details] File: smolt_data
file->print, right ? (i.e. not direct print icon) and instant crash on 64bit ?
correct
Some additional information, after remove the plug-in descripted at #902004 the print dialogue will work.
Doesn't crash for me with the extension installed (on x86-64) and file->print on an empty document, though the extension does appear to hook into every menu launch so the bt is plausible. caolan->sbergman: Able to reproduce this ? or have any good ideas.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.