Bug 165222 - Konqueror crashes if external application on another desktop tries to open link in new tab (SIGABRT, D-Bus related)
Summary: Konqueror crashes if external application on another desktop tries to open li...
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-28 19:02 UTC by Frank Reininghaus
Modified: 2008-12-16 15:15 UTC (History)
3 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 Frank Reininghaus 2008-06-28 19:02:54 UTC
Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          gcc (GCC) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) 
OS:                Linux

Steps to reproduce:

1. Open Konqueror, make sure that "Open as tab in existing Konqueror when URL is called externally" is enabled in "Settings->Configure Konqueror.../General".
2. Go to another desktop and open KMail.
3. Click on a http:// link in a message.
4. Konqueror crashes bacause of a failed assertion, backtrace below.

Expected behaviour:

Open link in a new tab if there is a Konqueror instance running on the same desktop (this actually happens), but leave Konqueror sessions on other desktops unchanged.

This happens no matter if I run the applications on a KDE3 or KDE4 SVN desktop. I'm running KDE and qt-copy from SVN trunk rev. 825430, compiled on Kubuntu 8.04.

The backtrace looks like it's related to D-Bus. My D-Bus version is 1.1.20-1ubuntu2. I'm not sure if the problem is in Konqueror itself, but I don't know the internals well enough to decide this. 


Application: Konqueror (konqueror), signal SIGABRT
[Thread debugging using libthread_db enabled]
[New Thread 0xb5dcb720 (LWP 6408)]
[New Thread 0xb2938b90 (LWP 6418)]
[KCrash handler]
#6  0xb7f5a410 in __kernel_vsyscall ()
#7  0xb6125085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6126a01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb71db1d8 in qt_message_output (msgType=QtFatalMsg, 
    buf=0xbfe6ad50 "ASSERT: \"false\" in file qdbusmessage.cpp, line 165")
    at global/qglobal.cpp:2058
#10 0xb71db25d in qFatal (msg=0xb7358fa4 "ASSERT: \"%s\" in file %s, line %d")
    at global/qglobal.cpp:2260
#11 0xb71db6d9 in qt_assert (assertion=0xb714f21b "false", 
    file=0xb714f63d "qdbusmessage.cpp", line=165) at global/qglobal.cpp:1828
#12 0xb7122056 in QDBusMessagePrivate::toDBusMessage (message=@0xbfe6cfa8)
    at qdbusmessage.cpp:165
#13 0xb7110aa5 in QDBusConnectionPrivate::send (this=0x80c2ba0, 
    message=@0xbfe6cfa8) at qdbusintegrator.cpp:1629
#14 0xb7115bed in QDBusConnectionPrivate::deliverCall (this=0x80c2ba0, 
    object=0x80f3360, msg=@0x8113208, metaTypes=@0xbfe6d078, slotIdx=17)
    at qdbusintegrator.cpp:878
#15 0xb71167ab in QDBusConnectionPrivate::activateCall (this=0x80c2ba0, 
    object=0x80f3360, flags=256, msg=@0x8113208) at qdbusintegrator.cpp:770
#16 0xb7116dc7 in QDBusConnectionPrivate::activateObject (this=0x80c2ba0, 
    node=@0x81131f4, msg=@0x8113208, pathStartPos=9)
    at qdbusintegrator.cpp:1317
#17 0xb7116eb9 in QDBusActivateObjectEvent::placeMetaCall (this=0x81131c8)
    at qdbusintegrator.cpp:1411
#18 0xb730ad00 in QObject::event (this=0x80f3360, e=0x81131c8)
    at kernel/qobject.cpp:1140
#19 0xb67b5f55 in QApplicationPrivate::notify_helper (this=0x805cb80, 
    receiver=0x80f3360, e=0x81131c8) at kernel/qapplication.cpp:3772
#20 0xb67b623b in QApplication::notify (this=0xbfe6da30, receiver=0x80f3360, 
    e=0x81131c8) at kernel/qapplication.cpp:3366
