On Thu, 26 Mar 2009 11:23:47 +0000 Chris Vine <ch...@cvine.freeserve.co.uk> wrote:
> On Wed, 25 Mar 2009 21:01:25 -0500
> Victor Lowther <victor.lowt...@gmail.com> wrote:
>
> > In that case, would you mind trying the following patch on 75modules
> > with an unmodified 55wicd?
> >
> > BEGIN PATCH
> > diff --git a/sleep.d/75modules b/sleep.d/75modules
> > index 3f292e4..ed8bbcf 100755
> > --- a/sleep.d/75modules
> > +++ b/sleep.d/75modules
> > @@ -15,6 +15,7 @@ suspend_modules()
> > resume_modules()
> > {
> > modreload
> > + udevadm settle --timeout=5
> > }
> >
> > case "$1" in
> > END PATCH
>
> > The above patch should wait up to 5 seconds for udev to settle after
> > reloading modules. Can you see if that allows an unmodified 55wicd
> > to work properly?
>
> No, 55wicd still hangs.
>
> I shouldn't worry too much about it. Only people writing their own
> udev rules are going to run into this problem - it so happens that I
> have a rule which causes the wireless interface to come up whenever a
> USB wireless stick is inserted. It so happens that this rule is also
> invoked when rt73usb is reloaded on resumption if the stick is already
> there (something which is actually of itself quite useful, so no
> complaints about udev).
>
> If a solution is needed, I think it is at the wicd level so that
> calling /usr/lib/wicd/autoconnect.py twice doesn't hang. It is really
> a wicd interface bug - a duplicate call should return gracefully.
Chris,
Sorry for the delay on this, but can you file a bug [1] with the wicd
project so that this doesn't get lost? I'd like to make sure it's
fixed in the 1.6.x branch (which is slated for release soon, I hope).
[1] https://bugs.launchpad.net/wicd
-RW
signature.asc
Description: PGP signature
_______________________________________________ Pm-utils mailing list Pm-utils@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pm-utils
