[Bug 99868] Re: ipw3945: wireless key is not set from interfaces on boot.

2007-06-11 Thread Brian Murray
This bug report is being closed due to your last comment regarding this being fixed with an update. Thanks again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find. ** Changed in: Ubuntu Status: Needs Info => Fix Rele

Re: [Bug 99868] Re: ipw3945: wireless key is not set from interfaces on boot.

2007-06-10 Thread nikwik
Thank you for all! The issue is not there any more. (Running updated feisty, wlan works very fine.) I am not sure as to what update made it run, however. Sorry for not having taken any action before, to .close the bug'. With many thank yous Niklas On 6/9/07, Brian Murray <[EMAIL PROTECTED]> wro

[Bug 99868] Re: ipw3945: wireless key is not set from interfaces on boot.

2007-06-08 Thread Brian Murray
Thanks for taking the time to report this bug and helping to make Ubuntu better. Now that the final version of Feisty Fawn is available we were wondering if this issue still exists. Thanks in advance. -- ipw3945: wireless key is not set from interfaces on boot. https://bugs.launchpad.net/bugs/9

[Bug 99868] Re: ipw3945: wireless key is not set from interfaces on boot.

2007-04-02 Thread nikwik
Yes, the lrms are installed, and the interface comes to life in a perfect manner after restarting it by "ifdown eth1; ifup eth1". The problem is not, however, solved by fiddling around in the network-admin gui! Might have something to do with the network-admin? It is never becoming reallhy mature,

[Bug 99868] Re: ipw3945: wireless key is not set from interfaces on boot.

2007-04-02 Thread Brian Murray
Thanks for taking the time to report this bug and helping to make Ubuntu better. Do you have the linux-restricted-modules package installed? That contains a daemon needed for the ipw3945 chipset. Thanks in advance. ** Changed in: Ubuntu Assignee: (unassigned) => Brian Murray Status: