Bug 220811 - Konqueror Amarok JVN Pidgin
Summary: Konqueror Amarok JVN Pidgin
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Bugs
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-12-31 15:07 UTC by Paul Arzelier
Modified: 2018-10-21 05:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Arzelier 2009-12-31 15:07:43 UTC
Application that crashed: konqueror
Version of the application: 4.3.2 (KDE 4.3.2)
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-16-generic x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I was using pidgin, irc, konqueror and Amarok,  and when I selected the "next" link of a page in Jeux video network in the top 100 of video games, amarok freezed 10 seconds and crashed.

 -- Backtrace:
Application: Konqueror (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f5460a65af6 in ?? () from /usr/lib/libkhtml.so.5
#6  0x00007f5473ee7d83 in QObject::event (this=0x3680b10, e=0x318b888) at kernel/qobject.cpp:1075
#7  0x00007f5471e88efc in QApplicationPrivate::notify_helper (this=0x25c3580, receiver=0x3680b10, e=0x7fff2af2d330) at kernel/qapplication.cpp:4056
#8  0x00007f5471e901ce in QApplication::notify (this=0x7fff2af2d7d0, receiver=0x3680b10, e=0x7fff2af2d330) at kernel/qapplication.cpp:4021
#9  0x00007f5472abfab6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#10 0x00007f5473ed8c2c in QCoreApplication::notifyInternal (this=0x7fff2af2d7d0, receiver=0x3680b10, event=0x7fff2af2d330) at kernel/qcoreapplication.cpp:610
#11 0x00007f5473f03862 in QCoreApplication::sendEvent (this=0x25d14f0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#12 QTimerInfoList::activateTimers (this=0x25d14f0) at kernel/qeventdispatcher_unix.cpp:572
#13 0x00007f5473f0125d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#14 0x00007f5470db9bce in g_main_dispatch (context=0x25d01f0) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960
#15 IA__g_main_context_dispatch (context=0x25d01f0) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513
#16 0x00007f5470dbd598 in g_main_context_iterate (context=0x25d01f0, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>)
    at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591
#17 0x00007f5470dbd6c0 in IA__g_main_context_iteration (context=0x25d01f0, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#18 0x00007f5473f011a6 in QEventDispatcherGlib::processEvents (this=0x2544040, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#19 0x00007f5471f1d4be in QGuiEventDispatcherGlib::processEvents (this=0x2e17018, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#20 0x00007f5473ed7532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#21 0x00007f5473ed7904 in QEventLoop::exec (this=0x7fff2af2d5d0, flags=) at kernel/qeventloop.cpp:201
#22 0x00007f5473ed9ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#23 0x00007f54681ace26 in kdemain () from /usr/lib/libkdeinit4_konqueror.so
#24 0x0000000000406da8 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-31 15:14:05 UTC
Thanks for the report! 
The backtrace is missing an important bit of information
- If you can reproduce the crash at will (or you experience this regularly), can you install the "kdelibs5-dbg" package and post a complete backtrace here? Thanks
Comment 2 Andrew Crouthamel 2018-09-20 03:20:59 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-21 05:22:28 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!