Bug 220410 - Konqueror crashed after installing Privateer
Summary: Konqueror crashed after installing Privateer
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-28 16:19 UTC by Ronny Standtke
Modified: 2010-02-20 00:44 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ronny Standtke 2009-12-28 16:19:41 UTC
Application that crashed: konqueror
Version of the application: 4.3.4 (KDE 4.3.4)
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-16-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I just installed Privateer. At the end of the installation procedure the installer asked if I wanted to open a browser. I answered "yes", konqueror and okular where started and then just crashed.

 -- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
[KCrash Handler]
#6  0xb283fcbe in Okular::Page::hasPixmap(int, int, int) const () from /usr/lib/libokularcore.so.1
#7  0xb282cd52 in ?? () from /usr/lib/libokularcore.so.1
#8  0xb2832900 in Okular::Document::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libokularcore.so.1
#9  0xb694c263 in QMetaObject::activate (sender=0xa5a3c30, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#10 0xb694cec2 in QMetaObject::activate (sender=0xa5a3c30, m=0xb6a26908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#11 0xb6951387 in QSingleShotTimer::timeout (this=0xa5a3c30) at .moc/release-shared/qtimer.moc:76
#12 0xb695149c in QSingleShotTimer::timerEvent (this=0xa5a3c30) at kernel/qtimer.cpp:298
#13 0xb69463bf in QObject::event (this=0xa5a3c30, e=0xbf94bab0) at kernel/qobject.cpp:1075
#14 0xb5f79f54 in QApplicationPrivate::notify_helper (this=0x9d28c88, receiver=0xa5a3c30, e=0xbf94bab0) at kernel/qapplication.cpp:4056
#15 0xb5f8167c in QApplication::notify (this=0xbf94beb4, receiver=0xa5a3c30, e=0xbf94bab0) at kernel/qapplication.cpp:3603
#16 0xb6ebc1aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#17 0xb69366cb in QCoreApplication::notifyInternal (this=0xbf94beb4, receiver=0xa5a3c30, event=0xbf94bab0) at kernel/qcoreapplication.cpp:610
#18 0xb69637ce in QCoreApplication::sendEvent (this=0x9d2be34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#19 QTimerInfoList::activateTimers (this=0x9d2be34) at kernel/qeventdispatcher_unix.cpp:572
#20 0xb69610e0 in timerSourceDispatch (source=0x9d2be00) at kernel/qeventdispatcher_glib.cpp:165
#21 0xb5986e88 in g_main_dispatch (context=0x9d2aef8) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960
#22 IA__g_main_context_dispatch (context=0x9d2aef8) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513
#23 0xb598a730 in g_main_context_iterate (context=0x9d2aef8, block=<value optimized out>, dispatch=1, self=0x9d28f00) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591
#24 0xb598a863 in IA__g_main_context_iteration (context=0x9d2aef8, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#25 0xb696102c in QEventDispatcherGlib::processEvents (this=0x9d109d8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#26 0xb601abe5 in QGuiEventDispatcherGlib::processEvents (this=0x9d109d8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#27 0xb6934c79 in QEventLoop::processEvents (this=0xbf94bd74, flags=) at kernel/qeventloop.cpp:149
#28 0xb69350ca in QEventLoop::exec (this=0xbf94bd74, flags=...) at kernel/qeventloop.cpp:201
#29 0xb693753f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#30 0xb5f79dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#31 0xb774682f in kdemain () from /usr/lib/libkdeinit4_konqueror.so
#32 0x080485cb in _start ()

Reported using DrKonqi
Comment 1 Pino Toscano 2009-12-28 16:46:23 UTC
Hi Ronny,

the backtrace shows it did open a document (a PDF? a CHM? another type?) with Okular.
Do you remember which document it was? If the document is public, can you please attach in this bug report?

Thanks
Comment 2 Ronny Standtke 2010-01-07 18:45:41 UTC
> Do you remember which document it was? If the document is public, can you
> please attach in this bug report?

It was the manual of Privateer (http://privateer.sourceforge.net) that is put into /tmp/ by the installer of the game and opened at the end of the installation process when answering "yes" to the question if you want to open a browser. It is 2 MB large. Let's see if I can attach it...
Comment 3 Ronny Standtke 2010-01-07 18:49:48 UTC
Nope. Unfortunately, the file is too large.
Comment 4 Albert Astals Cid 2010-01-22 00:15:25 UTC
Can you reproduce the crash by opening that pdf in konqueror again?
Comment 5 Ronny Standtke 2010-01-31 14:56:26 UTC
(In reply to comment #4)
> Can you reproduce the crash by opening that pdf in konqueror again?

I just tried several times but I could not reproduce the crash. The PDF has embedded files and I remember that I was trying to take a look at them when everything crashed. But even that I can no longer reproduce. Maybe it is a timing related bug? Is the backtrace alone not sufficient for finding out what went wrong?
Comment 6 Albert Astals Cid 2010-01-31 15:22:40 UTC
No, it is not enough.
Comment 7 Albert Astals Cid 2010-02-20 00:44:29 UTC
The user can't reproduce the crash and the backtrace doens't have enough information to be useful so i'm closing as WORKSFORME. Please if you get another crash that you can reproduce or with a better backtrace do not hesitate to open a new bug.

Thanks for using Okular