I reported similar issues as bug #1172967, so I will close that one.
The upgrade from 12.10 to 13.04 was not smooth. After restarting at the
end of the process, the boot hung with a black screen. I rebooted in
failsafe mode and after enabling networking I resumed in low graphics
mode and was
Raring Ringtail on every boot (with U+1 I do a lot of boots) does not
automatically connect to WPA wireless.
Raring Beta 2 invariably disconnects on boot. Systems Settings Network says
out of range obviously tried to connect without the encryption key it already
has. Manually select drop down
25 February disconnects from wireless encrypted network on boot. That's
the latest daily build update.
Select System Settings network it says Out of range. It is not.
Select connect to hidden networks and after a delay, displays the
network, has the encryption key already, and when selected
As of 26 January build, either amd64 or i386, network manager detects
the network, sees that an encryption key is needed, and then
disconnects.
Manually connect to the hidden network, it's got the key already, click
thru the drop downs and connects fine.
Obviously the network manager needs to
As of 23 January, Raring still disconnects.
Sees the hidden wireless network.
NM reports that secrets required so it disconnects.
Then NM discovers it has the secrets i.e. the encryption password.
Does not even try to connect. Pangolin, Mint14, etc. have no problem.
Raring's NM won't connect
network out of range message from Network Manager. Same bug on Aspire 1
netbook with
Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak]
as on the Broadcom reported previously.
Network Manager sees the hidden network, knows it requires WPA key,
then tries to connect
Actually, Raring has been rebased to upstream v3.8-rc3 now. Can you
apply the latest updates and see if this bug still exists?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097002
Title:
On every
Just submitted bug 1099976 where network manager is falsely reporting
out of range.
Anyway let me see if I can try the latest upstream kernel. All these
bugs are pointing right at a network manager logic failure, but I'll try
the kernel anyway.
--
You received this bug notification because you
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097002
Title:
On every boot, raring 3.7.0-7 fails to connect to wireless
Installed latest upstream kernel I could find:
3.8.0-030800rc3-generic #201301092235 SMP Thu Jan 10 03:36:25 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
That didn't help the network manager logic bug at all, got the same
disconnect. Do note I filed a bug #1099976 where the syslog clearly
shows:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.8 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
If this bug is fixed in the
I'll give the mainline kernel a try tomorrow.
Do note, looking at the syslogs, every time the mainline kernel is asked
to authenticate by the Network Manager it does connect just fine.
The problem is, the Network Manager is not asking for the
authentication.
I'm no developer, but having
Today, raring detected the right wireless network ssid, then said out
of range.
Does NM check for hidden network encryption before issuing that message?
I'd guess not.
Did manual settings network hidden network and connected right up
since NM had all the info it needed. No problem with out of
Raring 3.8 still has problem. Here's relevant syslog entries from Acer
5253 amd64 notebook. At 15:23:45 NM decides to disconnect. At
14:23:50. I started manual connect to hidden network which went through
just fine, see the entries.
As a user since Dapper Drake Beta, why has Network Manager
So you mean the bug is present in Quantal as well? Are you sure it is
working fine in Precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097002
Title:
On every boot, raring 3.7.0-7 fails to
Yes, Quantal doesn't connect and must be manually connected through
system settings, even though it remembers the network name, encryption,
etc. When it boots up, where it should connect, it says disconnect
which does show up in the many many messages from network manager on the
syslog. Once
** Tags added: quantal regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097002
Title:
On every boot, raring 3.7.0-7 fails to connect to wireless WPA
To manage notifications about
Here's Precise. Booted up, I looked closely, there was a Disconnected
message followed shorty by Connected. Attached is syslog showing
that. All I had to do is wait a few seconds.
Raring today, there was a Disconnected and when I finally got tired of
waiting, systems settings network manager
To determine if this is a kernel or network manager issue, would it be
possible for you to try to install a kernel for precise and see if that
solves the issue?
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New =
Actually, on Quantal, I even installed a Debian kernel, upstream looked
at the result and said as soon as the kernel gets the authenticate
signal it promptly connects. As you can see from the syslogs, once the
NM gets around to issuing the authentiate, the kernel goes right ahead
and connects.
Please test with a Quantal live CD, so that we know where the regression
was introduced.
** Changed in: network-manager (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tried with an installed Quantal,
Release:12.10
Codename: quantal
Linux version 3.5.0-17-generic (buildd@allspice) (gcc version 4.7.2
(Ubuntu/Linaro 4.7.2-2ubuntu1) ) #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012
Set up wireless WPA was working fine.
Shutdown, booted, Quantal
22 matches
Mail list logo
