* feat(Themes): add support for GTK3 dynamic theming
Instead of overriding named colors of all GTK3 themes via the config
directory file, only override named colors for each variant of the
adw-gtk3 theme (light and dark), and let GTK3 apps change themes
depending on the value of org.gnome.desktop.interface color-scheme.
* fix(Themes): apply requested changes
- remove gtk3 override if it's a symlink
- remove call to gtk.sh with old arg 'assets-only'
- append key to dconf path to respect dconf write signature
* refactor(Themes): separate 'include'/'apply' logic for GTK3 dynamic theming
* revert(Themes): reset timer between color-scheme refresh
- rename DMS_ENABLE_GTK4_REFRESH to DMS_ENABLE_GTK_REFRESH
- revert a3fba8
* feat(Themes): add 'remove' mode to gtk.sh
Allow to remove all inclusions and overrides for GTK.
* fix(Themes): backup adw-gtk3 original css in 'apply' (not 'include')
* style(Themes): rename argument 'include' to 'patch' for clarity
* feat(settings): add option to suppress config reload toast (#2730)
Add a toggle in Settings → Compositor Layout to disable the 'config reloaded' toast for Niri and MangoWC compositors. Session setting showConfigReloadToast defaults to true.
* chore: update settings search index for config reload toast
* refactor(settings): rename 'Compositor Notifications' to 'Compositor Toasts'
* fix(settings): reuse existing I18n.tr('Notifications') translation
* Add option to ignore app-requested notification timeout
Notifications may include an expireTimeout hint that currently takes
precedence over the configured Low/Normal/Critical durations, so
popups can disappear earlier (or later) than expected with no
interaction involved. Add notificationIgnoreAppTimeout (default off,
matching the notification spec) to let users force their own
durations regardless of what the app requests.
* Update settings search index for new timeout override toggle
lock-before-suspend released the logind sleep delay inhibitor as soon as Qt
reported the lock rendered (afterAnimating/afterRendering). That signal fires
before the compositor has committed/presented the ext-session-lock surface, so
the machine could freeze ~1 frame later with the desktop still the last
presented frame. On resume the desktop was briefly visible before the lock
appeared (both suspend and hibernate).
Gate lockerReady on WlSessionLock.secure (the ext-session-lock `locked` event),
so the inhibitor is held until the compositor confirms the session is locked and
the desktop is hidden. LockSurface passes the WlSessionLock down as sessionLock;
the readiness check returns early until secure, and re-fires on secureChanged.
The Go-side fallback timer in loginctl monitor remains as the backstop.
Reproduced on niri / s2idle with 3 outputs: debug log showed lockerReady sent
18 ms before `PM: suspend entry`; with this change the desktop no longer flashes
on resume.
Signed-off-by: Thomas Kroll <99196436+tkroll-ionos@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
* Add hotspot contract layer with capability-gated dispatch.
Establish the interface and manager plumbing for hotspot support so backends can opt in without expanding the core Backend contract.
Only backends that implement HotspotBackend get hotspot state propagated; others are forced to unsupported regardless of what they self-report.
* Add IPC handlers and API docs for hotspot actions.
Wire up configure/ start/ stop hotspot through the request router so the QML service layer can drive hotspot operations.
Bump API version to 27 and document the capability-gating contract clients should follow.
* Implement NetworkManager hotspot backend.
Implement HotspotBackend on NetworkManagerBackend with DMS-owned profile management, AP capability detection, and band validation.
Device resolution is deferred to StartHotspot when no device is specified, so profiles survive hardware changes.
* Isolate client Wi-Fi state from AP-mode connections.
Filter AP-mode profiles and access points out of all client Wi-Fi paths so the DMS hotspot (and user-created APs) never appear as saved networks, visible networks, or connected state.
This protects existing client behavior before hotspot controls are exposed in the UI.
* Prefer idle radios for automatic hotspot device selection.
* Add hotspot properties and methods to QML service layer.
Expose hotspot state and actions through DMSNetworkService, NetworkService, and LegacyNetworkService.
Capability is gated on API version and backend-reported support, not backend name checks, and stays stable when Wi-Fi radio is disabled.
* Add hotspot controls to Settings and Control Center.
Settings shows a hotspot setup card as a sibling in the Wi-Fi tab with SSID, password, device, band, save, and start/ stop controls.
Control Center shows a compact row that toggles a configured hotspot or routes to Settings for initial setup.
Both stay visible when Wi-Fi is disabled, explaining the requirement instead of hiding.
* Add translator context to hotspot strings.
* fix(spotlight): fix empty results on restoring last file search query
- When "remember last query" is enabled and the last query is file search, it shows "no results" until the query is manually modified in full launcher mode.
* fix(spotlight): properly restore last selected mode(tab) when enabled in full launcher mode
* fix(spotlight): allow file trigger in plugins mode(tab)
* fix(spotlight): restore previous mode when clearing '/' file search prefix
When the '/' prefix is removed from the query, the controller now correctly reverts to the previous mode instead of remaining stuck in "files" mode.
* fix(spotlight): code review fix
bbedward