This forum has been archived. All content is frozen. Please use KDE Discuss instead.

X11 Forwarding not working in Qt apps

Tags: None
(comma "," separated)
archtaku
Registered Member
Posts
26
Karma
0
OS
I can forward any X11 app over SSH, with the exception of Qt-based apps. You can find some verbose output from an "ssh -X" login at the below link. When I try starting konsole, kmymoney, okular, konqueror, etc. it fails, but I can launch xeyes, gimp, chromium, etc. with no problem. No Qt-based app will work with X11 forwarding.

http://pastebin.com/1ha87vjt
User avatar
Hans
Administrator
Posts
3304
Karma
24
OS
Have you tried with ssh -Y? I think it worked for me the last time I tried.


Problem solved? Please click on "Accept this answer" below the post with the best answer to mark your topic as solved.

10 things you might want to do in KDE | Open menu with Super key | Mouse shortcuts
archtaku
Registered Member
Posts
26
Karma
0
OS
Nope, not working. Maybe it has something to do with Desktop Effects being on?

EDIT: No, I just disabled desktop effects on that box and there's been no change.
User avatar
dpalacio
Registered Member
Posts
240
Karma
2
OS
All the examples you gave and the qt application you tested in the attached log are KDE apps. Do non-kde Qt apps fail to appear as well? e.g. qdbusviewer, assistant.

Something in the KDE runtime might be failing to start or is locked.


connect(post, SIGNAL(readSignature()), qapp, SLOT(quit()));
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
The problem seems to be that the remote host does not have access to the D-Bus session bus.

I suggest running "export `dbus-launch`" prior to attempting to launch the session bus, assuming the home dirs aren't shared. Running "kdeinit4" will also ensure KDE infrastructure is running, although KDE apps should automatically start this if needed.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
archtaku
Registered Member
Posts
26
Karma
0
OS
bcooksley wrote:The problem seems to be that the remote host does not have access to the D-Bus session bus.

I suggest running "export `dbus-launch`" prior to attempting to launch the session bus, assuming the home dirs aren't shared. Running "kdeinit4" will also ensure KDE infrastructure is running, although KDE apps should automatically start this if needed.


Thanks. Exporting those variables worked.
archtaku
Registered Member
Posts
26
Karma
0
OS
I believe I found the root problem.

Code: Select all
ejohnson@dfwejohnson:~/.dbus/session-bus$ ls -la
total 20
drwx------ 2 ejohnson users 4096 Jul 30 16:51 .
drwx------ 3 ejohnson users 4096 Jul 15 17:17 ..
-rw-r--r-- 1 ejohnson users  463 Nov 25 01:04 7534c4642d8706fc6fd8e1620000090a-0
-rw-r--r-- 1 root     root   476 Aug  8 16:56 7534c4642d8706fc6fd8e1620000090a-10
-rw-r--r-- 1 ejohnson users  477 Nov 25 13:07 7534c4642d8706fc6fd8e1620000090a-11


Notice how the file with offset 10 (the default DISPLAY offset for an X-forwarded SSH session) is owned by root and not writeable by my username. After looking at the file and noticing that it contained the same variables, I figured the problem was that my user couldn't write to the file, so I chown'ed it back to ejohnson:users and commented out the bits I added to start a session dbus, and now forwarding works perfectly for Qt apps.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]