You are not logged in.
use case: I want to connect to my bl-linux system from a Windows laptop using VNC. It works fine with vino-server or x11vnc, but after locking the host system with bl-lock, I am no longer able to interact with the host system over vnc. (FWIW I'm using tightvnc on Windows)
I solved this by using xscreensaver, starting xscreensaver on autostart, and starting x11vnc on autostart. See scripts below.
~/.config/autostart/x11vnc.desktop
[Desktop Entry]
Encoding=UTF-8
Type=Application
Name=X11VNC
Comment=
Exec=/usr/bin/x11vnc-start
StartupNotify=false
Terminal=false
Hidden=false
~/.config/autostart/xscreensaver.desktop
[Desktop Entry]
Encoding=UTF-8
Type=Application
Name=XSSVR
Comment=
Exec=/usr/bin/xscreensaver-start
StartupNotify=false
Terminal=false
Hidden=false
/usr/bin/xscreensaver-start
#!/bin/bash
xscreensaver -no-splash &
/usr/bin/x11vnc-start
#!/bin/bash
x11vnc -forever -display :0 -rfbauth /home/USER/.x11vnc/passwd
Perform the following to set a password for x11vnc:
$ mkdir ~/.x11vnc
$ x11vnc -storepasswd password ~/.x11vnc/passwd
Note that I did not find the need to add call("bl-lock") to bl-exit (see https://forums.bunsenlabs.org/viewtopic … 093#p16093 )
vino should work fine too if you'd prefer it over x11vnc. If that's the case, then you'd probably want to create an autostart entry for vino instead of x11vnc.
references:
https://forums.bunsenlabs.org/viewtopic.php?id=1252
https://wiki.archlinux.org/index.php/x1 … a_password
Last edited by moduspwnens (2016-06-15 17:49:42)
Offline
use case: I want to connect to my bl-linux system from a Windows laptop using VNC. It works fine with vino-server or x11vnc, but after locking the host system with bl-lock, I am no longer able to interact with the host system over vnc. (FWIW I'm using tightvnc on Windows)
bl-lock does the job it is supposed to do.
If you want your system to be open for VNC connections at all times, then you should prevent bl-lock from doing what it is supposed to do. No need to install xscreensaver for this.
Offline
moduspwnens wrote:use case: I want to connect to my bl-linux system from a Windows laptop using VNC. It works fine with vino-server or x11vnc, but after locking the host system with bl-lock, I am no longer able to interact with the host system over vnc. (FWIW I'm using tightvnc on Windows)
bl-lock does the job it is supposed to do.
If you want your system to be open for VNC connections at all times, then you should prevent bl-lock from doing what it is supposed to do. No need to install xscreensaver for this.
good to know, thanks
Offline