Hi gmayer,
Can you open a new bug report for us regarding the issue you are seeing?
Also be sure to file your bug report against the linux-ubuntu-modules
package. In your new report please include the information outlined
here: https://wiki.ubuntu.com/KernelTeamBugPolicies . Please be sure to
at
I must say that I'm still encountering this problem. I've ignored or
worked around it for a while but it's getting damn annoying now.
Symptoms: ipw3945 connects to untrusted wireless networks all by itself,
causing havoc with NM and lately even on the command line. I need to
restart NM and/or relo
I no longer see this behaviour with recent ipw3945 (updated because of
work going on wrt Bug #121439).
If nobody else has this problem any more, perhaps we could call it
fixed.
--
Gutsy Regression: ipw3945 Connects To Untrusted Networks
https://bugs.launchpad.net/bugs/129213
You received this bu
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: linux-meta => linux-source-2.6.22
--
Gutsy Regression: ipw3945 Connects To Untrusted Networks
https://bugs.launchpad.net/bugs/129213
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
This is not a NetworkManager bug, it's a problem with the driver:
ipw3945 connects to untrusted networks all by itself, whether or not NM
is running.
Restarting DBUS does nothing for me... sometimes 'killall
ipw3945d-`uname -r` && rmmod ipw3945 && modprobe ipw3945' does, though.
Sometimes NM will
** Changed in: network-manager (Ubuntu)
Sourcepackagename: linux-meta => network-manager
Importance: Undecided => Medium
--
Gutsy Regression: ipw3945 Connects To Untrusted Networks
https://bugs.launchpad.net/bugs/129213
You received this bug notification because you are a member of Ubuntu
Bugs
I'v seen the same behavior. Restarting DBUS works most of the time to
connect to the WPA(2) network again.
** Changed in: linux-meta (Ubuntu)
Status: New => Confirmed
--
Gutsy Regression: ipw3945 Connects To Untrusted Networks
https://bugs.launchpad.net/bugs/129213
You received this bug n