Application: okular (0.15.98) KDE Platform Version: 4.9.98 Qt Version: 4.8.4 Operating System: Linux 3.7.2-1-desktop x86_64 Distribution: "openSUSE 12.3 Beta 1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: opened several okular ( ~8 to 10 ) then start to close one after zoom in zoom out. Get the backtrace. This is openSUSE KDE KDF (4.10.rc3) rpms The crash can be reproduced some of the time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 0x00007f1abc655634 in free () from /lib64/libc.so.6 #6 0x00007f1abdccb418 in QtFontStyle::~QtFontStyle (this=0xfd1290, __in_chrg=<optimized out>) at text/qfontdatabase.cpp:261 #7 0x00007f1abdccba9c in ~QtFontFoundry (this=<optimized out>, __in_chrg=<optimized out>) at text/qfontdatabase.cpp:349 #8 ~QtFontFamily (this=<optimized out>, __in_chrg=<optimized out>) at text/qfontdatabase.cpp:428 #9 free (this=<optimized out>) at text/qfontdatabase.cpp:677 #10 ~QFontDatabasePrivate (this=<optimized out>, __in_chrg=<optimized out>) at text/qfontdatabase.cpp:662 #11 QGlobalStaticDeleter<QFontDatabasePrivate>::~QGlobalStaticDeleter (this=0x7f1abe563348 <privateDb()::cleanup>, __in_chrg=<optimized out>) at ../../src/corelib/global/qglobal.h:1949 #12 0x00007f1abc60ef61 in __run_exit_handlers () from /lib64/libc.so.6 #13 0x00007f1abc60efe5 in exit () from /lib64/libc.so.6 #14 0x00007f1abc5f8a1c in __libc_start_main () from /lib64/libc.so.6 #15 0x00000000004095a9 in _start () Reported using DrKonqi
Hi, when you say "opened several okular ( ~8 to 10 ) then start to close one after zoom in zoom out." what do you mean exactly, how do you open the several okular?
For example open dolphin, go to a folder where you know there's several pdf available. filter the folder with pdf, select them all, then hit the enter key But it seems fixed on 4.10 rc3, I can't reproduce it anymore. For the safe of the shake, if it doesn't crash for you then simply clause the bug.
Closing the bug for now. Thanks for the report :-) Do not hesitate to reopen it if it comes back