Bug 343613 - Dolphin hangs when opening a file with Kate while Kate is already open
Summary: Dolphin hangs when opening a file with Kate while Kate is already open
Status: RESOLVED DUPLICATE of bug 339094
Alias: None
Product: frameworks-kservice
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-31 06:21 UTC by Andrew Chen
Modified: 2015-02-02 16:28 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 Andrew Chen 2015-01-31 06:21:22 UTC
Opening a file in Dolphin with Kate while Kate is already open causes Dolphin to hang. Closing the tab (in Kate) of the opened file causes Dolphin to display an error message: "KDEInit could not launch '/usr/bin/kate'". After pressing OK, everything returns back to normal.
This causes major disruption in my workflow since I can no longer open multiple files in Kate using Dolphin. Also, I have not found an workaround.

Reproducible: Always

Steps to Reproduce:
1. Open Kate
2. Open a file with Kate in Dolphin
3. Test if Dolphin is responsive
4. Close the opened file's tab in Kate
5. Test again if Dolphin is responsive

Actual Results:  
a. Dolphin hangs after opening file
b. Dolphin displays error message after closing tab

Expected Results:  
a. Dolphin should stay responsive after opening file
b. Dolphin should not encounter an error after closing tab

Versions:
Dolphin:
Version 14.11.97
Using KDE Development Platform 4.14.4
Kate:
Version 5.0.0
Using KDE Frameworks 5.6.0

Package Versions:
kdebase-dolphin 14.12.1-2
kdelibs 4.14.4-1
kate 14.12.1-4
Comment 1 Frank Reininghaus 2015-01-31 08:41:22 UTC
Thanks for the bug report. I can reproduce this with both Dolphin 4.x and the KF5-based version (provided Kate 5 is running when selecting "Open with..." in Dolphin. The backtraces look similar (blocks in DBus code that is called from KToolInvocation (which is used by KRun). So the problem seems to be in KService or KIO.

Backtrace with the KF5 version of Dolphin:

Thread 1 (Thread 0x7ffff7f837c0 (LWP 2709)):
#0  0x00007fffee6cb3cd in poll () from /lib64/libc.so.6
#1  0x00007fffe49a7ff8 in ?? () from /lib64/libdbus-1.so.3
#2  0x00007fffe49a6f5f in ?? () from /lib64/libdbus-1.so.3
#3  0x00007fffe499162c in ?? () from /lib64/libdbus-1.so.3
#4  0x00007fffe4991fd9 in ?? () from /lib64/libdbus-1.so.3
#5  0x00007fffe499259d in dbus_connection_send_with_reply_and_block () from /lib64/libdbus-1.so.3
#6  0x00007fffef9841a3 in q_dbus_connection_send_with_reply_and_block (connection=0x6628a0, message=0x6630b0, 
    timeout_milliseconds=2147483647, error=0x7fffffff6560) at qdbus_symbols_p.h:135
#7  0x00007fffef98e83e in QDBusConnectionPrivate::sendWithReply (this=0x6615f0, message=..., sendMode=1, timeout=2147483647)
    at qdbusintegrator.cpp:1959
#8  0x00007fffef97c537 in QDBusConnection::call (this=0x7fffffff6a30, message=..., mode=QDBus::Block, timeout=2147483647)
    at qdbusconnection.cpp:584
#9  0x00007ffff35a6032 in KToolInvocation::startServiceInternal (this=
    0x7ffff3817650 <(anonymous namespace)::Q_QGS_s_self::innerFunction()::holder>, 
    _function=0x7ffff35f21dd "start_service_by_desktop_path", _name=..., URLs=..., error=0x7fffffff6c20, serviceName=0x0, 
    pid=0x7fffffff6c1c, startup_id=..., noWait=false, workdir=...)
    at /home/kde-frameworks/kde/src/frameworks/kservice/src/kdeinit/ktoolinvocation.cpp:99
#10 0x00007ffff35a6787 in KToolInvocation::startServiceByDesktopPath (_name=..., URLs=..., error=0x7fffffff6c20, serviceName=0x0, 
    pid=0x7fffffff6c1c, startup_id=..., noWait=false)
    at /home/kde-frameworks/kde/src/frameworks/kservice/src/kdeinit/ktoolinvocation.cpp:190
#11 0x00007ffff571f9c1 in KRun::runService (_service=..., _urls=..., window=0x6db300, tempFiles=false, suggestedFileName=..., 
    asn=...) at /home/kde-frameworks/kde/src/frameworks/kio/src/widgets/krun.cpp:768
#12 0x00007ffff56f7ec9 in KFileItemActionsPrivate::slotRunApplication (this=0xa1c090, act=0xa4a4e0)
Comment 2 Arjun AK 2015-02-02 16:28:12 UTC

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