Skip to content
SmallTardigradePublic

About

One Wayland daemon for notifications, the OSD and a control centre, so all three finally look like the same desktop. Plasma, Hyprland, sway.

Topics

Resources

Contributing

Security policy

Stars

4 stars

Watchers

0 watching

Forks

Repository files navigation

glassosd

A themeable notification daemon, on-screen display and control centre for Wayland.

Most desktops split these across three programs that look nothing like each other: a notification daemon, whatever the compositor uses for its volume popup, and a separate control centre. glassosd draws all three from one stylesheet, and behaves the way a notification daemon should when the desktop gets busy.

A notification over the desktop

It ships with a glass look because that is what it was built for. It is not locked to it — every colour, radius, shadow and font comes from a JSON theme file, and the repository includes Material, Nord and flat themes with no translucency at all. See Theming.

glassosdctl theme-file material-dark   # or nord, frosted, rose, glass-dark

Blur strength is your compositor's setting, not ours. ext-background-effect-v1 lets a client name the region to blur, not how hard. On KWin: System Settings → Desktop Effects → Blur, or kwriteconfig6 --file kwinrc --group Effect-blur --key BlurStrength <1-15>. A stronger blur samples a wider area, so over a bright window it pulls that brightness in — the surface gets lighter as well as hazier.


Contents


What it does

Three modules, each of which can be turned off independently — you are not made to take the OSD to get the notification daemon, or the other way round.

Notifications

A full freedesktop Desktop Notifications implementation, plus the KDE extensions: inline reply, action icons, raw image hints and NotificationReplied. Nothing about the layout is special-cased per application — buttons, reply fields and progress bars appear because the sending application published them.

The behaviour that matters once the desktop is actually busy:

Rate limiting at most N on screen; the rest queue behind a "+N more" indicator
Burst coalescing 30 mails arriving at once become one card that says 30
Replace by tag stack tags and replaces_id update a card in place
Idle threshold popups that appeared while you were away wait for you to come back
Hover to hold the dwell timer pauses while the pointer is over a card
Swipe to dismiss drag a card aside with a pointer or a finger
Multiple displays follows the screen you're using, or pin popups, OSD and centre to different ones
Persistent history survives a restart, grouped by app, collapsible
Do Not Disturb persists across login
Per-app rules match on app, summary, body, category or urgency

On-screen display

Volume, microphone, brightness, keyboard backlight, caps/num/Fn lock, touchpad, wifi, bluetooth and power profile — as a continuous bar or as discrete segments. Optional volume feedback sounds once, when you stop adjusting, at the level you settled on, rather than stuttering on every step.

Control centre

Notification history grouped by app, plus optional widgets: an MPRIS media player, volume and brightness sliders, a Do Not Disturb toggle, and a configurable quick-action button grid.

What that looks like

Grouping, mixed apps and a critical notification Inline reply, actions and a progress bar
Five messages from one app collapse into one counted card. Critical urgency is marked on the app name and nowhere else. Inline reply, action buttons and progress bars appear because the sender published them — nothing is special-cased per application.
The notification centre A busy desktop
History grouped by app, searchable, with per-app settings behind the sliders icon on any group header. At most N on screen and the rest queued behind a count, rather than thirty cards covering the desktop.

Volume, brightness, microphone and the lock-key indicators

The OSD covers volume, microphone, brightness and the caps, num and Fn lock indicators. A locked key fills its chip with the accent colour, so the state reads without stopping to read the words.



How it compares

glassosd exists because dunst and swaync each had half of what was wanted.

glassosd dunst swaync
Rate limiting ✅ ✅ ✗
Burst coalescing (wake-from-suspend) ✅ partial¹ ✗
Idle threshold ✅ ✅ ✗
Persistent history ✅ ✗² ✅
Control centre ✅ ✗ ✅
Media player widget ✅ ✗ ✅
Inline reply ✅ ✗ ✅
App icons ✅ ✅ ✅
Volume / brightness OSD ✅ ✗ ✗³
Lock-key OSD ✅ (KWin only) ✗ ✗
Theming JSON config file CSS
X11 ✗ ✅ ✗

¹ dunst's notification_limit queues rather than merges, so a 30-message burst still drips through one at a time. ² dunst keeps history in memory for the session only. ³ swayosd is a separate program.

