Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#30104 - [libnotify] 0.7.5-1 daemon stops instead of displaying message
Attached to Project:
Arch Linux
Opened by siriusb (siriusb) - Saturday, 02 June 2012, 08:50 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 17 October 2012, 12:00 GMT
Opened by siriusb (siriusb) - Saturday, 02 June 2012, 08:50 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 17 October 2012, 12:00 GMT
|
DetailsDescription:
Using openbox + tint2, notification-daemon stopped working. When sending a message with notify-send, daemon stops and no message pops up. Also Thunar (daemon-mode) doesn't notify about events (mounting USB device etc). Additional info: * package version(s) libnotify 0.7.5-1 openbox 3.5.0-7 (lxde) tint2 0.11-5 * config and/or log files etc. May 31 08:38:26 localhost kernel: [ 3378.486740] notification-da[1716] trap int3 ip:7f5204c9c5e1 sp:7fffed96f420 error:0 Steps to reproduce: 1. start daemon (/usr/lib/notification-daemon-1.0/notification-daemon) 2. send message (notify-send 'Hello world!' 'This is an example notification.' --icon=dialog-information) 3. no message and daemon not running |
This task depends upon
Closed by Gaetan Bisson (vesath)
Wednesday, 17 October 2012, 12:00 GMT
Reason for closing: None
Additional comments about closing: see comments
Wednesday, 17 October 2012, 12:00 GMT
Reason for closing: None
Additional comments about closing: see comments
Comment by Ionut Biru (wonder) -
Saturday, 02 June 2012, 13:54 GMT
as you can see, notification-daemon crashed. you need to debug this crasher and report upstream about it.
Comment by Greg (dolby) -
Tuesday, 16 October 2012, 07:49 GMT
Has this been reported upstream?
Comment by siriusb (siriusb) -
Tuesday, 16 October 2012, 15:08 GMT
I'm sorry I wasn't too active managing my bug reports lately. Anyway, notification-daemon started working after a while, so pls consider this issue closed. Thanks.