Bug 2517249 - noctalia RPM should Provide: desktop-notification-daemon
Summary: noctalia RPM should Provide: desktop-notification-daemon
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: noctalia
Version: 44
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Carl George 🤠
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-16 17:38 UTC by James D List
Modified: 2026-08-27 00:55 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-08-18 09:56:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description James D List 2026-08-16 17:38:24 UTC
Fedora 44's noctalia package does not currently provide the RPM virtual capability desktop-notification-daemon, despite Noctalia v5 implementing a desktop notification daemon.

This causes packages such as blueman, which require desktop-notification-daemon, to require another notification daemon package. On my Fedora Sway installation, that requirement is currently being satisfied by gnome-shell, preventing the GNOME/GDM dependency stack from being removed.

Reproduction:

$ rpm -q --provides noctalia
application()
application(dev.noctalia.Noctalia.desktop)
bundled(fzy)
bundled(luau)
bundled(material_color_utilities)
bundled(wuffs)
noctalia = 5.0.0~beta.7-1.fc44
noctalia(x86-64) = 5.0.0~beta.7-1.fc44


$ dnf repoquery --requires blueman | grep notification
desktop-notification-daemon


$ dnf repoquery --whatprovides desktop-notification-daemon
# includes gnome-shell, mako, dunst, SwayNotificationCenter, etc.,
# but not noctalia

Would it be appropriate for the Fedora package to add:

Provides: desktop-notification-daemon

Noctalia's built-in notification daemon already implements the notification service, so this would allow RPM dependencies such as Blueman's to be satisfied by Noctalia itself.

Comment 1 Carl George 🤠 2026-08-17 19:29:11 UTC
When I was first creating this package I did notice that some third party packages had this provides.  I asked around with other Fedora maintainers and no one knew why this was a thing.  It not covered in the guidelines at all.  Is this just something the blueman package came up with?  The commit adding that requires to blueman has no explanation about why it's used.

https://src.fedoraproject.org/rpms/blueman/c/7846d32199bad86991454aba859626b49bd89707?branch=rawhide

I'm not necessarily opposed to adding the provides, I just want to understand it better before proceeding.

Comment 2 James D List 2026-08-17 21:08:48 UTC
I had a better look and it seems like desktop-notification-daemon is an old virtual capability but isn't currently very well documented.

dnf repoquery --whatrequires desktop-notification-daemon returns only blueman and system-config-printer so it seems not many packages use this provides anymore.

I ran into this as noctalia is acts as my notification daemon but doesn't advertise the provides so it brought in another package (which happened to be gnome-shell which was keeping GDM and large part of the GNOME stack installed). Installing mako which satisfied the desktop-notification-daemon allowed the GNOME stack to be removed even when not actively using the application.

I also found that Terra's Fedora 44 build of Noctalia V5 appears to provide desktop-notification-daemon (https://pkgs.org/download/desktop-notification-daemon). However I'm using the package from the official Fedora repos.

Comment 3 Carl George 🤠 2026-08-18 02:34:40 UTC
I think I found the origin of it in the commit history of the libnotify package.  I was surprised to see it's 20 years old.

https://src.fedoraproject.org/rpms/libnotify/c/03f15ef7223cb0a35efe7c09f2eade429ab7b930?branch=rawhide

However, it was dropped from that package 11 years ago for similar reasons that you're describing, pulling in surprise unwanted dependencies.

https://src.fedoraproject.org/rpms/libnotify/c/e4ea37910284f2ba30c5cc421a8a09613805d85f?branch=rawhide

Based on that, I think a better approach would be to change blueman and system-config-printer to no longer requires desktop-notification-daemon.  I've submitted pull requests to do that.

https://src.fedoraproject.org/rpms/blueman/pull-request/4

https://src.fedoraproject.org/rpms/system-config-printer/pull-request/4

Comment 4 Fedora Update System 2026-08-18 09:47:47 UTC
FEDORA-2026-11368c22d9 (system-config-printer-1.5.18-20.fc46) has been submitted as an update to Fedora 46.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-11368c22d9

Comment 5 Fedora Update System 2026-08-18 09:56:24 UTC
FEDORA-2026-11368c22d9 (system-config-printer-1.5.18-20.fc46) has been pushed to the Fedora 46 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2026-08-18 09:59:42 UTC
FEDORA-2026-503c992157 (system-config-printer-1.5.18-20.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-503c992157

Comment 7 Fedora Update System 2026-08-18 10:08:24 UTC
FEDORA-2026-503c992157 (system-config-printer-1.5.18-20.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2026-08-18 22:57:10 UTC
FEDORA-2026-efb77778ec (system-config-printer-1.5.18-20.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-efb77778ec

Comment 9 Fedora Update System 2026-08-18 23:01:37 UTC
FEDORA-2026-391e777dcc (blueman-2.4.6-10.fc46) has been submitted as an update to Fedora 46.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-391e777dcc

Comment 10 Fedora Update System 2026-08-18 23:02:35 UTC
FEDORA-2026-63ce789408 (blueman-2.4.6-10.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-63ce789408

Comment 11 Fedora Update System 2026-08-18 23:05:23 UTC
FEDORA-2026-391e777dcc (blueman-2.4.6-10.fc46) has been pushed to the Fedora 46 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2026-08-18 23:05:26 UTC
FEDORA-2026-63ce789408 (blueman-2.4.6-10.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2026-08-18 23:13:02 UTC
FEDORA-2026-70d6c3fec6 (blueman-2.4.6-7.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-70d6c3fec6

Comment 14 Fedora Update System 2026-08-19 01:39:28 UTC
FEDORA-2026-efb77778ec has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-efb77778ec`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-efb77778ec

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 15 Fedora Update System 2026-08-19 01:40:33 UTC
FEDORA-2026-70d6c3fec6 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-70d6c3fec6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-70d6c3fec6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 16 Fedora Update System 2026-08-20 15:32:37 UTC
FEDORA-2026-efb77778ec (system-config-printer-1.5.18-20.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2026-08-27 00:55:05 UTC
FEDORA-2026-70d6c3fec6 (blueman-2.4.6-7.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.