Gutsy: WLAN via Network-Manager lacks long-term stability
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
Invalid
|
Undecided
|
Brian Murray | ||
Bug Description
Binary package hint: network-manager
Ever since I upgraded to Gutsy (fresh Tribe 5 install, by the way, just in case you wondered) wireless networking started going weird, got fixed somehow just to show even stranger issues. I'll report some of them seperately.
First of all, I use an on-board IPW2200 WLAN adaptor which connects to a Linksys WRT54G most of the time. I didn't get the chance to test it on different setups, yet.
The main issue at the moment is the general instability of my connection causing loss of signal and having to reconnect to the AP. Most of the time this goes without much trouble, however, sometimes it keeps trying to re-connect until the Network-Manager Daemon itself shuts down removing the nm-applet from the notification area, even though the process is still visible in the gnome-system-
Fortunately there is a log which I'll attach:
Sep 26 09:25:18 rechner avahi-daemon[5118]: Withdrawing address record for fe80::20e:
Sep 26 09:25:34 rechner NetworkManager: <WARN> nm_signal_
Sep 26 09:25:34 rechner NetworkManager: ******************* START *******
Sep 26 09:25:34 rechner NetworkManager: (no debugging symbols found)
Sep 26 09:25:34 rechner NetworkManager: Using host libthread_db library "/lib/tls/
Sep 26 09:25:34 rechner NetworkManager: (no debugging symbols found)
Sep 26 09:25:34 rechner last message repeated 12 times
Sep 26 09:25:35 rechner NetworkManager: [Thread debugging using libthread_db enabled]
Sep 26 09:25:35 rechner NetworkManager: [New Thread -1212238160 (LWP 4651)]
Sep 26 09:25:35 rechner NetworkManager: [New Thread -1229026416 (LWP 5553)]
Sep 26 09:25:35 rechner NetworkManager: [New Thread -1220633712 (LWP 4799)]
Sep 26 09:25:35 rechner NetworkManager: [New Thread -1212241008 (LWP 4789)]
Sep 26 09:25:35 rechner NetworkManager: (no debugging symbols found)
Sep 26 09:25:35 rechner last message repeated 4 times
Sep 26 09:25:35 rechner NetworkManager: 0xffffe410 in __kernel_vsyscall ()
Sep 26 09:25:35 rechner NetworkManager: ******************* END *******
It always ends like this, but I don't understand why. Sometimes the "Signal 11" line comes first.
| Pizuz (florian-fahr) wrote | #1 |
| Alexander Sack (asac) wrote | #2 |
| Changed in network-manager: | |
| status: | New → Incomplete |
| Brian Murray (brian-murray) wrote | #3 |
| Changed in network-manager: | |
| assignee: | nobody → brian-murray |
| status: | Incomplete → Invalid |
Might be a good idea to add that signal 11 means segmentation fault... In case someone wondered ;)
If anyone could modify the report to include this I'd be thankful.