mirror of
https://github.com/outbackdingo/hyprcosmic-session.git
synced 2026-08-25 07:20:17 +00:00
gitops
f8fec1360b
The toolkit variables are the generic Wayland session contract, not anything COSMIC-specific: Firefox on Wayland instead of XWayland, Qt preferring the Wayland platform plugin with an xcb fallback, and Java AWT told not to expect a reparenting window manager, without which Swing windows come up blank or mispositioned. Leaving them out is why Qt and Java applications behaved differently under HyprCosmic than under the stock session on the same machine. They are set with `:-` like the XDG lines above rather than assigned outright, so a value already chosen in the environment survives. The Qt platform theme stays pointed at CuteCosmic rather than being switched to qt5ct the way HyDE would have it. This fork themes GTK, waybar and rofi and has no Qt pipeline at all, so handing Qt applications to qt5ct would hand them to a configuration nothing here writes; CuteCosmic at least follows the COSMIC palette that cosmic.conf does drive. Worth revisiting if Qt theming ever gets built. DCONF_PROFILE is guarded, which start-cosmic's is not. Naming a profile dconf cannot find is not a soft failure: it logs "using null configuration" and from then on every GSettings read returns schema defaults while writes go nowhere, so a desktop's worth of settings simply appears blank. Measured on this machine -- `DCONF_PROFILE=cosmic` dumps 33 keys, a name that does not resolve dumps zero. So the profile is looked for first and the variable is only exported once found. The bare name is used rather than an absolute path. start-cosmic gets its prefix rewritten in at install time by the Justfile, which pins one prefix; dconf searches /etc/dconf/profile first and XDG_DATA_DIRS after, so the bare name finds the packaged profile under /usr/share while still letting an administrator override it from /etc. DCONF_PROFILE joins SSH_AUTH_SOCK in the systemd and D-Bus activation environments, matching what start-cosmic imports.