tags 673822 upstream unreproducible moreinfo thanks On Mon, 21 May 2012 17:47:16 +0200, Javier Fernández-Sanguino Peña wrote:
> I'm running a desktop system which does *not* have a Wireless interface but > Network-manager (installed because of GNOME3) dependencies pulls in > wicd-daemon unconditionally. This isn't true. Wicd isn't listed among the dependencies of NM -- if it was the case, it would be *VERY* weird. Please run a "aptitude why wicd-daemon", and check what pulled it in. > This package installs a script under /usr/lib/pm-utils/sleep.d/55wicd and > gets run after any resume of hibernation. > > However, since this script is not a configuration file and it does not provide > any way to disable it, the script will run regardless of whether the system is > using a wireless connection or a wired connection (as is my case). Regardless of what the comments in that file say, it just runs wicd suspend/resume, and the existence of a wireless connection is not taken into consideration. > If possible, I would appreciate if the script would NO-OP either > > a) by detecting that wicd is not configured using some kind of system > indication. For example, in my system, /etc/wicd/wireless-settings.conf is an > empty (0-bytes) file which could be an indication. If you don't want wicd to manage wireless, just clear the "wireless_interface" entry in manager-settings.conf . > b) by making it possible for the administrator to disable it. This could be > possible by either using a defaults file (under /etc/) or by moving the script > under /etc/ and replacing /usr/lib/pm-utils/sleep.d/55wicd with a symbolic > link. > > This would enable adminsitrators to remove, if required, this script from > suspend. A better option would be making it configurable from within WICD. > On the one hand this would save some CPU cycles when resuming for hibernation, > making the system startup faster and, on the other hand, it would avoid > potential issues that could be caused by > running /usr/share/wicd/daemon/autoconnect.py > (or /usr/share/wicd/daemon/suspend.py) on systems that are really not > configured with any Wireless interface. Again, this has nothing to do with "wireless" interfaces. Since you seem to be a NM user, I guess you don't want wicd at all. At the beginning of your mail you said it was "pulled in" -- this shouldn't happen, and certainly is not a bug in the wicd packages. Please check why it was pulled in first; then decide whether use it or just keep NM. Using both programs is technically possible, but not really encouraged. Keeping just one of them will save you tons of possible problems and Heisenbugs (and no, I won't add a Conflict.) Kindly, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 ----|---- http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
