Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 455289 - Notification daemon crashes after changing theme
Notification daemon crashes after changing theme
Product: Fedora
Classification: Fedora
Component: notification-daemon (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: David Zeuthen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-07-14 13:42 EDT by Martin Sourada
Modified: 2013-03-05 22:56 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-14 17:57:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martin Sourada 2008-07-14 13:42:28 EDT
Description of problem:

Version-Release number of selected component (if applicable):
notification-daemon-0.3.7-9.fc9 as well

How reproducible:

Steps to Reproduce:
1. install notification-daemon-engine-nodoka
2. switch /apps/notification-daemon/theme to nodoka (or back to standard if you
use nodoka already)
Actual results:
Applications emitting notification bubbles stop emiting them, application
restart is necessary to get it working again. notify-send also usually does not
emit the requested bubble on first or second try, but not always, I don't see
any pattern as to how many tries or how much time it takes for the bubbles to
start displaying again.

Expected results:
Theme changes and notification bubbles continue display.

Additional info:
I am now back at F9, but the problem was reproducible on yesterdays rawhide as
well. When I reboot to rawhide again, I recheck the exact versions (though from
a quick look into koji it shouldn't be necessary).
Comment 1 Matthias Clasen 2008-07-14 17:57:16 EDT
Should be fixed in
Comment 2 Martin Sourada 2008-07-15 17:18:33 EDT
Yep, seems it works now :-)

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