On 16/05/07, Azalin <[EMAIL PROTECTED]> wrote: > Dear Dave, > > so not to cloud the launchpad bug report with our conversation I > decided to mail you directly. I hope that is ok. >
Yep no problem > In any case, what I mean with SOMEONE fix the problem is that someone > from Canonical or at least someone involved in maintaining Firestarter > should fix this problem. > Its worrying that this has been left out in the cold especially with a fix sitting there. > As far as your fix is concerned, why not try the supplied script in > the bugreport and place it as 50firestarter (make it executable) in > the dispatcher.d directory of NetworkManager. That script will not be > replaced by an update, at least I doubt it and if it will then it will > most defenitely be replaced by something that is also trying to fix > this issue so no harm can come from that. Whilst when firestarter is > updated, the firestarter script might be updated and thus your edited > version might be replaced. The problem most likely will reappear. With > the dispatcher script I assume it works for wireless connections as > well. Just tested it - works a treat with my wifi. > > I would say, just give it a go. > > Cheers, > > Alex. > -- The unavoidable price of reliability is simplicity. -- C.A.R. Hoare -- Firestarter init fails on system boot when NetworkManager is used https://bugs.launchpad.net/bugs/42759 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
