noctalia-shell icon indicating copy to clipboard operation
noctalia-shell copied to clipboard

Steam notifications

Open Forceres opened this issue 1 month ago • 10 comments

Description

Steam notifications don't show up.

Steps to Reproduce

  1. Go to Steam (Native) app.
  2. Get notification.
  3. No notification from noctalia-shell.

Expected Behavior

It should intercept notification and show it.

Environment

  • Distro: CachyOS
  • Compositor: Niri
  • Noctalia-shell Version: 3.3.1

Forceres avatar Nov 28 '25 23:11 Forceres

I'm not sure if quickshell is capable of doing that, we just listen to notifications that we get from it. As far as I'm aware no other notification daemon gets the notifications from steam (I might be wrong though).

Description

Steam notifications don't show up.

Steps to Reproduce

1. Go to Steam (Native) app.

2. Get notification.

3. No notification from noctalia-shell.

Expected Behavior

It should intercept notification and show it.

Environment

* Distro: CachyOS

* Compositor: Niri

* Noctalia-shell Version: 3.3.1

Ly-sec avatar Nov 29 '25 07:11 Ly-sec

Also happen with Spotify's Show desktop notification when the song changes I'm pretty sure.

neyfua avatar Nov 29 '25 12:11 neyfua

Also happen with Spotify's Show desktop notification when the song changes I'm pretty sure.

Spotify sends it directly through standard methods (at least on NixOS for me), which means that it gets picked up by notification daemons, including Noctalia's notification system. Steam in particular uses its own toasts system, avoiding the usage of something like notify-send entirely.

r6915ee avatar Nov 30 '25 02:11 r6915ee

Also happen with Spotify's Show desktop notification when the song changes I'm pretty sure.

Spotify sends it directly through standard methods (at least on NixOS for me), which means that it gets picked up by notification daemons, including Noctalia's notification system. Steam in particular uses its own toasts system, avoiding the usage of something like notify-send entirely.

But it somehow doesn't work on my system. It's not like I need it but it's a bug we could improve Imo.

neyfua avatar Nov 30 '25 04:11 neyfua

But it somehow doesn't work on my system. It's not like I need it but it's a bug we could improve Imo.

That might depend on package implementation, in that case. The actual Spotify program on my computer is provided through the NixOS Unstable package, so it's able to access system programs normally. The Spotify Flatpak over on Flathub isn't maintained by Spotify, so I'd assume that it either needs a permission set through either the main Flatpak functionality or something like Flatseal. It could also lack the functionality all together, due to it being wrapped.

r6915ee avatar Nov 30 '25 06:11 r6915ee

But it somehow doesn't work on my system. It's not like I need it but it's a bug we could improve Imo.

That might depend on package implementation, in that case. The actual Spotify program on my computer is provided through the NixOS Unstable package, so it's able to access system programs normally. The Spotify Flatpak over on Flathub isn't maintained by Spotify, so I'd assume that it either needs a permission set through either the main Flatpak functionality or something like Flatseal. It could also lack the functionality all together, due to it being wrapped.

Actually I'm not using the flatpak version, I'm using a package called spotify-launcher available on openSUSE main repo. So I don't know if there's a fix around on openSUSE.

neyfua avatar Nov 30 '25 09:11 neyfua

Actually I'm not using the flatpak version, I'm using a package called spotify-launcher available on openSUSE main repo. So I don't know if there's a fix around on openSUSE.

That would depend on spotify-launcher's implementation, in that case. The openSUSE repositories don't look like they have the normal Spotify client in them.

It might be an issue on spotify-launcher's end.

r6915ee avatar Nov 30 '25 20:11 r6915ee

Actually I'm not using the flatpak version, I'm using a package called spotify-launcher available on openSUSE main repo. So I don't know if there's a fix around on openSUSE.

That would depend on spotify-launcher's implementation, in that case. The openSUSE repositories don't look like they have the normal Spotify client in them.

It might be an issue on spotify-launcher's end.

Oh alright, thank you. But to my notice it works fine with other notification daemons like dunst or SwayNC.

neyfua avatar Dec 01 '25 00:12 neyfua

Oh alright, thank you. But to my notice it works fine with other notification daemons like dunst or SwayNC.

In that case, it might be that spotify-launcher doesn't send the notification through the right specification. Quickshell appears to only support notifications sent through Freedesktop's notification specification (please correct me if I'm wrong on this, though).

r6915ee avatar Dec 01 '25 00:12 r6915ee

Oh alright, thank you. But to my notice it works fine with other notification daemons like dunst or SwayNC.

In that case, it might be that spotify-launcher doesn't send the notification through the right specification. Quickshell appears to only support notifications sent through Freedesktop's notification specification (please correct me if I'm wrong on this, though).

Hmm I don't actually quite understand its behavior so I can't tell if ur right or wrong tho, but thanks for the feedbacks.

neyfua avatar Dec 01 '25 08:12 neyfua

Not related to noctalia, that's a niri issue.

Ly-sec avatar Dec 07 '25 22:12 Ly-sec