On Tue, May 22, 2012 at 09:55:18PM +0200, David Paleino wrote: > 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.
Excuse my ignorance, you are right, wicd was not pulled because of Network-Manager, my mistake. In my system, wicd was pulled in because of the task-xfce-desktop: jfs@silicio:$ LC_ALL=C aptitude why wicd-daemon id wicd Depends wicd-daemon (= 1.7.2.3-1) jfs@silicio:$ LC_ALL=C aptitude why wicd id task-xfce-desktop Recommends wicd I incorrectly assumed that wicd was somehow associated to wireless, when it's not. The starting 'w' got me confused :) > > 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. What I tried to say is that wicd is trying to do things on suspend/resumen even if it's not *configured* for any given interface. At least in my system, I have never configured wicd and my *wired* interface (eth1) has always been managed by /etc/network/interfaces. In this setup (the user has not ever configured wicd and the interfaces are already managed) it doesn't make sense for the suspend script to run at all. > > 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 . I actually don't want wicd to manage *any* of my *wired* interfaces. So I cannot understand why the script runs when: - /etc/wicd/wireless-settings.conf is an empty file - /etc/wicd/wired-settings.conf has not been configured at all (available at http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=37;filename=wired-settings.conf;att=1;bug=557156) > 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.) The problem is: I'm a regular user of /etc/network/interfaces, I use guessnet, and I don't want any networking packages to interfere with my setup. Not NetworkManager, not Wicd, not others. Unfortunately, the different desktop management systems introduce a network manager that interferes with a setup that has been working fine since (IIRC) Woody. I don't mind having wicd installed if that is pulled in by a task and is inactive. But having the software *do* stuff when I have never configured it, nor even started the graphical interface, and have it behave in a way that interferes with my network setup is quite strange. The fact is, that just because I installed the Xfce desktop to test out the *desktop* environment, wicd got pulled in and broke my networking setup (for more information see #557156) and this only happens *when* I suspended the system and resumed from suspend. You are tagging this as 'unreproducible' bug, I believe that it is quite easy to reproduce: 1- Install a bare system 2- Configure the system's networking using a fixed IP address either by using the Debian Installer or by manually editing /etc/network/interfaces after installation 3- Install the xfce-desktop task (which pulls in wicd) 4- Suspend the system 5- Return from suspend Right before step 4, the system will be configured with a static IP address. In step 5 wicd's suspend script will run, even though wicd is unconfigured. And this leads us to a completely broken network setup (using DHCP) due to bug #557156. A way I see to prevent bug #557156 and other future bugs, wicd's suspend script should *not* run if wicd is not being used to manage the system's networking. I don't know wicd's internals, but reviewing wicd's code, it occurs to me than an alternative way would be for the script to check if wicd daemon is running and abort if it's not. That way a sysadmin could simply disable the wicd daemon using wicd's default file and then the suspend script would do nothing. Regards Javier
signature.asc
Description: Digital signature