dunst is still the right choice if you need X11. glassosd is Wayland only.



Install

Fedora

sudo dnf copr enable smalltardigrade/glassosd
sudo dnf install glassosd

The package installs man glassosd, man glassosdctl and man glassosdrc, so the full configuration reference is available offline.

Built for Fedora 43, 44 and Rawhide (x86_64). glassosd --help and glassosdctl --help both work without a session, so you can check what you got before logging in to a desktop.

Arch

Every dependency is in extra. A PKGBUILD sketch is in packaging/DEPENDENCIES.md.

From source

See Building.



Setup

glassosd-setup

That walks through everything below, asking before each change, and glassosd-setup --undo reverts all of it. If you would rather do it by hand:

systemctl --user enable --now glassosd.service

glassosd is also D-Bus activated, so the next application to post a notification would start it anyway — but the OSD and the control centre need it running for the whole session.

If you already run a notification daemon, stop it first. Only one program can own org.freedesktop.Notifications:

systemctl --user disable --now dunst.service       # or swaync.service, mako.service

On Plasma, turn off the built-in popups so they do not double up:

kwriteconfig6 --file plasmarc --group OSD --key Enabled false

That setting lives in your own plasmarc, so removing glassosd later will not put it back and Plasma's volume and brightness popups stay gone. To restore them:

kwriteconfig6 --notify --file plasmarc --group OSD --key Enabled true

To keep the notification daemon you already have and use glassosd only for the OSD:

glassosdctl module notifications off
glassosdctl restart

File operations

Dolphin, Ark and everything else built on KIO report a copy or an extraction to Plasma's job view (org.kde.JobViewServer), not to the notification interface. Plasma shows those in its own notification popups, which are not there while glassosd is the notification daemon, so a long transfer would show nothing. glassosd listens for those jobs and shows each as a progress card: what is happening and where, the file, how far it has got, the speed and the time left. When it finishes the card says so ("Copied to Documents") with the totals. A job that finishes within a moment gets no card, a job you cancel or skip leaves no card, and a card you dismiss stays dismissed while the job carries on.

Apps with no KDE job that publish a taskbar progress bar (the Unity launcher entry that Chromium-based browsers and Steam send) are shown the same way, with the percentage. Firefox-based browsers do not send it, so their downloads show no progress card.

The cards are read-only: there is no pause or cancel. Those commands have to come from the owner of org.kde.JobViewServer, which is plasmashell and cannot be replaced, and a listener cannot send. glassosd does not take anything from plasmashell, so its taskbar progress is unaffected. Turning this off (glassosdctl set JobProgress false && glassosdctl restart) does not bring Plasma's cards back; it means no file progress is shown at all. To drop only the taskbar-progress cards (terminals report apt and cargo this way) and keep Dolphin's, set AppProgress to false; to hide one app, use a rule such as glassosdctl rule-set no-term-progress category=transfer desktop_entry=org.kde.konsole skip_display=true.

Sandboxed apps

Flatpaks cannot reach org.freedesktop.Notifications — it is outside their sandbox. They go through xdg-desktop-portal, which hands off to whichever backend the desktop nominates, and which has no fallback: with no backend it exports no notification interface at all.

glassosd implements that backend, so it can serve sandboxed applications directly rather than through xdg-desktop-portal-gtk as a relay. It declares version 2 of the interface, which is what keeps sounds, categories, markup bodies, display hints and reply buttons from being stripped on the way through — and the app id it receives is verified by the portal rather than claimed by the sender, so per-app rules are reliable for Flatpaks.

It is not selected automatically: that would take notifications away from the desktop's own daemon on any machine that merely has glassosd installed. glassosd-setup detects the situation and offers to point the portal here. The full explanation, and how to diagnose one application end to end, is in docs/portal-routing.md.


Compositor support

glassosd needs wlr-layer-shell-unstable-v1. That covers KDE Plasma, Hyprland, sway, river, Wayfire, labwc and anything else wlroots-based.

It does not work on GNOME, which does not implement layer-shell, or on X11.

Plasma integration is detected at runtime, never required at build time. Where a feature has no portable equivalent there is a CLI way in:

