Description of problem: In Mageia3 i586 the notify-send command does not output any popup notification (used for example to warn for a low laptop battery) in a LXDE desktop install. notify-send is installed but the notification-daemon is not running. but I could fix this by altering the LXDE autostart file (/etc/xdg/lxsession/LXDE/autostart), it had an error in the notification daemon path : the wrong one "@/usr/lib/notification-daemon" and the working one is "@/usr/libexec/notification-daemon". The notification daemon binary is under /usr/libexec, im not sure if it is the normal path or it should be relocated to /usr/lib and then the bug will be in the notification daemon install package. Version-Release number of selected component (if applicable): How reproducible: Install LXDE desktop session Steps to Reproduce: 1. install LXDE desktop 2. type the following command: notify-send "test" 3. open the file as root /etc/xdg/lxsession/LXDE/autostart 4. edit the line "@/usr/lib/notification-daemon" and change it to "@/usr/libexec/notification-daemon" 5. logout 6. log in again and then notify-send is working Hope this helps Reproducible: Steps to Reproduce:
Component: Security => RPM PackagesQA Contact: security => (none)
Created attachment 4603 [details] Proposed patch for spec file This bug still exist also in Cauldron. Added proposed patch to spec file.
CC: (none) => napcok
Hi, thanks for reporting this bug. As there is no maintainer for this package I added the committers in CC. (Please set the status to 'assigned' if you are working on it)
Keywords: (none) => TriagedCC: (none) => ennael1, fundawang, lists.jjorge, oliver.bgr
This bug is fixed in Cauldron, still exist in MGA3. I'm apprentice in progress, without svn commit rights, so I can't fix this by myself.
ah, maybe you can ask your mentor for mga3 ?
Sure, I will do that.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD