Folks:
I've had my share of difficulties running Xvnc on Rivendell systems
lately. The VNC service will crash; or it will stop responding to mouse
clicks or keystrokes; and in some cases even the keyboard and mouse
attached to the physical machine will become unusable.
Some machines never experience problems; others experience them
frequently. In some cases, killing and restarting Xvnc will resolve the
problems, but in others, I have to reboot the machine.
The problem has been encountered on machines running CentOS 7, with
Rivendell installed via the Paravel install script. I've encountered the
problem with both Rivendell V2 and Rivendell V3. I don't remember seeing
the problem on my older Debian-based Rivendell machies.
I recently changed two machines where the problem was particularly
troublesome over to tigervnc running on a virtual desktop, and have not
had any problem reported since doing so. My suspicion is that the problem
is between the OS and the hardware, rather than anything in Rivendell.
Recently, I installed Rivendell v3.6.5 on three machines under Rocky Linux
8, compiling and installing QT from source and doing the same for
Rivendell. I had not intended these to be test beds for Xvnc, in part
because they are almost never logged in to; they receive logs and audio
files by other means and export them to Rivendell systems at other
stations. However, I'm going to experiment with them to see if I can
replicate the problem.
Has anyone else but me encountered this sort of problem?
Rob
--
umar@python:~$ more stinking bills
more: stat of stinking failed: No such file or directory
more: stat of bills failed: No such file or directory
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
