Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1021425 [details] Patch 1 of 3 Because Fedora 22 has GNOME 3.16, notification-daemon should be upgraded to the latest 3.16.x release in F22. It currently is at 0.7.6, which is intended for GNOME 3.6 or so.
Created attachment 1021426 [details] Patch 2 of 3
Created attachment 1021427 [details] Patch 3 of 3
I offer to co-maintain this package. Let me know if you have any questions.
Also, this update is needed because: 1. Packaging GNOME Flashback 3.16.x in F22 depends on it (1219043) 2. Various bugs were fixed, such as: - A crash with newer glib versions - A crash in hint_to_boolean - Notifications with long text are not positioned properly
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
notification-daemon-3.14.1-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/notification-daemon-3.14.1-1.fc21
notification-daemon-3.16.1-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/notification-daemon-3.16.1-1.fc22
Package notification-daemon-3.16.1-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing notification-daemon-3.16.1-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-10338/notification-daemon-3.16.1-1.fc22 then log in and leave karma (feedback).
notification-daemon-3.14.1-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/notification-daemon-3.14.1-2.fc21
notification-daemon-3.16.1-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
notification-daemon-3.14.1-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.