Karmic WPA connection disconnects regularly

Bug #401272 reported by Michael Nelson
40
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
Nominated for Karmic by crazyserver

Bug Description

Binary package hint: network-manager

Since upgrading my karmic netbook approximately 1 week ago (sorry it's not more specific), my wireless connection consistently drops out frequently (approx. once per minute).

Other machines (using Jaunty) on the same wireless router are unaffected.

ProblemType: Bug
Architecture: i386
Date: Sun Jul 19 05:41:20 2009
DistroRelease: Ubuntu 9.10
IfupdownConfig:
 auto lo
 iface lo inet loopback
Package: network-manager 0.7.1-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-2.17-generic
SourcePackage: network-manager
Tags: ubuntu-unr
Uname: Linux 2.6.31-2-generic i686

Revision history for this message
Michael Nelson (michael.nelson) wrote :
Revision history for this message
NoahY (noahy) wrote :

Can confirm this, only recently, though... about a week ago there was no problem. Also using WPA on Karmic, AMD 64

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
NoahY (noahy) wrote :

Seems to be fixed in the latest upgrades (July 25th)... will test more.

Revision history for this message
NoahY (noahy) wrote :

Yep, I'm going to mark this as fixed... feel free to change it back if the problem still persists for you.

Changed in network-manager (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
nbubis (nbubis) wrote :

Hi,

I'm still experiencing this bug on karmic (as of Aug 29). Wireless works great with unsecured networks but disconnects about once a minute on secured WPA networks. I've tried running "sudo service apparmor stop" as suggested by some - but the problem persists.

I'm running the 2.6.31-8 (x86_64) kernel, with hardware listed as:

Ethernet controller : Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express
Network controller : Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection

Revision history for this message
Jonathan Jesse (jjesse) wrote :

running fully updated kubuntu 9.10 netbook edition i am experiencing htis bug again, my Mac and my windows machines dont have this problem. also in an earlier alpha of 9.10 I had no problems.
can soeone re-look into this bug?

Thanks

Revision history for this message
Bryan Moore (moore-bryan) wrote :

I can confirm as well.
Karmic running on Lenovo z61e with Atheros AR5212 802.11abg NIC; I use neither NetworkManager nor wicd, just straight /etc/network/interfaces and /etc/wpa_supplicant.conf.

Revision history for this message
crazyserver (crazyserver) wrote :

This happens also to me with all updates since today

Changed in network-manager (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
another_sam (anothersam) wrote :

I had this one
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/348204
using WPA and WPA2 but now is fixed. currently I use WPA2 with no problems. I did not test WPA.

Revision history for this message
crazyserver (crazyserver) wrote :

I've got an Intel Wireless Wifi 4965AGN

It's possible that the fix of the bug of another_sam can fix this bug.

Revision history for this message
Bryan Moore (moore-bryan) wrote :

This is "confirmed;" any word on a patch or fix?

Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

Michael Nelson, thank you for reporting this and helping make Ubuntu better. Karmic reached EOL on April 30, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.10-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

affects: network-manager (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: karmic needs-kernel-logs needs-upstream-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers