** Changed in: network-manager
Importance: Unknown = Medium
--
NM 0.8 not recognizing Verizon UM150 USB 3G CMDA device
https://bugs.launchpad.net/bugs/410386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
please be sure you have username/password (often just anything) and APN
set in the mobile broadband configuration.
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Incomplete
--
NM 0.8 not recognizing Verizon UM150 USB 3G CMDA device
https://bugs.launchpad.net/bugs/410386
You
Marking FixReleased as the original problem was fixed upstream and
released to Karmic as version:
0.8~a~git.20090820t182117.cb60390-0ubuntu3
tekstrider, per your comment #26, you should be able to file the re-
connect bug via apport now.
** Changed in: network-manager (Ubuntu)
Status:
** Changed in: network-manager
Status: New = Fix Released
--
NM 0.8 not recognizing Verizon UM150 USB 3G CMDA device
https://bugs.launchpad.net/bugs/410386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I can confirm the reconnect problem. To workaround, I killed modem-
manager and restarted networking. This allows the device to connect
again without the need to log out.
Should the failure to reconnect be filed as a separate bug?
--
NM 0.8 not recognizing Verizon UM150 USB 3G CMDA device
Yes, please file the re-connect problem as a separate bug, thanks!
--
NM 0.8 not recognizing Verizon UM150 USB 3G CMDA device
https://bugs.launchpad.net/bugs/410386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Oops, can't file the bug using apport since I'm using the trunk build
version from the PPA. I was under the impression it is bad form to file
a bug against a package not yet released to updates? Should I wait on
this until network-manager hits karmic updates?
--
NM 0.8 not recognizing Verizon
See also Bug 414604, which may be a duplicate of this one, and provides
detailed information. And my UM175 is most definitely NOT working with
today's updates.
--
NM 0.8 not recognizing Verizon UM150 USB 3G CMDA device
https://bugs.launchpad.net/bugs/410386
You received this bug notification
This appears to be fixed with latest build:
network-manager - 0.8~a~git.20090817t203502.3e22183-0ubuntu1~nmt2
modemmanager - 0.2.git.20090817t181641.ca767e4-0ubuntu1~nmt2
Found here:
https://edge.launchpad.net/~network-manager/+archive/trunk
CDMA modem is connecting as expected with the only
Oops spoke too soon. Problem is just different now.
--
NM 0.8 not recognizing Verizon UM150 USB 3G CMDA device
https://bugs.launchpad.net/bugs/410386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Confirmed fixed in latest builds from edge.launchpad.net as tekstr1der
said.
--
NM 0.8 not recognizing Verizon UM150 USB 3G CMDA device
https://bugs.launchpad.net/bugs/410386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
OK what happens now is that it works the first time, but if I plug it
in, connect, then disconnect and unplug it, I can no longer ever get it
working again until I reboot.
--
NM 0.8 not recognizing Verizon UM150 USB 3G CMDA device
https://bugs.launchpad.net/bugs/410386
You received this bug
Output from modem manager is attached.
This shows plugging in the modem and then clicking the connection in nm-
applet.
At the end, I have two green nm-applet bubbles with the spinner
animation going and no additional progress.
** Attachment added: output.txt
I'm seeing very similar symtoms with a UM175. I have the extra wrinkle
that if I unplug the device while NM is spinning I get a kernel panic.
nm-tool shows it in state connecting forever.
--
NM 0.8 not recognizing Verizon UM150 USB 3G CMDA device
https://bugs.launchpad.net/bugs/410386
You
Rob, the unplugging freeze/panic was reported seperately here:
https://bugs.launchpad.net/ubuntu/+source/network-manager-
applet/+bug/412605
Could you please post a log of your debug results from following these
steps:
1) Stop NetworkManager
2) run /usr/sbin/modem-manager --debug
3) Start
tekstr1der, thanks for the detailed information. I'm in the process of
reporting an upstream bug.
What are the exact steps you take to reproduce this bug?
Besides not connecting, what other visible symptoms occur? Does the
applet just spin and never connect?
** Summary changed:
-
tekstr1der, one more question...
What version of network-manager worked for you? I'm trying to determine
if you were using modem manager at all previously, or just network-
manager alone. In order to use modem manager, you would have had to be
using a version of network-manager from the modem
** Bug watch added: GNOME Bug Tracker #591748
http://bugzilla.gnome.org/show_bug.cgi?id=591748
** Also affects: network-manager via
http://bugzilla.gnome.org/show_bug.cgi?id=591748
Importance: Unknown
Status: Unknown
--
NM 0.8 not recognizing Verizon UM150 USB 3G CMDA device
** Changed in: network-manager
Status: Unknown = New
--
NM 0.8 not recognizing Verizon UM150 USB 3G CMDA device
https://bugs.launchpad.net/bugs/410386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Tony, thanks for picking this up.
The visible symptoms are the network manager applet just spins
indefinitely with both lights green. I receive an IP and DNS nameserver
information from ISP, but the connection is never fully established.
0.7.1.git.5.272c6a626-0ubuntu1 WITHOUT the modemmanager
20 matches
Mail list logo
