#1 2016-05-24 20:11:26

capncrunch

Member

Registered: 2016-04-27

Posts: 11

VNC Vino remote window freezes / turns black

I'm experiencing a problem with Vino server on a new Bunsen installation. After installing Bunsen, I installed Vino using the "Network \ Install Remote Desktop" script in the openbox menu. Vino appears to have installed correctly, and I'm able to connect from a Linux Mint client using tightvnc viewer. If I leave the VNC window connected, after a short period of time (which I *think* corresponds to the screensaver activating on the remote Bunsenlabs host) the VNC window is suddenly completely frozen. I cannot open any menus, I cannot move any Windows, etc. If I close that VNC window, and try to open a new one, the window opens completely black. Moving the mouse over it does nothing.

Some supplemental information:

1. Don't know if this would have any impact, but the filesystem is set up with '/' and 'swap' as primary partitions, and '/home' inside an LVM partition.

2. I have Bunsen set up to autologin my user. In lightdm.conf:

autologin-user=USERNAME

3. I added "/usr/lib/vino/vino-server &" to ~/.config/openbox/autostart and rebooted the Bunsen host

4. From my Linux Mint client I use the same connection string I use for connecting to Vino on my crunchbang host:

$ vncviewer -compresslevel 3 -x11cursor -via USERNAME@remotehost localhost:0

5. This is what I get in the terminal window when I make the connection to vino on Bunsen:

$ Connected to RFB server, using protocol version 3.7
No authentication needed
Desktop name "USERNAME@remotehost"
VNC server default format:
  32 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Warning: Cannot convert string "-*-helvetica-bold-r-*-*-16-*-*-*-*-*-*-*" to type FontStruct
Using default colormap which is TrueColor.  Pixel format:
  32 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Tunneling active: preferring tight encoding

After about 10 minutes of inactivity, everything inside the VNC window freezes. The Bunsen host itself is not frozen. I'm able to SSH into it from a new terminal window. It's only the VNC window which freezes at first, and then turns black.

Can someone please help me out?

Last edited by capncrunch (2016-05-24 20:14:42)

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,093

Website

Re: VNC Vino remote window freezes / turns black

I *think* corresponds to the screensaver activating on the remote Bunsenlabs host

I think so too

Try this fix:
https://forums.bunsenlabs.org/viewtopic … 969#p23969

---

Para todos todo, para nosotros nada

capncrunch

Member

Registered: 2016-04-27

Posts: 11

Re: VNC Vino remote window freezes / turns black

That seems to have worked, thanks!

Is there a way to have both a functioning Vino server and a functioning screen lock at the same time? Does this same problem arise with other vnc servers, like tightvnc, for example?

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,093

Website

Re: VNC Vino remote window freezes / turns black

Is there a way to have both a functioning Vino server and a functioning screen lock at the same time?

You could remove the Hidden=true line from ~/.config/autostart/light-locker.desktop and change the Exec line to:

Exec=light-locker --lock-after-screensaver=0

https://forums.bunsenlabs.org/viewtopic … 466#p26466

This will stop light-locker (the screenlocker in BL) from activating after the screensaver cuts it but will leave the functionality otherwise intact.

Does this same problem arise with other vnc servers, like tightvnc, for example?

I have no experience of VNC so I can't really say for sure but I think this issue is due to the screenlocker itself rather than the VNC program.

---

Para todos todo, para nosotros nada