On Wed, Feb 25, 2026 at 01:22:31PM +0100, David Ayers wrote: Hello David,
> On "testing" the package is already installed during Gnome Desktop > installation: Ok, that's good. > (Installing that package on trixie though, does have the effect of new > maps having a dark canvas. It doesn't make the window, menu or widget > use the Dark Theme and existing maps still have the white background, > but that may be something I can tweak... let's focus in testing.) Well the version in trixie is the last stable release which is still using Qt5. The 2.9.500+ versions in testing/sid are what soon will be vym 3 and use Qt6. I would prefer to focus on those, because we can't change the version in trixie anyway. I could get hold of an Ubuntu 25.10 desktop installation this morning, which as far as I know uses a customized Gnome installation, and there vym picks up the system dark theme. Window decoration is an instant change, application menu and canvas requires a restart. That was tested with vym 2.9.604 using the default theme setting "System settings for dark theme". Now the question is what might be the relevant magic Ubuntu applied. >From the perspective of the installed qt6 packages I see that qt6-gtk-platformtheme is installed and qt6-qpa-plugins, but I'm not sure if the later is relevant. I do not see any QPlatform reference (https://doc.qt.io/qt-6/qpa.html) in the vym code. > Setting "export QT_QPA_PLATFORMTHEME=gtk3" before starting via command > line does not have an effect on honoring the "System setting for dark > theme". That variable is also unset on the Ubuntu system I tried. > It may very well be an upstream logic bug here: > src/main.cpp > L424 > // Use dark theme depending on system appearance and preferences > > > int text_hsv_value = app.palette().color(QPalette::WindowText).value(); > int bg_hsv_value = app.palette().color(QPalette::Base).value(); > systemSeemsDark = (text_hsv_value > bg_hsv_value); > QString settingsDarkTheme = settings.value("/system/darkTheme", > "system").toString(); > usingDarkTheme = false; > iconTheme = "bright"; > if (settingsDarkTheme != "never") { > if (settingsDarkTheme == "always" || (settingsDarkTheme == "system" > && systemSeemsDark)) { > usingDarkTheme = true; > iconTheme = "dark"; > } > } > > I haven't wrapped my head around it yet but once I find time to figure > out how to actually build and install the package, I hope to be able to > provide a patch that could be submitted upstream. That should be fine, allowing you to override the system setting or if the system settings suggest it's dark, it's switching to the dark theme. > PS: I did find: > https://www.debian.org/doc/manuals/maint-guide/build.en.html > which is actually target for maintainers but now I also found this: > https://wiki.debian.org/BuildingTutorial > so please give me the weekend, to see if I can figure this out... Rebuilding should be rather easy if you do it in place on a system with a deb-src configured to fetch source packages: apt source vym # grab the source package apt install build-essential fakeroot # get the general build tools in place apt build-dep vym # install the build dependencies cd vym-2.9.604 dpkg-buildpackage -us -uc -rfakeroot # build the package Though I believe that shouldn't be necessary. At least the current Qt6 based version should be working fine. Sven
