https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #34 from Robin Bankhead <kde.b...@headbank.co.uk> --- (In reply to Pierre Ossman from comment #32) > 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. > Thanks for looking in, Pierre. Apologies if I misinterpreted the position: I was drawing on your comments on your tracker [1] and the deprecation of the `vncserver` Perl script that seemed to indicate that the systemd (system) service would be the only mode of operation you'd be supporting. I follow your reasoning above but from my POV a systemd service environment is very different from an OpenRC one, and in any case as you'll see above it's only quite recently that we obtained the debugging that gave me something substantive to bring to your door. > 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? Current Gentoo packaging of tigervnc-1.14.1 is built against xserver-21.1.14. We have a live ebuild (built from git) but that also currently builds against 21.1.14. As for KDE I am currently at 6.2.4 but 6.2.5 is available, I may get time at the weekend to update (takes a while on Gentoo, y'know...) Given that I've been aware of this bug since mid-2022 (and it may have existed in some form back as far as 2012) my hopes are not super high of a happy accident resolving it this time around, but we'll see. [1] https://github.com/TigerVNC/tigervnc/issues/1096 -- You are receiving this mail because: You are watching all bug changes.
