[opensuse] vncviewer on Leap 42.3
I have been using vncviewer for years to access remote openSUSE desktops from my local openSUSE. I now have two machines running Leap 42.3, and I cannot connect. The password is correct. I get a popup that says: read: Connection reset by peer (104) The command on the server (started by xinetd) is: service x11vncservice { socket_type = stream protocol = tcp wait = no user = root server = /usr/bin/x11vnc server_args = -inetd -rfbauth /etc/vncpasswd -o /var/log/x11vnc.log -find -env FD_XDM=1 -shared -forever port = 5900 type = UNLISTED } /etc/vncpasswd has the password as generated with x11vnc, as I have always done. I connect with this: vncviewer -passwd /home/roger/.vncpasswd mercury:0 or even: vncviewer mercury:0 /home/roger/.vncpasswd has the password generated with x11vnc, as I have always done. And it says: TigerVNC Viewer 64-bit v1.6.0 Built on: ??-??-?? ??:?? Copyright (C) 1999-2015 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Mon Aug 28 11:32:22 2017 CConn: connected to host mercury port 5900 Mon Aug 28 11:32:23 2017 CConnection: Server supports RFB protocol version 3.8 CConnection: Using RFB protocol version 3.8 CConnection: Choosing security type VncAuth(2) CConn: read: Connection reset by peer (104) I see only this in the log on the server (the display I want to connect to) Aug 28 11:23:32 mercury xinetd[29561]: START: x11vncservice from=10.2.10.41 Aug 28 11:23:32 mercury xinetd[29561]: EXIT: x11vncservice status=1 duration=0(sec) Aug 28 11:23:37 mercury xinetd[29561]: START: x11vncservice from=10.2.10.41 Aug 28 11:23:37 mercury xinetd[29561]: EXIT: x11vncservice status=1 duration=0(sec) Aug 28 11:28:25 mercury xinetd[29561]: START: x11vncservice from=10.2.10.41 Aug 28 11:28:26 mercury xinetd[29561]: EXIT: x11vncservice status=1 duration=1(sec) Aug 28 11:31:56 mercury xinetd[29561]: START: x11vncservice from=10.2.10.41 Aug 28 11:31:56 mercury xinetd[29561]: EXIT: x11vncservice status=1 duration=0(sec) I am using the same RPM packages as when this worked (except these are now for Leap 42.3): on the server: x11vnc xorg-x11-Xvnc on the client: tightvnc -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
A bit more information. On the server, x11vnc reports: 29/08/2017 09:44:19 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 1899 29/08/2017 09:44:19 29/08/2017 09:44:19 wait_for_client: WAIT:cmd=FINDDISPLAY 29/08/2017 09:44:19 29/08/2017 09:44:19 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/2560 29/08/2017 09:44:19 29/08/2017 09:44:19 initialize_screen: -inetd mode: F_GETFL(stdin): 0x2 29/08/2017 09:44:19 initialize_screen: -inetd mode: F_GETFL(stdout): 0x2 29/08/2017 09:44:19 initialize_screen: -inetd mode and stdio is O_RDWR 29/08/2017 09:44:19 other clients: 29/08/2017 09:44:19 incr accepted_client=1 for 10.2.10.41:37746 sock=3 29/08/2017 09:44:19 Client Protocol Version 3.8 29/08/2017 09:44:19 Protocol version sent 3.8, using 3.8 29/08/2017 09:44:19 wait_for_client: got client 29/08/2017 09:44:19 client progressed=1 in 0/0 0.000001 s 29/08/2017 09:44:19 client useCopyRect: 10.2.10.41 0 29/08/2017 09:44:19 client_set_net: 10.2.10.41 0.0050 29/08/2017 09:44:19 wait_for_client: running: env X11VNC_SKIP_DISPLAY='' /bin/sh /tmp/x11vnc-find_display.82GiGi 29/08/2017 09:44:19 wait_for_client: find display cmd failed. 29/08/2017 09:44:19 wait_for_client: bad reply ' ' I have googled a bit, but nothing seems to point anywhere useful. If I start the x11vnc server manually, the same happens. # x11vnc -rfbauth /etc/vncpasswd -oa /var/log/x11vnc.log -find -rfbport 5900 PORT=5900 The server says nothing more than the above. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Aug 29, 2017 at 10:04 AM, Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:
A bit more information. On the server, x11vnc reports:
29/08/2017 09:44:19 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 1899 29/08/2017 09:44:19 29/08/2017 09:44:19 wait_for_client: WAIT:cmd=FINDDISPLAY 29/08/2017 09:44:19 29/08/2017 09:44:19 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/2560 29/08/2017 09:44:19 29/08/2017 09:44:19 initialize_screen: -inetd mode: F_GETFL(stdin): 0x2 29/08/2017 09:44:19 initialize_screen: -inetd mode: F_GETFL(stdout): 0x2 29/08/2017 09:44:19 initialize_screen: -inetd mode and stdio is O_RDWR 29/08/2017 09:44:19 other clients: 29/08/2017 09:44:19 incr accepted_client=1 for 10.2.10.41:37746 sock=3 29/08/2017 09:44:19 Client Protocol Version 3.8 29/08/2017 09:44:19 Protocol version sent 3.8, using 3.8 29/08/2017 09:44:19 wait_for_client: got client 29/08/2017 09:44:19 client progressed=1 in 0/0 0.000001 s 29/08/2017 09:44:19 client useCopyRect: 10.2.10.41 0 29/08/2017 09:44:19 client_set_net: 10.2.10.41 0.0050 29/08/2017 09:44:19 wait_for_client: running: env X11VNC_SKIP_DISPLAY='' /bin/sh /tmp/x11vnc-find_display.82GiGi 29/08/2017 09:44:19 wait_for_client: find display cmd failed. 29/08/2017 09:44:19 wait_for_client: bad reply ' '
I have googled a bit, but nothing seems to point anywhere useful. If I start the x11vnc server manually, the same happens.
# x11vnc -rfbauth /etc/vncpasswd -oa /var/log/x11vnc.log -find -rfbport 5900 PORT=5900
The server says nothing more than the above.
It seems that TightVNC does not work with sddm. So I will have to change it. I think it needs XDMCP, which sddm does not provide. There is a suggestion to use lightdm. But I see that kdm also supports XDMCP. Is anyone using lightdm or kdm with Leap 42.3/KDE? Any issues with either of them in this context? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/12/2017 03:27 AM, Roger Oberholtzer wrote:
It seems that TightVNC does not work with sddm. So I will have to change it. I think it needs XDMCP, which sddm does not provide.
There is a suggestion to use lightdm. But I see that kdm also supports XDMCP.
Is anyone using lightdm or kdm with Leap 42.3/KDE? Any issues with either of them in this context?
In the forums, awhile back, there were several recommendations to install kdm and switch to it because of this. I have not tried the KDE/KDM combo, because I quit KDE when KDE4 ended, for now. I use Xfce with LightDM, much happier that way. ... but, why not just try them? It is easy enough to switch, try them, and if not to your liking, just switch back to SDDM. With something that simple (switching there and back with Display Managers), I tend to just do it long before asking "has anyone else...?". ;-) -- -Gerry Makaro aka Fraser_Bell on the forums, IRC, and mail at openSUSE.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Sep 13, 2017 at 11:50 PM, Fraser_Bell <Fraser_Bell@opensuse.org> wrote:
On 09/12/2017 03:27 AM, Roger Oberholtzer wrote:
It seems that TightVNC does not work with sddm. So I will have to change it. I think it needs XDMCP, which sddm does not provide.
There is a suggestion to use lightdm. But I see that kdm also supports XDMCP.
Is anyone using lightdm or kdm with Leap 42.3/KDE? Any issues with either of them in this context?
In the forums, awhile back, there were several recommendations to install kdm and switch to it because of this.
I have not tried the KDE/KDM combo, because I quit KDE when KDE4 ended, for now. I use Xfce with LightDM, much happier that way.
... but, why not just try them? It is easy enough to switch, try them, and if not to your liking, just switch back to SDDM.
With something that simple (switching there and back with Display Managers), I tend to just do it long before asking "has anyone else...?".
Same here. I was more wondering if there were less obvious issues than that it just seemed to work. I'm not sure what those might be. But it seems to me that a display manager might be able to cause subtle problems. My plan is to make a KIWI-based OEM Leap 42.3 installer that enables lightdm or kdm by default. Work is in progress. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/12/2017 03:27 AM, Roger Oberholtzer wrote:
Is anyone using lightdm or kdm with Leap 42.3/KDE? Any issues with either of them in this context?
sddm does indeed have issues with various "seats" not being able to access some things even with the proper permissions. (such as a virtual machine started at boot time via a systemd service not being controllable by the very same user that systemd starte it with. ** Switching to lightdm did solve this problem for me but I didn't try kdm. It was as easy as installing lightdm and one or more if its configuration utilities and greeters (lightdm, lightdm-kde-greeter, lightdm-gtk-greeter, lightdm-gtk-settings lightdm-qt5, etc). Then run as root systemctl stop sddm systemctl disable sddm systemctl enable lightdm systemctl start lightdm then maybe reboot and rattle chicken bones in a paper sack etc. This was not on leap 42.3 so recommendations are approximate. **I reported that problem and it was subsequent fixed but I saw no reason to switch back to sddn. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Fraser_Bell -
John Andersen -
Roger Oberholtzer