Bug 300476 - Konqueror crash
Summary: Konqueror crash
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.8.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-05-22 23:42 UTC by Ivan Ramos
Modified: 2018-10-27 02:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (6.50 KB, text/plain)
2013-07-27 13:41 UTC, Ivan Ramos
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Ramos 2012-05-22 23:42:18 UTC
Application: konqueror (4.8.2 (4.8.2))
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-24-generic-pae i686
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed: I was visiting the Hulu site in the web. Suddenly it close. Right in the moment after the enter key. And i have been having problem to make  the flash player work.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb7778740 (LWP 2331))]

Thread 2 (Thread 0xb4fd4b40 (LWP 2358)):
#0  0x07d7ca6b in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0x07d7d002 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0x07d7d1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x0442c8e7 in QEventDispatcherGlib::processEvents (this=0xb4600468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x043f850d in QEventLoop::processEvents (this=0xb4fd4240, flags=...) at kernel/qeventloop.cpp:149
#5  0x043f87a9 in QEventLoop::exec (this=0xb4fd4240, flags=...) at kernel/qeventloop.cpp:204
#6  0x042e194c in QThread::exec (this=0xa1e5378) at thread/qthread.cpp:501
#7  0x043d5b5d in QInotifyFileSystemWatcherEngine::run (this=0xa1e5378) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x042e4de0 in QThreadPrivate::start (arg=0xa1e5378) at thread/qthread_unix.cpp:298
#9  0x0095fd4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#10 0x00752ace in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb7778740 (LWP 2331)):
[KCrash Handler]
#7  QMetaObject::cast (this=0x1d816d4, obj=0xa09ea00) at kernel/qmetaobject.cpp:293
#8  0x014265ac in qobject_cast<QBoxLayout const*> (object=0xa09ea00) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:389
#9  QLayout::spacing (this=0xa09ea00) at kernel/qlayout.cpp:428
#10 0x018f8157 in QToolBarLayout::updateGeomArray (this=0xa09ea00) at widgets/qtoolbarlayout.cpp:268
#11 0x018f9d92 in QToolBarLayout::layoutActions (this=0xa09ea00, size=...) at widgets/qtoolbarlayout.cpp:421
#12 0x018fa300 in QToolBarLayout::setGeometry (this=0xa09ea00, rect=...) at widgets/qtoolbarlayout.cpp:374
#13 0x01426cb2 in QLayoutPrivate::doResize (this=0xa09ea50, r=...) at kernel/qlayout.cpp:681
#14 0x0142827d in QLayout::activate (this=0xa09ea00) at kernel/qlayout.cpp:1259
#15 0x0142863e in QLayout::widgetEvent (this=0xa09ea00, e=0xb335f60) at kernel/qlayout.cpp:752
#16 0x013f7e92 in notify_helper (e=0xb335f60, receiver=0xa08d018, this=0x9dbbc00) at kernel/qapplication.cpp:4550
#17 QApplicationPrivate::notify_helper (this=0x9dbbc00, receiver=0xa08d018, e=0xb335f60) at kernel/qapplication.cpp:4531
#18 0x013fd3a2 in QApplication::notify (this=0x9dbbc00, receiver=0xa08d018, e=0xb335f60) at kernel/qapplication.cpp:4524
#19 0x01066b21 in KApplication::notify (this=0xbfc7d35c, receiver=0xa08d018, event=0xb335f60) at ../../kdeui/kernel/kapplication.cpp:311
#20 0x043f997e in QCoreApplication::notifyInternal (this=0xbfc7d35c, receiver=0xa08d018, event=0xb335f60) at kernel/qcoreapplication.cpp:876
#21 0x043fdad8 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#22 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9d99370) at kernel/qcoreapplication.cpp:1500
#23 0x043fde0c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1393
#24 0x0442c494 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#25 postEventSourceDispatch (s=0x9dbeca0) at kernel/qeventdispatcher_glib.cpp:279
#26 0x07d7ccda in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#27 0x07d7d0e5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#28 0x07d7d1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#29 0x0442c887 in QEventDispatcherGlib::processEvents (this=0x9d99f08, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#30 0x014b0aaa in QGuiEventDispatcherGlib::processEvents (this=0x9d99f08, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#31 0x043f850d in QEventLoop::processEvents (this=0xbfc7d1e4, flags=...) at kernel/qeventloop.cpp:149
#32 0x043f87a9 in QEventLoop::exec (this=0xbfc7d1e4, flags=...) at kernel/qeventloop.cpp:204
#33 0x043fdeba in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#34 0x013f5a74 in QApplication::exec () at kernel/qapplication.cpp:3820
#35 0x00293695 in kdemain (argc=2, argv=0xbfc7d6b4) at ../../../konqueror/src/konqmain.cpp:242
#36 0x0804850b in main (argc=2, argv=0xbfc7d6b4) at konqueror_dummy.cpp:3

Reported using DrKonqi
Comment 1 Andrea Iacovitti 2012-05-23 08:17:41 UTC
What's the url of the site you are visiting?
Is there a way to reliable reproduce the crash?
Comment 2 Dawit Alemayehu 2012-08-21 22:10:19 UTC
which browser engine ? Also please provide a specific link you were visitng if at all possible as requested in comment #1.
Comment 3 Ivan Ramos 2013-07-27 13:41:57 UTC
Created attachment 81381 [details]
New crash information added by DrKonqi

konqueror (4.8.5 (4.8.5)) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1

- What I was doing when the application crashed: Iwas tring to visit the news paper call elnuevodia.com. And i was using  the Konqueror browser because is the only one i can use use to see the news paper. In the past the problem couln't be reported. The crash always happend but once i restart the aplication the conection ocurre, so i can see the newspaper. This crash happend using other browser. I mean using rekonq. But the crash reporting assitent can't find the right debugger. So i had to close the reporting assistant whit out the input necesary.

-- Backtrace (Reduced):
#8  0x02efe5ac in qobject_cast<QBoxLayout const*> (object=0x8aa7000) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:389
#9  QLayout::spacing (this=0x8aa7000) at kernel/qlayout.cpp:428
#10 0x033d0167 in QToolBarLayout::updateGeomArray (this=0x8aa7000) at widgets/qtoolbarlayout.cpp:268
#11 0x033d1da2 in QToolBarLayout::layoutActions (this=0x8aa7000, size=...) at widgets/qtoolbarlayout.cpp:421
#12 0x033d2310 in QToolBarLayout::setGeometry (this=0x8aa7000, rect=...) at widgets/qtoolbarlayout.cpp:374
Comment 4 Andrew Crouthamel 2018-09-24 02:24:05 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 5 Andrew Crouthamel 2018-10-27 02:33:18 UTC
Dear Bug Submitter,

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!