Hello everyone.
I was running OpenSUSE 12.3 and my VPN and Remote Desktop worked perfectly for SSH, VNC, and RDP. I ran the 13.1 upgrade and it installed with no issues. But now I cannot connect with remote desktop. The VPN connection works fine, and I can start the Remote Desktop application. I can connect with SSH, but both VNC and RDP do nothing. No screen blink, no error, just nothing.
Anyone have an idea where I can look? (I did turn off the firewall, too.)
Thanks for any help.
Matt
Hi Matt,
I’ve just installed a fresh copy of 13.1 (XFCE) and I get the same results for XRDP.
I can authenticate but just get a blank black screen.
Chris
Hi Matt,
I get the same results with KDE (just a black screen, after authenticating into my 13.1 box via XRDP).
Chris
Hi Chris,
Right before I went to bed last night I think I found the problem. In /var/log/messages I see that there are certificate errors. It is trying to ask if I want to accept the certificate, but cannot because there is no standard input device.
I don’t know how to fix that, so I’ll have to do some more reading.
Can you try a remote desktop session and then check the end of /var/log/messages to see if you are getting the same error?
Matt
Hi Matt,
This is what I am getting with KDE at the moment.
2013-11-21T14:53:21.314080+00:00 l044 su: (to chris) chris on none
2013-11-21T14:53:21.315153+00:00 l044 su: pam_unix(su:session): session opened for user root by (uid=1000)
2013-11-21T14:53:21.324462+00:00 l044 su: pam_unix(su:session): session closed for user root
2013-11-21T14:53:21.535810+00:00 l044 su: (to chris) chris on none
2013-11-21T14:53:21.536425+00:00 l044 su: pam_unix(su:session): session opened for user root by (uid=1000)
2013-11-21T14:53:48.479626+00:00 l044 XRDP-sesman[3709]: (3709)(-1221371584)[INFO ] shutting down sesman 1
2013-11-21T14:53:48.497502+00:00 l044 XRDP-sesman[4094]: (4094)(-1221764800)[WARN ] [init:47] libscp initialized
2013-11-21T14:53:48.501361+00:00 l044 XRDP-sesman[4095]: (4095)(-1221764800)[CORE ] starting sesman with pid 4095
2013-11-21T14:53:48.507589+00:00 l044 XRDP-sesman[4095]: (4095)(-1221764800)[INFO ] listening…
2013-11-21T14:53:48.509274+00:00 l044 XRDP-sesman[4095]: (4095)(-1221764800)[ERROR] bind error on port ‘3350’: 98 (Address already in use)
2013-11-21T14:53:52.610734+00:00 l044 XRDP[4100]: (4100)(-1221978368)[WARN ] local keymap file for 0x0809 found and dosen’t match built in keymap, using local keymap file
2013-11-21T14:55:58.384381+00:00 l044 su: (to chris) chris on none
2013-11-21T14:55:58.385175+00:00 l044 su: pam_unix(su:session): session opened for user root by (uid=1000)
2013-11-21T14:55:58.393837+00:00 l044 su: pam_unix(su:session): session closed for user root
2013-11-21T14:55:58.610337+00:00 l044 su: (to chris) chris on none
2013-11-21T14:55:58.611096+00:00 l044 su: pam_unix(su:session): session opened for user root by (uid=1000)
2013-11-21T14:56:02.994972+00:00 l044 dbus[491]: [system] Activating service name=‘org.freedesktop.PackageKit’ (using servicehelper)
2013-11-21T14:56:03.034669+00:00 l044 dbus[491]: [system] Successfully activated service ‘org.freedesktop.PackageKit’
2013-11-21T14:56:37.856510+00:00 l044 su: pam_unix(su:session): session closed for user root
2013-11-21T14:57:02.698529+00:00 l044 XRDP[4220]: (4220)(-1221978368)[WARN ] local keymap file for 0x0809 found and dosen’t match built in keymap, using local keymap file
2013-11-21T14:57:29.916264+00:00 l044 dbus[491]: [system] Activating service name=‘org.freedesktop.PackageKit’ (using servicehelper)
2013-11-21T14:57:29.965414+00:00 l044 dbus[491]: [system] Successfully activated service ‘org.freedesktop.PackageKit’
I have not got my XFCE box any more as it has become KDE.
Chris
Well, that is definitely not the error I was getting. In your log file, this looks suspicious to me:
ERROR] bind error on port ‘3350’: 98 (Address already in use)
I am unfamiliar with port 3350 so I looked it up and it is registered to FINDVIATV. I have no idea what that means, but I’m fairly certain we are looking at two different issues. I’m guessing for your problem you should do a
netstat -an | grep 3350
and see what is using that port.
Matt
Hi Matt,
I agree, we do seem to have different errors.
I will leave it for now, and post again once I have got it all working. I found it hard to get XRDP to work on 12.3
Thanks for your help and for getting back to me.
Chris
Wow. Still having this same issue in OpenSUSE 13.1 Thought by now it would have been fixed.
Yes! Me too, very frustrating!
Does anybody have an idea about this?
Björn
When connecting to gnome and after the login if it shows blank screen with only cursor then you need to load the rdp session in fall back mode.
You can look into this.
windows 7 - Blank desktop when logging in via xrdp - Ask Ubuntu
Hello,
i have the same problem, i decide to use x2go and it work like charm in 13.1.
Repository
OBS Remonte Desktop
URL: Index of /repositories/X11:/RemoteDesktop:/x2go/openSUSE_13.1
Category: YUM
information how to set up,
https://wiki.archlinux.org/index.php/X2Go
Regards
Czeslaw M.
Similar problem but session gets closed immediately after connection
SuSE 13.1; using KDE
Client using tightvnc 1.3.10
relative log entries from /var/log/messages:
2013-12-12T18:12:50.897720-05:00 linuxSQL xinetd[606]: START: vnc1 from=192.168.2.49
2013-12-12T18:12:51.009020-05:00 linuxSQL kdm_config[3303]: Multiple occurrences of section [General] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
2013-12-12T18:12:51.009501-05:00 linuxSQL kdm_config[3303]: Multiple occurrences of section [Xdmcp] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
2013-12-12T18:12:51.009891-05:00 linuxSQL kdm_config[3303]: Multiple occurrences of section [X--Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
2013-12-12T18:12:51.010306-05:00 linuxSQL kdm_config[3303]: Multiple occurrences of section [X--Greeter] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
2013-12-12T18:12:51.010530-05:00 linuxSQL kdm_config[3303]: Multiple occurrences of section [X-:*-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
2013-12-12T18:12:51.010727-05:00 linuxSQL kdm_config[3303]: Multiple occurrences of section [X-:0-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
2013-12-12T18:12:51.010921-05:00 linuxSQL kdm[1294]: plymouth should quit after server startup
2013-12-12T18:12:51.311941-05:00 linuxSQL kdm_greet[3310]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
2013-12-12T18:12:51.348096-05:00 linuxSQL kdm: localhost:1[3309]: Abnormal termination of greeter for display localhost:1, code 1, signal 0
2013-12-12T18:12:51.353712-05:00 linuxSQL xinetd[606]: EXIT: vnc1 status=0 duration=1(sec)
I had the same issue.
at a terminal window type
dbus-launch vncserver
enter a password
take note of the session/port # (2, 3, 4, etc)
go to /home/your_username/.vnc (it is a hidden folder)
edit the file xstartup (I would save it first)
for KDE contents should be
#!/bin/sh
/usr/bin/startkde
for GNOME contents should be
#!/bin/sh
/usr/bin/gnome &
had to REBOOT after editing xstartup to get GUI’s to come
also have to run **dbus-launch vncserver **again since is not configured for start on boot yet
from vnc client enter address of server followed by session number
like xxx.xxx.xxx.xxx:# (e.g. 192.168.2.8:2)
enter password when prompted
This will get you started.
read the article at the following link to set up other options like KDE or GNOME interfaces and to setup automatic start on boot
Set up Remote Admin on a server, with mostly default settings (no change to the vnc config file) so it’s set for screen 1 on port 5901. On a notebook (openSuse 12.3) I run KRDC, the VNC client. It does exactly nothing, not even an error message. The most I get is Connecting to 192.168… in the status line–even after deleting all the tabs for connection attempts.
From Firefox on the notebook I can go to 192.168.1.2:5801 and I get a login screen. I can log in, the password is accepted. The remote desktop appears and the image of the disk drive starts to fade in–then the screen goes white with a message that the server has reset the connection.
The file “vnc” in /etc/xinitd.d/ configures “service vnc1” for ‘nobody’ on port 5901. I made my user (not ‘nobody’) a member of the nobody group.
Tried to start Xvnc in a terminal window but found that it is allegedly running, but it is not listed in System Monitor (ksysguard) or in Yast under Services Manager.
I’ll watch this space for suggestions.
Thanks.
change the user to **root **for vnc1 in YaST->xinetd
even if temporarily
I had to change the user to get the service to work automatically on boot (otherwise had to start manually as described in prior post)
My novice thoughts are the permissions seem to be broken on the YaST install of tightVNC
And if memory serves me it has something to do with KDE startup for the session
I am using KDE so I don’t know if the same issue occurs in Gnome
Changed vnc file in /etc/xinitd.d directory to make ‘root’ the vnc user on the server. Disabled the server’s firewall. From the VNC client on a notebook, using a vnc connection for root@servername:5901, I get ‘connecting to server IP’ in the status line at the bottom but no action on the screen. In Firefox using servername:5801 displays the server login, where the p/w is accepted for user ‘root’. The remote desktop starts to load, then the server closes the connection.
sorry I can’t give the exact answer but I can suggest some things to try.
the issues you are having are very similar to the ones I was having
using root for the xinetd was only a work around for auto start on boot
i would make sure I could get VNC running manually from a daemon first (step #2 described above)
I had a similar problem with trying to VNC in to a 13.1 Gnome desktop, that was virtualized under a physical 13.1 install. However, I had no problems VNC’ing in to the physical install. I had the same issues with a KDE desktop on another VM. After 4 hours tearing my hair out and combing the web, it occurred to me that I had not patched either VM with all the updates…which, of course, fixed the problem.
I’m happy to put my own dumb-ness out there as a warning to others…VNC seems to work fine using the basic YaST “Enable Remote Administration” mechanism if the system is up to date as of the date and time of this post. 
Steve
agree, always should make sure system is up to date when trying to fix issues
however, my system was up to date (at least with the “software updater” service)
are you saying, go to tightvnc.com and update?
the version that comes with SuSE 13_1 is 1.3.10 which is also the most current version for linux available at tighvnc.com
also pulling updates outside of SuSE’s Software Updater has always seemed tricky to me.
SuSE often does not use the default locations the software provider uses.
You can spend a lot of time trying to figure out how to pull it all together if you are even able to figure it out.