Any guide on how to use V. 1.11?

[Dave it.]

Hi.

I've been using TigerVNC on Arch for years. Always been solid and reliable.

After the latest upgrade to 1.11 I can't get TigerVNC to work at all.

Problems:
vncserver returns an error "Couldn't find suitable Xsession". I looked into the perl script, apparently it's because I don't have either Xsession entries in /etc/X11. I don't use XDM or anything requiring an Xsession script, and I've never needed the script there, do I really need it now or is vncserver just plain no longer supported?

vncsession seems to have replaced vncserver but doesn't work either, sudo vncsession <user> <:display> gets the message "Failure daemonizing". Again no further explanation, no documentation, nothing I can see.

So I stitched together an Xvnc command and I managed to get a client showing a nice shiny black screen, but again no documentation as to how I actually get anything useful to show up on it.

After the best part of a day I've given up. I must be missing something, where's the documentation? Any ideas or recommendations on how to proceed?

[Dave it.]

So in a last-ditch attempt I ln -s-ed the xstartup script in my ~/.vnc directory to /etc/X11/Xsession and everything seems to work now.

Solved, kinda.

[Pierre Ossman]

On 10/09/2020 15:04, Dave it. wrote:
> Hi.
>
> I've been using TigerVNC on Arch for years. Always been solid and reliable.
>
> After the latest upgrade to 1.11 I can't get TigerVNC to work at all.
>
> Problems:
> vncserver returns an error "Couldn't find suitable Xsession". I looked into
> the perl script, apparently it's because I don't have either Xsession
> entries in /etc/X11. I don't use XDM or anything requiring an Xsession
> script, and I've never needed the script there, do I really need it now or
> is vncserver just plain no longer supported?
>

That is correct. vncserver simply did not work for modern desktops so we
cannot support that model.

> vncsession seems to have replaced vncserver but doesn't work either, sudo
> vncsession <user> <:display> gets the message "Failure daemonizing". Again
> no further explanation, no documentation, nothing I can see.
>

vncsession is not meant to be run directly (unless you _really_ know
what you are doing). The proper way to start things is via
vncserver@.service. Please have a look in the service files on how to
get started.

Regards
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[Dave it.]

On Friday, 11 September 2020 at 11:07:55 UTC+2 Pierre Ossman wrote:

vncsession is not meant to be run directly (unless you _really_ know
what you are doing). The proper way to start things is via
vncserver@.service. Please have a look in the service files on how to
get started.

Followed all the instructions in the vncserver@.service file, mapped users, still get the "Failure daemonizing" error whether I start the vncserver using vncsession, vncsession-start or via the systemd service.

vncserver is still there and working, albeit with the ugly hack.

[DRC]

On 9/11/20 4:07 AM, Pierre Ossman wrote:
> That is correct. vncserver simply did not work for modern desktops so
> we cannot support that model.

What was the show-stopper?  The only GNOME 3 issue I wasn't ever able to
resolve with vncserver was this one:

https://github.com/TurboVNC/turbovnc/issues/51

The requirement to use sudo is a non-starter for portal environments
(and most of our large-scale deployments prefer MATE anyhow), so I'm
trying to understand how (or even why) to adopt this new approach.

[Oleksandr Natalenko]

https://bbs.archlinux.org/viewtopic.php?pid=1925707#p1925707

[Dave it.]

So the problem was in /etc/pam.d/tigervnc, the selinux entries had to go (the clue was in  Paul's post). Everything is working perfectly now, and as intended. No more fugly hacks. I didn't find it out, the Arch packager fixed it.

Thanks to all that have contributed.

Best, Dave