[Bug 281034] New: KDE4.7 applications don't work easily via ssh-tunnels

[Diego Ercolani]

https://bugs.kde.org/show_bug.cgi?id=281034

           Summary: KDE4.7 applications don't work easily via ssh-tunnels
           Product: kde
           Version: 4.7
          Platform: openSUSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: diego.ercolani at gmail.com


Version:           4.7 (using KDE 4.7.0) 
OS:                Linux

One useful thing of linux desktop is the (storical) possibility to launch
application remotely and use local terminal only for display purposes. With the
new KDE approach it seems that this it isn't possible anymore as a local dbus
messaging server is involved (sorry for my lack of knowlegde), but the result
is that this service isn't usable anymore.
For evidence purpose I attach a session dump where I try to launch before xterm
(successfully to highlight that X11 environment is correct) and then I try to
launch konqueror then, as suggested by the console I issue the command export
$(dbus-launch) and the environment correctly permit to launch konqueror but I
have a lot of warning and

pc-diego:~ # useradd -m pippo
pc-diego:~ # passwd pippo
Changing password for pippo.
New Password: 
Bad password: too simple
Reenter New Password: 
Password changed.
pc-diego:~ # logout
SSISNET\diego at pc-diego:~> ssh -CX pippo at 127.0.0.1
Password: 
Have a lot of fun...
/usr/bin/xauth:  file /home/pippo/.Xauthority does not exist
pippo at pc-diego:~> xterm
pippo at pc-diego:~> konqueror 
konqueror(10143)/kdeui (kdelibs): Session bus not found 
To circumvent this problem try the following command (with Linux and bash) 
export $(dbus-launch) 
KCrash: Application 'konqueror' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
sock_file=/home/pippo/.kde4/socket-pc-diego/kdeinit4_localhost_10
Warning: connect() failed: : File o directory non esistente
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi directly
drkonqi(10145)/kdeui (kdelibs): Session bus not found 
To circumvent this problem try the following command (with Linux and bash) 
export $(dbus-launch) 
pippo at pc-diego:~> export $(dbus-launch) 
pippo at pc-diego:~> konqueror
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Cannot connect to server socket err = File o directory non esistente
Cannot connect to server socket
jack server is not running or cannot be started
kbuildsycoca4 running...
"KConfigIni: In file /tmp/kde-pippo/kconf_updateX11070.tmp, line 1: " Invalid
entry (missing '=') 
Cannot connect to server socket err = File o directory non esistente
Cannot connect to server socket
jack server is not running or cannot be started
grepHelper: File does not exists:  "/proc/asound/card1/pcm0p/info" 
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x8400018
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x8400018
Cannot connect to server socket err = File o directory non esistente
Cannot connect to server socket
jack server is not running or cannot be started
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 18 (X_ChangeProperty)
  Resource id:  0x8400018
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x8a00018
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x8a00018
Cannot connect to server socket err = File o directory non esistente
Cannot connect to server socket
jack server is not running or cannot be started
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 18 (X_ChangeProperty)
  Resource id:  0x8a00018
pippo at pc-diego:~> 

Reproducible: Always



Expected Results:  
like xterm.... simply without any environment setting 

Opened a bug request under bugs.novell.com
(https://bugzilla.novell.com/show_bug.cgi?id=714893) they asked to open an
upstream bugrequest as is envolved the architecture

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.