Feature Plasma Elsewhere
Notifications, centre, history, DND, rules ✅ ✅
Background blur ✅ automatic compositor config, below
Volume/brightness OSD ✅ automatic route media keys through glassosdctl osd
Global shortcuts ✅ registered for you bind glassosdctl in your config
Caps/Num Lock OSD ✅ ✗ — needs org_kde_kwin_keystate, KWin only
Tray icon ✅ ✅ with any StatusNotifierItem host (waybar)

Per-compositor configuration — layer rules for blur, and media-key and shortcut bindings for Hyprland and sway — is in docs/compositors.md.


Configuring it

Everything lives in ~/.config/glassosdrc, and every key has a glassosdctl equivalent that applies live, with no restart.

glassosdctl status               # what is running, and every current setting
glassosdctl set Limit 5          # popups on screen at once
glassosdctl position bottom-right
glassosdctl theme-file nord
glassosdctl test                 # fire the demo sequence

Themes are JSON, not CSS — QML has no CSS engine, and pretending otherwise would mean shipping a fake one. A theme only needs the keys it changes, so a two-line theme is a valid theme:

{
  "accent": "#ff7043",
  "card.background": "#1a1a1a",
  "radius.card": 4
}

Saving the file re-themes the running daemon. material-dark.json and nord.json in themes/ are worked examples of turning the glass off entirely.

The full reference is man glassosdrc — every setting, the rules engine, focus modes, sounds, widgets, the button grid and all the theme keys.


Documentation

man glassosd the daemon and its modules
man glassosdctl every command
man glassosdrc configuration, rules, sounds, widgets, themes
docs/troubleshooting.md when something does not work
docs/portal-routing.md sandboxed apps whose notifications never arrive
docs/compositors.md Hyprland and sway setup
CONTRIBUTING.md building from source
packaging/DEPENDENCIES.md package names per distribution

Everything glassosdctl does goes through org.glassosd.Control on the session bus, so it works identically on every compositor:

busctl --user introspect org.glassosd.Daemon /Control org.glassosd.Control

Reporting bugs

Please use the issue tracker. Include:

glassosdctl version
glassosdctl status
journalctl --user -u glassosd -n 100 --no-pager
echo "$XDG_CURRENT_DESKTOP / $XDG_SESSION_TYPE"

For a rendering problem, a screenshot helps — please check it for anything private before attaching it.

For a problem with one application's notifications, capture what it actually sends:

dbus-monitor --session "interface='org.freedesktop.Notifications'"

Feature ideas and questions are better in [Discussions][discussions] than the issue tracker.



Building

See CONTRIBUTING.md.


Stopping or uninstalling

Disabling the service is not enough on its own. glassosd is started on demand — by any application posting a notification, and by xdg-desktop-portal whenever its configuration still names glassosd as the notification backend — so a disabled glassosd comes back. If that happens while another daemon is showing your notifications, glassosd relays Flatpak notifications to it and tells you once why it was started, rather than leaving the portal waiting.

The off switch is the same as the first step of uninstalling. It leaves the settings it asked you to change, because they are yours and live in your own config, so put them back:

glassosd-setup --undo

That re-enables Plasma's built-in OSD and restores portal notification routing, asking before each one. It works whether or not you used glassosd-setup to make the changes in the first place.

Then remove the package however you installed it. Your notification history, settings and themes stay in ~/.local/share/glassosd and ~/.config/glassosdrc; delete those too if you want nothing left.

If you have already uninstalled and your volume and brightness popups are gone, that is Plasma's own OSD still switched off. One command brings it back:

kwriteconfig6 --notify --file plasmarc --group OSD --key Enabled true

Licence

GPL-2.0-or-later.

This is not a free choice. src/osdmodel.cpp is a port of shell/osd.cpp from plasma-workspace, which is GPL-2.0-or-later; the original authors' copyright is carried in that file's header, and everything derived from it inherits those terms.

The icon set in qml/icons/ and the bundled themes are CC0-1.0, so they can be lifted into a bar, a theme or another shell without inheriting the GPL.

The project is REUSE compliant — every file carries an SPDX header or is covered by REUSE.toml.


Developed with Claude.

About

One Wayland daemon for notifications, the OSD and a control centre, so all three finally look like the same desktop. Plasma, Hyprland, sway.

Topics

Resources

Contributing

Security policy

Stars

4 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages