Bug 206141 - Konqueror crashes in Bookmark Editor
Summary: Konqueror crashes in Bookmark Editor
Status: RESOLVED DUPLICATE of bug 181856
Alias: None
Product: konqueror
Classification: Applications
Component: bookmarks (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-03 17:44 UTC by masinick
Modified: 2009-09-03 18:30 UTC (History)
2 users (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 masinick 2009-09-03 17:44:37 UTC
Application that crashed: konqueror
Version of the application: 4.3.1 (KDE 4.3.1)
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-5.dmz.10-liquorix-686 i686
Distribution: Debian GNU/Linux unstable (sid)

What I was doing when the application crashed:
I tried to drag and drop a menu entry in the Bookmark Editor and got a crash.  Also got a crash when using multiple tabs and attempting to update something, but I have not yet duplicated that scenario.

 -- Backtrace:
Application: Konqueror (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  0xb7671caa in KTextEdit::highlighter() const () from /usr/lib/libkdeui.so.5
#7  0xb2bd3eff in ?? () from /usr/lib/libkhtml.so.5
#8  0xb2bd7e8f in ?? () from /usr/lib/libkhtml.so.5
#9  0xb2b51a43 in ?? () from /usr/lib/libkhtml.so.5
#10 0xb2ae7ee2 in ?? () from /usr/lib/libkhtml.so.5
#11 0xb2ae80b6 in ?? () from /usr/lib/libkhtml.so.5
#12 0xb2a41fad in KHTMLView::dispatchMouseEvent(int, DOM::NodeImpl*, DOM::NodeImpl*, bool, int, QMouseEvent*, bool, int, int) () from /usr/lib/libkhtml.so.5
#13 0xb2a505c2 in KHTMLView::mousePressEvent(QMouseEvent*) () from /usr/lib/libkhtml.so.5
#14 0xb6b7287e in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#15 0xb6f18f53 in QFrame::event(QEvent*) () from /usr/lib/libQtGui.so.4
#16 0xb2a4b06f in KHTMLView::widgetEvent(QEvent*) () from /usr/lib/libkhtml.so.5
#17 0xb2a4b315 in KHTMLView::eventFilter(QObject*, QEvent*) () from /usr/lib/libkhtml.so.5
#18 0xb7e73bfa in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#19 0xb6b1c7ec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#20 0xb6b252e1 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#21 0xb75654ad in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#22 0xb7e749cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#23 0xb6b2436e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&) () from /usr/lib/libQtGui.so.4
#24 0xb6b92ea5 in ?? () from /usr/lib/libQtGui.so.4
#25 0xb6b92386 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4
#26 0xb6bbc892 in ?? () from /usr/lib/libQtGui.so.4
#27 0xb66ea4b8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#28 0xb66eda13 in ?? () from /usr/lib/libglib-2.0.so.0
#29 0xb66edb98 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#30 0xb7e9f858 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#31 0xb6bbbfd5 in ?? () from /usr/lib/libQtGui.so.4
#32 0xb7e7301a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#33 0xb7e73462 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#34 0xb7e758b9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#35 0xb6b1c697 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#36 0xb4a9b3df in kdemain () from /usr/lib/libkdeinit4_konqueror.so
#37 0x0804e291 in _start ()

Reported using DrKonqi
Comment 1 FiNeX 2009-09-03 18:23:41 UTC
could this be a dup of bug #181856 ?
Comment 2 masinick 2009-09-03 18:30:21 UTC
I am willing to consider this particular defect a duplicate of bug #181856 and I also acknowledge that bug #181856 has superior descriptions of the environment and how to reproduce the defect, so if you can fix bug #181856 then this defect can be closed as well.

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