noo not agai!
On Oct 17, 2013 12:26 PM, "Max Waterman" <
davidmaxwaterman+launch...@fastmail.co.uk> wrote:
> Just getting this starting today (or perhaps yesterday), after a bunch of
> s/w was upgrade (so that's what I blame). Quite irritating since my other
> devices on the network are fi
My fix was to switch to Debian.
On Jul 4, 2013 7:25 PM, "Vladimir Mencl" <291...@bugs.launchpad.net> wrote:
> Hi,
>
> I'm surprised how long this bug has been around. It has been affecting
> me since I installed 12.04 on a T410si ThinkPad with an RTL8191SEvB (pci
> 10ec:8172)
>
> I also get a ver
Could you post that patch if you have it available?
--
network-manager roams to (none) ((none)) - background scanning
https://bugs.launchpad.net/bugs/291760
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
This is NOT a driver issue.
This issue is a result of NetworkManager expecting wireless drivers to be
able to bgscan and be connected/responsive at the same time.
It is not a driver issue because there's probably nothing WRONG with the
driver other than NetworkManager's false expectations of what
wvengen wrote:
> Problem still exists on Lucid with BCM4322 and network-manager
> 0.8-0ubuntu3 when connecting to a Thompson TG789vn access point.
>
I'm also seeing that with BCM4322 but quite convinced this is a driver bug. I
sent a report to the support email address on this page
http://www.bro
I installed Lucid recently, on a work network with 3 other people. Every two
minutes, the network would go down for 10 seconds due to my MacBookPro 3,1's
Atheros card's background scanning. Again, I had to just install wicd.
The fact that it's broken on my system is not so bad as the fact that the
I gave up on Broadcom a long time ago, and have not been affected by this
since. I just bought an intel 3945 for 9USD on ebay, possibly this is he
best solution.
On Tue, Mar 23, 2010 at 8:09 AM, Kensan
wrote:
> This bug is still around and even further confirmation it's not the
> drivers I check
I reported a bug for my AR5418 hardware on MacBook Pro 3.1, it was marked as
a dup of this one, now MY BUG was seemingly fixed as I don't have the
symptoms anymore, yet this giant bug report still exists. Clearly, it was
incorrect to mark my bug as a dup in the first place, and now we have lost
tra
Pretty sure this problem went away with my AR5418 ath9k-using hardware a
long time ago. I think this bug report is ruined.
--
network-manager roams to (none) ((none)) - background scanning
https://bugs.launchpad.net/bugs/291760
You received this bug notification because you are a member of Ubuntu
I am experiencing similar issues on a non ath5k driver. My chipset is
Intersil ISL3890/3886.
Network Manager roams to (none)(none) every 2 minutes or so, disrupting
downloads in progress.
Also, on "busy" networks, system becomes very sluggish. Feels like the
network driver is interrupting everythi
dhd writes:
> I'm really amazed that the upstream developers are either not aware or
> don't want to fix this!
I filed a bug report. So far, it appears to have been rigorously
ignored. I'm still hoping.
--
Perry E. Metzgerpe...@piermont.com
--
network-manager roams to (none)
Steve Conklin writes:
> This doesn't appear to be a problem with any particular driver, so I'm
> removing it from kernel bugs
Well, it might still prove to be a misdesign in the kernel interface to
wireless drivers in general.
Perry
--
network-manager roams to (none) ((none))
https://bugs.l
Howard Chu writes:
> Interesting. Is that WPA with a Pre-Shared Key? I use WPA/EAP and
> obviously had the problem. Haven't tried WPA2 at all.
My bad behavior is easily reproduced on a WEP network. I think it
happens regardless of the type of encryption in use.
--
Perry E. Metzger
Hi, that behaviour appears when I use wpa2 as encryption. With wpa
only everything works fine.
Greetings
Thomas
Am 04.05.2009 um 21:26 schrieb Alexander Sack :
>>> Regardless of whether I am connected or not, when I open the NM
>>> menu to see
>>> broadcast networks, it is going to have to
Alexander Sack writes:
>> No. Opening the menu only shows you the results of the last scan,
> whenever that was. It doesn't initiate a scan.
>
> But the problem is that you cannot look in the menu to connect to a
> new AP because that list is outdated or non-existing. This feels kind
> of a regre
Alexander Jones writes:
> Regardless of whether I am connected or not, when I open the NM menu to see
> broadcast networks, it is going to have to scan then, right?
No, not necessarily.
Perry
--
network-manager roams to (none) ((none))
https://bugs.launchpad.net/bugs/291760
You received thi
Regardless of whether I am connected or not, when I open the NM menu to see
broadcast networks, it is going to have to scan then, right?
So if that scan causes me to temporarily lose connectivity, that is a bug
that needs fixing much more importantly.
On my AR5418 (ath9k) I see the message every
dhd writes:
> Thanks, that's really helpful. Maybe someone should change the title of
> the bug, then, because I'm certainly still experiencing something which
> could be described as "network-manager roams to (none) ((none))".
Yes, but it is not the same bug that everyone else is describing. I
dhd writes:
> Hi, unfortunately, this patch does not entirely fix my problem. I'm
> seeing roaming to (none) ((none)) less frequently, but it is still
> happening. Likewise I still have between 10 and 45% packet loss due to
> gratuitous roaming every 3-10 seconds. Another example:
You would s
I would suggest that people may also want to complain here:
http://bugzilla.gnome.org/show_bug.cgi?id=580185
I opened that bug report up with the gnome Bugzilla a little while ago.
Howard Chu writes:
> So despite the broad cross-section of drivers being affected, Dan
> Williams on the networkm
LuisMondesi writes:
> I got this same issue on an OQO model 02 with Jaunty
I don't see that from your dmesgs at all. At the very least, you haven't
shown us the critical dmesgs.
In any case, does applying the patch fix things for you? If not, you
have a different problem, because I'm 100% certa
OK - I've got some good news and some bad news. The good new is that I
created a usb key of Jaunty alpha 4 to test, and as far as I could tell,
the problem did not occur. My wireless connection did drop out
periodically, but that actually *did* seem like a driver issue (when it
died, it went comple
I believe it's WPA Supplicant that does the roaming, not Network
Manager.
--
network-manager roams to (none) ((none))
https://bugs.launchpad.net/bugs/291760
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
Hi,
the problem is not directly reproducible, just at certain times the
connection seems to break since the throughput heavily drops, pings
are not delivered and so on. When I then check the log, entries as
attached appear.
Ubuntu: 8.10
network-manager: 0.7~~svn20081018t105859-0ubuntu1
cat /etc/n
24 matches
Mail list logo
