https://bugs.kde.org/show_bug.cgi?id=489840
Pierre Ossman <oss...@cendio.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |oss...@cendio.se
--- Comment #32 from Pierre Ossman <oss...@cendio.se> ---
TigerVNC developer here, trying to have a look at this.
(In reply to Robin Bankhead from comment #26)
> If that's the case then we may have run out of road here, because tigervnc
> only support systemd nowadays.
I'd like to start with clearing up this misunderstanding. We don't have a
strict requirement on systemd, but I can understand the confusion.
We only support the components that are included with TigerVNC. One such
component is the "vncserver" service, which is used to start sessions. Starting
desktop environments is hard, and easy to get wrong. We don't have the
resources to help out with other software that starts desktops. E.g. old school
"vncserver" commands that the user runs when already in an existing session.
Other components of TigerVNC has nothing to do with this and are supported on
their own merits. E.g. the "Xvnc" component, which seems to be the relevant one
here. At that point, it's up to you how you launch your desktop and
applications. Just as long as you don't expect us to support those as well.
We'll gladly help out with issues with Xvnc, but not the complexities beyond
that.
For the issue at hand, it seems to be an X11 interaction issue. So it falls
under what Xvnc is supposed to do.
That said, the X11 code is 99% just standard Xorg. So usually, the issues need
to be resolved there.
I tried to reproduce the problem here, but was unable to. I am running Plasma
6.2.5, and an Xvnc based on Xorg server 21.1.8.
Could this issue already be resolved with sufficiently new versions of things?
Could someone test with those newer versions?
--
You are receiving this mail because:
You are watching all bug changes.