#21 0xb784f2c7 in KApplication::notify (this=0xbfe6da30, receiver=0x80f3360, 
    event=0x81131c8)
    at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:311
#22 0xb72f524d in QCoreApplication::notifyInternal (this=0xbfe6da30, 
    receiver=0x80f3360, event=0x81131c8) at kernel/qcoreapplication.cpp:587
#23 0xb72f97dd in QCoreApplication::sendEvent (receiver=0x80f3360, 
    event=0x81131c8)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#24 0xb72f57ee in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, 
    event_type=0, data=0x804b6c8) at kernel/qcoreapplication.cpp:1198
#25 0xb72f5a63 in QCoreApplication::sendPostedEvents (receiver=0x0, 
    event_type=0) at kernel/qcoreapplication.cpp:1091
#26 0xb732c33e in QCoreApplication::sendPostedEvents ()
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#27 0xb732b52b in postEventSourceDispatch (s=0x805e790)
    at kernel/qeventdispatcher_glib.cpp:211
#28 0xb5fa5bf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#29 0xb5fa8e5e in ?? () from /usr/lib/libglib-2.0.so.0
#30 0xb5fa93ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#31 0xb732a78c in QEventDispatcherGlib::processEvents (this=0x805a520, 
    flags=@0xbfe6d824) at kernel/qeventdispatcher_glib.cpp:325
#32 0xb6871db0 in QGuiEventDispatcherGlib::processEvents (this=0x805a520, 
    flags=@0xbfe6d854) at kernel/qguieventdispatcher_glib.cpp:204
#33 0xb72f1aca in QEventLoop::processEvents (this=0xbfe6d8dc, 
    flags=@0xbfe6d894) at kernel/qeventloop.cpp:149
#34 0xb72f1d09 in QEventLoop::exec (this=0xbfe6d8dc, flags=@0xbfe6d8e4)
    at kernel/qeventloop.cpp:200
#35 0xb72f5b84 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#36 0xb67b5c6e in QApplication::exec () at kernel/qapplication.cpp:3304
#37 0xb7f3f584 in kdemain (argc=1, argv=0xbfe6dd44)
    at /home/kde-devel/kde/src/KDE/kdebase/apps/konqueror/src/konqmain.cpp:226
#38 0x08048796 in main (argc=)
    at /home/kde-devel/kde/build/KDE/kdebase/apps/konqueror/src/konqueror_dummy.cpp:3
#0  0xb7f5a410 in __kernel_vsyscall ()
Comment 1 Frank Reininghaus 2008-11-08 16:11:51 UTC
This seems to be fixed in trunk rev. 881383. Most likely the root cause is the same as for bug 164307/bug 167667: If I revert the commit that fixed these, the crash is back.
Comment 2 Oka Kurniawan 2008-12-10 10:53:08 UTC
I experience this bug also. Everytime I click URL from KMail, it will open konqueror but the desktop crash.
Comment 3 Frank Reininghaus 2008-12-10 11:03:34 UTC
(In reply to comment #2)
> I experience this bug also. Everytime I click URL from KMail, it will open
> konqueror but the desktop crash.

You have to update to KDE 4.1.3 or later, the bug is fixed now (see my last comment). If you get a different backtrace, please file a new bug report.
Comment 4 Oka Kurniawan 2008-12-10 11:12:23 UTC
I am using KDE 4.2 beta 1. Is the fixed applied to KDE 4.2 also?
Comment 5 Frank Reininghaus 2008-12-10 12:51:19 UTC
(In reply to comment #4)
> I am using KDE 4.2 beta 1. Is the fixed applied to KDE 4.2 also?

Yes, the fix should actually be in 4.2 beta 1. Do you get the same backtrace? If yes, the bug is back (I can't test now because I'm not at home); if not, this is another bug.

Comment 6 Oka Kurniawan 2008-12-16 15:15:25 UTC
sorry took a long time to open the laptop again. Now I couldn't duplicate the error. Maybe because of the updates. Thanks anyway.