Bug 270178 - dolphin freeze due to dbus when started in a remote kppp or ssh session
Summary: dolphin freeze due to dbus when started in a remote kppp or ssh session
Status: RESOLVED FIXED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 1.6.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-05 21:44 UTC by Yagi858
Modified: 2018-04-15 16:03 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 Yagi858 2011-04-05 21:44:23 UTC
Version:           unspecified (using KDE 4.6.1) 
OS:                Linux

When starting a kppp session or ssh session to remote filesystem dolphin freeze if open, or very slow to start and not usable.

The message when launch dolphin is:
"unnamed app(13416): Communication problem with  "dolphin" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

Reproducible: Always

Steps to Reproduce:
launch kppp session (same is wvdial session) or launch ssh session to remote filesystem

Actual Results:  
Impossible to restore by starting dbus daemon. System restart is the solution.


dbus 1.4.1
Comment 1 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:18:33 UTC
Resetting assignee to default as per bug #305719
Comment 2 Adrián Chaves (Gallaecio) 2012-10-30 07:25:35 UTC
Could you please be a bit more specific in the steps to reproduce?

For example, would this be right?
1. Open a terminal.
2. Connect to a remote computer using SSH: ssh user@host
3. Open Dolphin in the remote computer from the terminal running the SSH session:
    $ dolphin

Also, do other graphical applications work?
Comment 3 Julian Steinmann 2018-03-30 09:35:45 UTC
Can you still reproduce this bug with Dolphin 17.12.3? If not, I'll close this bug soon.
Comment 4 Julian Steinmann 2018-04-15 16:03:28 UTC
No response -> closing. Thanks for reporting this bug, please reopen the report if you can still reproduce this behavior with newer versions of Dolphin.