TigerVNC 1.14.0 release.
Changelog: - Xvnc now supports hardware accelerated OpenGL and Vulkan on drivers that supports GBM¹ - The viewers and servers now follow the XDG Base Directory Specification, like "~/.config", for storing files in the home directory. - Existing users will continue using the legacy "~/.vnc" directory, but new users will get the XDG directories. - The native viewer has received a mild refresh of the UI appearance - Reverse connections can now be forced to be view-only - The special "%u" marker can be specified for "PlainUsers" to dynamically indicate the user running the server - vncserver can be run without forking for better compatibility with more system service managers - x0vncserver now supports systemd socket activation
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2024-849f60edfaPlease login to add feedback.
This update has been submitted for testing by jgrulich.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
no regressions noted
This update has made Xrdp connections unusable for me, even on a LAN. Even typing into a terminal in Xfce is now slow, I'm 3 characters ahead of what I can see. Downgrading to 1.13.1-14 fixed it for me.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
@nixuser: Sadly, I didn't see any related issue reported upstream about your problem. Can you please get in touch with upstream and report your issue there?
jgrulich edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by jgrulich.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
I've updated to tigervnc-1.14.0-2.fc40 and I cannot now reproduce the problem. I'm guessing nothing happened between -1 and -2 that should impact performance right?
I did reboot after the install this time and I may not have the first time, but I wouldn't have though that should be necessary. In any event I can't fault it now, sorry for the noise.
@nixuser right, there is no change between -1 and -2 that would fix your issue.
Works fine for me
This update can be pushed to stable now if the maintainer wishes
Works
This update has been submitted for stable by jgrulich.
This update has been pushed to stable.
I've come to the conclusion this version does introduce a performance regression.
The common trigger seems to be legacy NVIDIA cards (in both my cases Kepler generation) and default nouveau divers.
I am NOT seeing problems on systems with Intel graphics of various generations.
Upstream bug:
https://github.com/TigerVNC/tigervnc/issues/1810