Bug 298169 - konqueror crash after log in into web.de
Summary: konqueror crash after log in into web.de
Status: RESOLVED DUPLICATE of bug 298041
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-15 08:43 UTC by bostaurus
Modified: 2012-04-15 08:53 UTC (History)
1 user (show)

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 bostaurus 2012-04-15 08:43:02 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-23-generic-pae i686
Distribution: Ubuntu precise (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
I had opened konqueror and logged in web.de, it crashed.
This reaction is typically. Only yesterday it worked fine.(Saturday, 2012-04-14)

-- 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 0xb4c0e740 (LWP 2762))]

Thread 2 (Thread 0xb1ed5b40 (LWP 2763)):
#0  0xb77a3424 in __kernel_vsyscall ()
#1  0xb75df380 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0xb5235a8b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb522806e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb52281c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb67268e7 in QEventDispatcherGlib::processEvents (this=0xb1500468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0xb66f250d in QEventLoop::processEvents (this=0xb1ed5240, flags=...) at kernel/qeventloop.cpp:149
#7  0xb66f27a9 in QEventLoop::exec (this=0xb1ed5240, flags=...) at kernel/qeventloop.cpp:204
#8  0xb65db94c in QThread::exec (this=0x9587e10) at thread/qthread.cpp:501
#9  0xb66cfb5d in QInotifyFileSystemWatcherEngine::run (this=0x9587e10) at io/qfilesystemwatcher_inotify.cpp:248
#10 0xb65dede0 in QThreadPrivate::start (arg=0x9587e10) at thread/qthread_unix.cpp:298
#11 0xb52efd4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0xb75edace in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb4c0e740 (LWP 2762)):
[KCrash Handler]
#7  0xb01594a4 in type (this=0xaf0578a0) at ../../kjs/value.h:452
#8  KJS::cloneInternal (exec=0x9d903b0, ctx=0x9d903a0, in=0xaf0578a0, path=...) at ../../khtml/ecma/kjs_data.cpp:37
#9  0xb01599bd in KJS::encapsulateMessageEventData (exec=0x9d903b0, ctx=0x9d903a0, data=0xaf0578a0) at ../../khtml/ecma/kjs_data.cpp:117
#10 0xb0159bab in KJS::DelayedPostMessage::execute (this=0xb10b1a8, w=0x0) at ../../khtml/ecma/kjs_data.cpp:169
#11 0xb01084d4 in KJS::Window::afterScriptExecution (this=0xb0c30040) at ../../khtml/ecma/kjs_window.cpp:1327
#12 0xb013291c in KJS::JSEventListener::handleEvent (this=0xae2b770, evt=...) at ../../khtml/ecma/kjs_events.cpp:121
#13 0xaff44086 in DOM::EventTargetImpl::handleLocalEvents (this=0x9a84168, evt=0xa7da180, useCapture=false) at ../../khtml/xml/dom2_eventsimpl.cpp:62
#14 0xaff1c6c1 in DOM::NodeImpl::dispatchGenericEvent (this=0xb2ccb68, evt=0xa7da180) at ../../khtml/xml/dom_nodeimpl.cpp:469
#15 0xaff1c7bf in DOM::NodeImpl::dispatchWindowEvent (this=0xb2ccb68, evt=0xa7da180) at ../../khtml/xml/dom_nodeimpl.cpp:542
#16 0xaff9d013 in event (e=0x992bed0, this=0xb2ccb60) at ../../khtml/html/html_objectimpl.cpp:149
#17 DOM::HTMLPartContainerElementImpl::event (this=0xb2ccb60, e=0x992bed0) at ../../khtml/html/html_objectimpl.cpp:146
#18 0xb5b5eed4 in notify_helper (e=0x992bed0, receiver=0xb2ccb60, this=0x911c5e0) at kernel/qapplication.cpp:4559
#19 QApplicationPrivate::notify_helper (this=0x911c5e0, receiver=0xb2ccb60, e=0x992bed0) at kernel/qapplication.cpp:4531
#20 0xb5b6430d in QApplication::notify (this=0x992bed0, receiver=0xb2ccb60, e=0x992bed0) at kernel/qapplication.cpp:4288
#21 0xb6d0eb21 in KApplication::notify (this=0xbfed24dc, receiver=0xb2ccb60, event=0x992bed0) at ../../kdeui/kernel/kapplication.cpp:311
#22 0xb66f397e in QCoreApplication::notifyInternal (this=0xbfed24dc, receiver=0xb2ccb60, event=0x992bed0) at kernel/qcoreapplication.cpp:876
#23 0xb66f7ad8 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x90f8370) at kernel/qcoreapplication.cpp:1500
#25 0xb66f7e0c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1393
#26 0xb6726494 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#27 postEventSourceDispatch (s=0x911dbe8) at kernel/qeventdispatcher_glib.cpp:279
#28 0xb5227cda in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#29 0xb52280e5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#30 0xb52281c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#31 0xb6726887 in QEventDispatcherGlib::processEvents (this=0x90f8ef0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#32 0xb5c17aaa in QGuiEventDispatcherGlib::processEvents (this=0x90f8ef0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0xb66f250d in QEventLoop::processEvents (this=0xbfed2364, flags=...) at kernel/qeventloop.cpp:149
#34 0xb66f27a9 in QEventLoop::exec (this=0xbfed2364, flags=...) at kernel/qeventloop.cpp:204
#35 0xb66f7eba in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#36 0xb5b5ca74 in QApplication::exec () at kernel/qapplication.cpp:3820
#37 0xb7773695 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_konqueror.so
#38 0x0804850b in ?? ()
#39 0xb751c4d3 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
#40 0x08048531 in _start ()

This bug may be a duplicate of or related to bug 298041.

Possible duplicates by query: bug 298041, bug 296811, bug 295740, bug 294794, bug 292992.

Reported using DrKonqi
Comment 1 Jekyll Wu 2012-04-15 08:53:42 UTC

*** This bug has been marked as a duplicate of bug 298041 ***