Bug 267652

Summary:	KDE applications don't work over remote X connections
Product:	[I don't know] kde	Reporter:	Andreas Pietzowski <andreas>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	andreas, cfeck, de.techno
Priority:	NOR
Version:	4.6
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Andreas Pietzowski 2011-03-04 20:30:06 UTC

Version:           4.6 (using Devel) 
OS:                Linux

When I connect to my computer over "ssh -X <IP>" I can start almost every
graphical application like xeyes and thunderbird e.g. But KDE applications quit immediately due to a dbus problem.

This bug exists at least since KDE 4.5! Would be nice to see this fixed soon because normally KDE is very prod of its network transparancy.

Reproducible: Didn't try

Steps to Reproduce:
First off, don't use KDE on both sides! In my case I have an apple laptop with XQuartz installed and I want to get a KDE window to my mac from a remote KDE machine. ssh -X to my KDE desktop though.

Try to start xeyes - it starts up and shows the "window" on my Mac. KDE applications simply just quit!

Actual Results:  
This error message is reported on the remote shell:

unnamed app(4369): KUniqueApplication: Cannot find the D-Bus session server:  
"Failed to connect to socket /tmp/dbus-jg4voufHiB: Connection refused" 
unnamed app(4368): KUniqueApplication: Pipe closed unexpectedly.

Expected Results:  
A nicely popping-up KDE window :)

Comment 1 Andreas Pietzowski 2011-03-04 21:56:13 UTC

I found the soultion. Type the following after you have successfully logged in to the remote machine over ssh:

export `dbus-launch`

This command sets and exports the shell variables $DBUS_SESSION_BUS_ADDRESS and $DBUS_SESSION_BUS_PID.

Is there a way for KDE to detect the described dbus problem in advance and then set the two system variables in the beackground before starting the application?

Comment 2 Andreas Pietzowski 2011-03-20 21:01:21 UTC

Your solution works, great! ;-)

Due to the auto detect: Sure it can be detected. The starting application crashes when the dbus can't be found. Every application can detect it's crash and call a method. I am not a KDE programmer and don't know where to write this piece of code. But in my opinion it should be a very easy implementation.

It would be nice if there is someone out there who is familiar with the starting process of KDE applications whie connecting to the dbus.

This feature is mandatory for KDE to be "network transparent" :-)

Thanks in advance.

Comment 3 Christoph Feck 2011-03-21 03:17:33 UTC

Please do not change bug status.

Comment 4 Andreas Pietzowski 2012-04-25 20:49:20 UTC

Is nobody (aside me *g) annoyed about the issue that you cannot directly start KDE applications when connected via "ssh -X"? Isn't there a way to automate the export variable?

Comment 5 dE 2012-06-18 17:24:57 UTC

You've setup a trusted X11 forward? Maybe it's related to this?

Comment 6 Andreas Pietzowski 2012-06-18 20:52:04 UTC

Works wioth new installation of kubuntu. Don't know the reason before. Can't reproduce anymore...