Re: Can't get beyond a grey screen when I connect

Further to below, I'm currently running a remote session using the 
method below and I've noticed one oddity. It's not a deal breaker but I 
can only connect once then I have to kill the vncserver process and 
start a fresh instance to make the connection work again.

Essentially, I use ssh port forwarding to connect to my remote server 
with ports forwarded from the remote workstation. Then I connect to the 
remote workstation using ssh to kill the current server and start a new 
instance. Only then can I use a vnc viewer to connect to the remote 
workstation.


On 2022-09-11 20:03, Gary Dale wrote:
> Michael Setzer reminded me that he posted a working xstartup from his 
> system in a reply to an earlier message:
>
> #!/bin/sh
> # Uncomment the following two lines for normal desktop:
> unset SESSION_MANAGER
> unset DBUS_SESSION_BUS_ADDRESS
> exec  /bin/sh /etc/xdg/xfce4/xinitrc # X11/xinit/xinitrc
> [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
> [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
> xsetroot -solid grey
> xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
> startxfce4 &
>
> This seems to work. I've finally got a working remote session.
>
> Thanks Michael.
>
>
> On 2022-09-11 18:25, Gary Dale wrote:
>> I've been trying this all day with very limited success. The closest 
>> I've gotten is at one point I actually got an arrow cursor in the 
>> viewer window, but mostly I get an X cursor.
>>
>> I'm running a Debian/Bookworm AMD64 workstation with a Plasma 5 
>> desktop. However, I've also got Gnome and XFCE available. I've been 
>> trying various ~/.vnc/xstartup configurations but nothing seems to work.
>>
>> I want to connect through an ssh tunnel using port forwarding. I do 
>> this a lot to connect to Windows workstations through a similar setup 
>> - the router forwards the ssh port to the Linux server, where port 
>> forwarding takes me to the actual machine I want to use.
>>
>> I started with an old one that wanted to run startkde, something that 
>> no longer exists. I got the furthest when I replaced that line with 
>> startplasma, I recall. However I couldn't do anything despite the 
>> nicer cursor.
>>
>> That xstartup would have looked like this:
>>
>> #!/bin/sh
>> unset SESSION_MANAGER
>> unset DBUS_SESSION_BUS_ADDRESS
>>  /usr/bin/startplasma-x11 &
>>
>> [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
>> [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
>> xsetroot -solid grey
>> vncconfig -iconic &
>>
>>
>> I've similarly tried a number of xstartups that people have suggested 
>> to invoke Gnome or XFCE but they haven't even got me an arrow cursor 
>> - just the X.
>>
>> I tried ripping out the tightvnc server and running krfb on the 
>> workstation and using various clients (including krdc) on my laptop 
>> using both the ssh tunnel and simply connecting to the workstation 
>> directly over the LAN. I couldn't even get prompted for the VNC 
>> password.
>>
>> So now I'm back with the tightvnc server running. I can get to the 
>> machine and enter the VNC password, but I can't get a usable desktop.
>>
>> Any ideas?
>>
>>
>>
>> ___________________________________________________________
>> TightVNC mailing list, [email protected]
>> To change your subscription or to UNSUBSCRIBE, please visit
>> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
>
>
> ___________________________________________________________
> TightVNC mailing list,[email protected]
> To change your subscription or to UNSUBSCRIBE, please visit
> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

___________________________________________________________
TightVNC mailing list, [email protected]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list