Comment 25 for bug 42759

Hi Dave,

dave s schreef:
>
>> 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.
>
>
It indeed IS worrying... but there are some more worrying things at the
moment. like the tty / sata problem nobody seems to care about... there
is a work around, just like with firestarter, but there doesn't seem to
be anyone interested in fixing it in the distribution... strange.
>
>> 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.
>
>
>
Excellent. That way you at least know that your connection will be
protected even when firestarter is updated and the firestarter.sh is
replaced with another one :)

Cheers,

Alex.