Arch Linux

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!
Tasklist

FS#15815 - [wicd] notification-daemon dependency should be optional

Attached to Project: Arch Linux
Opened by Thomas Dy (stoichyu) - Wednesday, 05 August 2009, 18:41 GMT
Last edited by Isenmann Daniel (ise) - Sunday, 20 September 2009, 08:37 GMT
Task Type General Gripe
Category Packages: Extra
Status Closed
Assigned To Isenmann Daniel (ise)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The current wicd-1.6.2 package automatically pulls in notification-daemon even if it's not needed (when running KDE for example). It should be an optional dependency since GNOME and XFCE would most likely already install notification-daemon anyway.
This task depends upon

Closed by  Isenmann Daniel (ise)
Sunday, 20 September 2009, 08:37 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in wicd-1.6.2.2-2
Comment by Roman Kyrylych (Romashka) - Wednesday, 05 August 2009, 18:56 GMT
xfce4-notifyd provides notification-daemon,
the problem is that Pacman chooses the first package it finds (which is notification-daemon)
so it's not really a problem in wicd package

on the other hand - is notification-daemon a required dependency or can it be optdepends?
Comment by Jan de Groot (JGC) - Wednesday, 05 August 2009, 22:10 GMT
If there's no notification daemon available, the popup balloons wont get shown. As wicd's primary function is setting up networking and not nagging users with notifications, I don't think it's a problem moving it to optdepends.
Comment by Isenmann Daniel (ise) - Thursday, 06 August 2009, 05:27 GMT
It was added because of this bug report:  FS#15089  (http://bugs.archlinux.org/task/15089)
Some users had problems if no notification-daemon was installed.

But I completly agree with Jan, it should setting up network and not nagging users. On the other hand, it's useful for the user if he get some messages ("Disconnect", etc.) from the wicd-client.
Comment by Roman Kyrylych (Romashka) - Thursday, 06 August 2009, 07:49 GMT
I think  FS#15089  is upstream bug - wicd checks for notification daemon and switches off notification support but then still tries to use pynotify.

Loading...