Mobile Broadband must be enabled after every power on, suspend, hibernate, or signal loss
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NetworkManager |
New
|
Medium
|
|||
network-manager (Ubuntu) |
Incomplete
|
Low
|
Unassigned |
Bug Description
I have auto connect set for my 3G mobile broadband connection, but at every power-on or resume from suspend or hibernate I have to re-enable mobile broadband before it will auto connect. This is made worse by bug #566812 where a disconnect can also disable the mobile broadband completely.
With 10.04 3G connections while on the move were reasonably robust and reliable, however NetworkManager under Ubuntu 11.10 is flaky and unreliable.
Chris
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: network-manager 0.9.1.90-0ubuntu4
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Sun Oct 23 06:22:33 2011
ExecutablePath: /usr/sbin/
Gconf:
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
IpRoute:
default via 10.64.64.64 dev ppp0 proto static
10.64.64.64 dev ppp0 proto kernel scope link src 122.110.2.207
169.254.0.0/16 dev ppp0 scope link metric 1000
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
ppp0 no wireless extensions.
Keyfiles: Error: [Errno 2] No such file or directory
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcEnviron: PATH=(custom, no user)
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
Oct 23 05:46:40 chris-900SD kernel: [ 346.502118] composite sync not supported
Oct 23 05:50:37 chris-900SD kernel: [ 583.457149] ACPI: EC: GPE storm detected, transactions will use polling mode
Oct 23 06:09:23 chris-900SD kernel: [ 1710.256927] composite sync not supported
Changed in network-manager: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Status changed to 'Confirmed' because the bug affects multiple users.