It ceased to be a problem for me when I gave up on Ubuntu (again) and
went back to Debian. This was about a year ago now.
zw
On 10/4/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
> network-manager has come a long way since you posted your bug. Its most
> likely fixed. If its not fixed in latest
network-manager has come a long way since you posted your bug. Its most
likely fixed. If its not fixed in latest gutsy network-manager for you,
feel free to reopen it.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Fix Released
--
flaky association with wireless access poin
to grab the latest Gutsy Desktop cd please visit
http://cdimage.ubuntu.com/daily/current/
--
flaky association with wireless access points
https://bugs.launchpad.net/bugs/64931
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
Thank you for your bug report.
Can you please test if your bug is still present in gutsy by using the latest
gutsy livecd.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
flaky association with wireless access points
https://bugs.launchpad.net/bugs/64931
You receive
I should probably mention in this bug too that I have gone back to
Debian on this laptop - the last straw, in fact, was that the wireless
card didn't work AT ALL in feisty (the madwifi in feisty was
incompatible with the 2.6.20 kernel). I miss working suspend-to-disk,
but I need reliable wireless
I'm trying out fiesty beta on my laptop with PCMCIA wireless (using
NDISwrapper and a solid XP driver) and the wireless seems alot more
flaky than Edgy used to.
I use several wireless access points and whenever I go from one to the
other, I have to unplug my PCMCIA card, plug it in again, go to th
Yes, I can do that, no problem.
--
flaky association with wireless access points
https://launchpad.net/bugs/64931
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
It appears to be trying to migrate to the "better" network connection.
This is a good candidate for forwarding upstream.
Will you be able to test any custom patches or versions that end up
resulting from trying to fix this bug?
--
flaky association with wireless access points
https://launchpad.n
I guess I have to make two comments to add two attachments...
** Attachment added: "lspci -v"
http://librarian.launchpad.net/4810642/lspci-v.txt
--
flaky association with wireless access points
https://launchpad.net/bugs/64931
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Here you go.
** Attachment added: "lshal output"
http://librarian.launchpad.net/4810641/lshal.txt
--
flaky association with wireless access points
https://launchpad.net/bugs/64931
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Can you also attach the results from an "lshal" and "lspci -v"?
--
flaky association with wireless access points
https://launchpad.net/bugs/64931
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Here's /var/log/daemon.log from the problem system, which is basically
all network-manager logs. There is definitely a failure to associate
with SSID 'njs2' somewhere in here, and I believe there are some
failures to associate with 'UCSD' too.
** Attachment added: "n-m logfile"
http://libraria
whups, this got filed against acpi by mistake.
** Changed in: acpi (Ubuntu)
Sourcepackagename: acpi => network-manager
--
flaky association with wireless access points
https://launchpad.net/bugs/64931
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
13 matches
Mail list logo
