vncserver or: how to make a useful tool useless
Hi, I have a script that starts a vncserver session on a remote machine, sets up a ssh port redirect and connects to that with vncviewer. It no longer works :( (on Tumbleweed) The reason I found is speedy:~% rpm -q --changelog xorg-x11-Xvnc * Thu Feb 17 2022 Stefan Dirsch <sndirsch@suse.com> - n_vncserver.patch * fix location of Xsession script - vncserver usage has radically changed; please check this: https://github.com/TigerVNC/tigervnc/blob/master/unix/vncserver/HOWTO.md In short, instead of creating sessions on the fly, everything has to be pre-defined, restricted to *one* session per user, and launched via systemctl. Of course only as root..... Sorry, but I find this "improvement" a complete desaster in userfriendliness :(((
Peter Suetterlin wrote:
Hi,
I have a script that starts a vncserver session on a remote machine, sets up a ssh port redirect and connects to that with vncviewer.
It no longer works :( (on Tumbleweed)
The reason I found is
speedy:~% rpm -q --changelog xorg-x11-Xvnc * Thu Feb 17 2022 Stefan Dirsch <sndirsch@suse.com> - n_vncserver.patch * fix location of Xsession script - vncserver usage has radically changed; please check this:
https://github.com/TigerVNC/tigervnc/blob/master/unix/vncserver/HOWTO.md
In short, instead of creating sessions on the fly, everything has to be pre-defined, restricted to *one* session per user, and launched via systemctl. Of course only as root.....
Sorry, but I find this "improvement" a complete desaster in userfriendliness :(((
Yeah, it doesn't sound like much progress. Still, you can run more than one instance of vncserver (provided the service unit is defined to support it) - in your script, it sounds like you still have to be root, for the port redirect? -- Per Jessen, Zürich (17.4°C)
On 08.05.2022 19:19, Per Jessen wrote:
Yeah, it doesn't sound like much progress. Still, you can run more than one instance of vncserver (provided the service unit is defined to support it) - in your script, it sounds like you still have to be root, for the port redirect?
You can still run Xvnc and vncserver manually, you just lose some convenience offered by old script. Or you can simply get old script from previous release and use it. It is not that functionality is not there, it is just that upstream does not want to endorse using it the way they cannot fully support.
Andrei Borzenkov wrote:
On 08.05.2022 19:19, Per Jessen wrote:
Yeah, it doesn't sound like much progress. Still, you can run more than one instance of vncserver (provided the service unit is defined to support it) - in your script, it sounds like you still have to be root, for the port redirect?
You can still run Xvnc and vncserver manually, you just lose some convenience offered by old script. Or you can simply get old script from previous release and use it. It is not that functionality is not there, it is just that upstream does not want to endorse using it the way they cannot fully support.
Ah, thanks for the hint. I was considering doing that, but was afraid other changes might prevent me. I'll definitely have a try :D
Peter Suetterlin wrote:
Andrei Borzenkov wrote:
You can still run Xvnc and vncserver manually, you just lose some convenience offered by old script. Or you can simply get old script from previous release and use it. It is not that functionality is not there, it is just that upstream does not want to endorse using it the way they cannot fully support.
Ah, thanks for the hint. I was considering doing that, but was afraid other changes might prevent me. I'll definitely have a try :D
So I got the one from Leap 15.4, which has version 1.10. First try failed, complaining Unrecognized option: -rfbwait Quick&dirty try was to just remove that option from the program (perl code) I still do get an error/warning: xauth: (stdin):1: bad display name "Pi4:1" in "add" command But Xvnc is correctly started, and indeed it seems to work again as before! Yippieh.
Per Jessen wrote:
Peter Suetterlin wrote:
https://github.com/TigerVNC/tigervnc/blob/master/unix/vncserver/HOWTO.md
In short, instead of creating sessions on the fly, everything has to be pre-defined, restricted to *one* session per user, and launched via systemctl. Of course only as root.....
Sorry, but I find this "improvement" a complete desaster in userfriendliness :(((
Yeah, it doesn't sound like much progress. Still, you can run more than one instance of vncserver (provided the service unit is defined to support it)
I intended to use it to open a second session with a different WM on the same machine - this worked before, but with the new system no longer. It automatically connects to the running session instead :(
- in your script, it sounds like you still have to be root, for the port redirect?
No, for not priviledged ports (5901 isn't) this is possible as user :)
participants (3)
-
Andrei Borzenkov -
Per Jessen -
Peter Suetterlin