Mobile Broadband Fails to Configure on Ubuntu-Gnome (ZTE MF622)

[Gareth Williams]

The modem (ZTE MF622) is recognised and 'Mobile Broadband' can be enabled. The network is shown ('3' in the UK) and has signal strength bars (2 for me). However, the modem doesn't connect.

Ubuntu Desktop displays a Mobile Broadband Connection dialog/wiz

[Need (need-redhat-bugs)]

My modem is not supported by Fedora rawhide. I have installed and run usb_modeswitch. It now shows:

# lsusb
Bus 002 Device 005: ID 19d2:0031 ONDA Communication S.p.A.

I have also added a new fdi file and rebooted:

# cat /usr/share/hal/fdi/information/20thirdparty/20-zte-mf636.fdi
<!-- -*- SGML -*- -->
<deviceinfo version="0.2">
   <device>
<!-- ZTE MF636 HSDPA USB dongle -->
      <match <email address hidden>:usb.vendor_id" int="0x19d2">
         <match <email address hidden>:usb.product_id" int="0x0031">
            <match <email address hidden>:usb.interface.number" int="3">
            <append key="modem.command_sets" type="strlist">GSM-07.07</append>
            <append key="modem.command_sets" type="strlist">GSM-07.05</append>
            <append key="info.capabilities" type="strlist">modem</append>
            </match>
         </match>
      </match>
   </device>
</deviceinfo>

Unfortunately it does not seem to be detected by NetworkManager.

[Bug (bug-redhat-bugs)]

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[robledo (robledo-redhat-bugs)]

I have found that with modem ZTE MF626, F12 automatically mounts a usb-mass-storage device, and if ejected (while keeping the usb-modem connected), the modem is recognized, and connections are possible.

Pls see output in bug report
https://bugzilla.redhat.com/show_bug.cgi?id=541314

[Dan (dan-redhat-bugs)]

lsof, can you attach some 'dmesg' output from right when you plug the device in, through when it's modeswitched, through when NM fails to recognize the device? I'd like to see if it's correctly modeswitched or not.

[robledo (robledo-redhat-bugs)]

Dan, if you need output for the ZTE MF 626 (not 636), let me know. Same issue. Pls give precise instructions on how to "dmesg", however.

[Need (need-redhat-bugs)]

It's not modeswitched, I have to wrong the usb_modeswitch utility manually with a custom config file. I will post the output before and after tomorrow. Before the modeswitch the virtual cdrom is mounted.

[Need (need-redhat-bugs)]

s/wrong/run/;

[robledo (robledo-redhat-bugs)]

Created attachment 375229
dmesg output for zte mf626

attached output from dmesg > ztemf626.log, when 1) attached usb modem ZTE MF 626, 2) eject mass-storage device, leading to 3) recognition of mf 626 modem in NW, to 4) establish the 3G connection (disable wifi), and then 5) disconnect the 3G connection, and finally 6) try to reconnect the 3G connection.
hope it helps

[Need (need-redhat-bugs)]

I plug in the usb stick:

# dmesg -c
usb 2-2: new high speed USB device using ehci_hcd and address 5
usb 2-2: New USB device found, idVendor=19d2, idProduct=2000
usb 2-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0
usb 2-2: Product: ZTE CDMA Technologies MSM
usb 2-2: Manufacturer: ZTE, Incorporated
usb 2-2: configuration #1 chosen from 1 choice
scsi7 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 7:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0
sr0: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
sr 7:0:0:0: Attached scsi CD-ROM sr0
sr 7:0:0:0: Attached scsi generic sg1 type 5
ISO 9660 Extensions: Microsoft Joliet Level 1
ISOFS: changing to secondary root
SELinux: initialized (dev sr0, type iso9660), uses genfs_contexts

# lsusb
Bus 002 Device 005: ID 19d2:2000 ONDA Communication S.p.A.

# usb_modeswitch

Looking for target devices ...
 No devices in target mode or class found
Looking for default devices ...
 Found default devices (1)
Accessing device 005 on bus 002 ...
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached

Received inquiry data (detailed identification)
-------------------------
  Vendor String: ZTE
   Model String: USB SCSI CD-ROM
Revision String: 2.31
-------------------------

Device description data (identification)
-------------------------
Manufacturer: ZTE, Incorporated
     Product: ZTE CDMA Technologies MSM
  Serial No.: not provided
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x01 ...
 OK, message successfully sent
-> Run lsusb to note any changes. Bye.

# dmesg -c
scsi 7:0:0:0: rejecting I/O to dead device
usb 2-2: usbfs: process 10564 (usb_modeswitch) did not claim interface 0 before use
usb 2-2: USB disconnect, address 5
usb 2-2: new high speed USB device using ehci_hcd and address 6
usb 2-2: New USB device found, idVendor=19d2, idProduct=0031
usb 2-2: New USB device strings: Mfr=2, Product=1, SerialNumber=3
usb 2-2: Product: ZTE CDMA Technologies MSM
usb 2-2: Manufacturer: ZTE, Incorporated
usb 2-2: SerialNumber: 1234567890ABCDEF
usb 2-2: configuration #1 chosen from 1 choice
option 2-2:1.0: GSM modem (1-port) converter detected
usb 2-2: GSM modem (1-port) converter now attached to ttyUSB0
option 2-2:1.1: GSM modem (1-port) converter detected
usb 2-2: GSM modem (1-port) converter now attached to ttyUSB1
scsi8 : SCSI emulation for USB Mass Storage devices
option 2-2:1.3: GSM modem (1-port) converter detected
usb 2-2: GSM modem (1-port) converter now attached to ttyUSB2
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
option: option_instat_callback: error -71
option: option_instat_callback: error -71
option: option_instat_callback: error -71
option: option_instat_callback: error -71
usb-storage: device scan complete
scsi 8:0:0:0: Direct-Access ZTE MMC Storage 322 PQ: 0 ANSI: 2
sd 8:0:0:0...

[Dan (dan-redhat-bugs)]

Can you do the following for me?

1) service NetworkManager stop
2) killall -TERM modem-manager
3) modem-manager --debug
4) service NetworkManager start (in another window)
5) unplug and replug your device, try to reproduce the problem where the modem is not seen by NM
6) when you reproduce the problem, attach/paste the modem-manager output here and we can see what's going on with modem detection

[Need (need-redhat-bugs)]

First I deleted that custom fdi file then I rebooted and followed your instructions.

I got this:

# modem-manager --debug
** Message: Loaded plugin Generic
** Message: Loaded plugin Option
** Message: Loaded plugin Sierra
** Message: Loaded plugin MotoC
** Message: Loaded plugin Nokia
** Message: Loaded plugin Novatel
** Message: Loaded plugin ZTE
** Message: Loaded plugin Huawei
** Message: Loaded plugin Gobi
** Message: Loaded plugin Option High-Speed
** Message: Loaded plugin Ericsson MBM

I plug in the modem and nothing happens. So I run umount /media/*
Nothing happens, so I run usb_modeswitch then this happens:

** Message: (ttyUSB2) opening serial device...
** (modem-manager:2319): DEBUG: (ttyUSB2): probe requested by plugin 'ZTE'
** Message: (ttyUSB0) opening serial device...
** (modem-manager:2319): DEBUG: (ttyUSB0): probe requested by plugin 'ZTE'
** Message: (ttyUSB1) opening serial device...
** (modem-manager:2319): DEBUG: (ttyUSB1): probe requested by plugin 'ZTE'
** (modem-manager:2319): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>'
** (modem-manager:2319): DEBUG: (ttyUSB2): <-- 'AT+GCAP<CR><CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:2319): DEBUG: (ttyUSB0): --> 'AT+GCAP<CR>'

[Need (need-redhat-bugs)]

By the way with wvdial it works fine. For the init strings I use (from wvdial.conf):

Init1 = at+cfun=1
Init2 = at+cgdcont=1,"ip","PROVIDER"

[Dan (dan-redhat-bugs)]

Is that all the MM logs you have? You might want to wait 10 seconds or so for the modem to completely finish probing. If it actually never finishes, or takes a long time to finish, then we should gdb modem-manager to figure out why its hanging there.

[Need (need-redhat-bugs)]

Those are all the logs. Nothing happens unless I run usb_modeswitch (do you want me to run it?)

What do you mean when you say "try to reproduce the problem where the modem
is not seen by NM". Do you mean just plug in the modem and wait?

[Dan (dan-redhat-bugs)]

Yes, please run usb_modeswitch and report the MM logs.(In reply to comment #13)
> Those are all the logs. Nothing happens unless I run usb_modeswitch (do you
> want me to run it?)

Yes; the modem is not usable until its switched to modem mode.

> What do you mean when you say "try to reproduce the problem where the modem
> is not seen by NM". Do you mean just plug in the modem and wait?

Yeah.

[Need (need-redhat-bugs)]

Okay then to answer your question:

(In reply to comment #12)
> Is that all the MM logs you have? You might want to wait 10 seconds or so for
> the modem to completely finish probing. If it actually never finishes, or
> takes a long time to finish, then we should gdb modem-manager to figure out why
> its hanging there.

It never finishes. strace says it's doing nothing. I'll run it from within strace and post the result.

[Dan (dan-redhat-bugs)]

Ok, thanks. Basically, it looks like something in the kernel or the device is not responding or making the port hang. You should get more output from ModemManager, including messages about sending AT+GCAP to ttyUSB1. If the probe times out (it'll send 4 AT+GCAP requests to each port) then you should also see a message about "Closing serial port X" too.

[Dan (dan-redhat-bugs)]

Actually, give this a try:

Remove the line that contains '19d2' from /lib/udev/rules.d/61-option-modem-modeswitch.rules, then unplug your device, and replug it. Make sure you still have usb_modeswitch set up to flip the device to modem mode. modem-manager should then be able to use the device.

[Need (need-redhat-bugs)]

Okay I did that and reloaded the udev rules.

I got this:

** Message: Loaded plugin Ericsson MBM
** Message: (ttyUSB2) opening serial device...
** (modem-manager:9418): DEBUG: (ttyUSB2): probe requested by plugin 'ZTE'
** Message: (ttyUSB0) opening serial device...
** (modem-manager:9418): DEBUG: (ttyUSB0): probe requested by plugin 'ZTE'
** Message: (ttyUSB1) opening serial device...
** (modem-manager:9418): DEBUG: (ttyUSB1): probe requested by plugin 'ZTE'
** (modem-manager:9418): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>'
** (modem-manager:9418): DEBUG: (ttyUSB2): <-- 'AT+GCAP<CR><CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:9418): DEBUG: (ttyUSB0): --> 'AT+GCAP<CR>'
** (modem-manager:9418): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>'

Similar to before. NetworkManager doesn't seem to see the modem. I am expecting a 3G menu to appear and for me to be able to click on my connection (that doesn't happen).

Normal wvdial works.

[Dan (dan-redhat-bugs)]

(In reply to comment #18)
> Okay I did that and reloaded the udev rules.

Did you unplug/replug the ZTE device too after fixing the rules?

[Need (need-redhat-bugs)]

Yes I did.

[Dan (dan-redhat-bugs)]

Ok, kernel bugs. There's one or two fixes in the tty layer in 2.6.31.7 and 2.6.32 that could have an impact on this, so we may just have to see how 2.6.31.7 does.

[Dan (dan-redhat-bugs)]

Can you try the packages here?

http://koji.fedoraproject.org/koji/buildinfo?buildID=149089

They fix a specific issue with unresponsive serial ports that could be blocking ModemManager in your case.

[Stian (stian-redhat-bugs)]

I've been having exactly the same problem. With ModemManager-0.2.997-5.git20100101 (the build mentioned above), NetworkManager recognizes my ZTE MF636, and I can connect normally, so this bug is fixed to me.

[Need (need-redhat-bugs)]

Nothing happens unfortunately.

# modem-manager --debug
** Message: Loaded plugin Generic
** Message: Loaded plugin Option
** Message: Loaded plugin Sierra
** Message: Loaded plugin MotoC
** Message: Loaded plugin Nokia
** Message: Loaded plugin Novatel
** Message: Loaded plugin ZTE
** Message: Loaded plugin Huawei
** Message: Loaded plugin Gobi
** Message: Loaded plugin Option High-Speed
** Message: Loaded plugin Ericsson MBM
# dmesg
usb 2-2: new high speed USB device using ehci_hcd and address 2
usb 2-2: New USB device found, idVendor=19d2, idProduct=2000
usb 2-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0
usb 2-2: Product: ZTE CDMA Technologies MSM
usb 2-2: Manufacturer: ZTE, Incorporated
usb 2-2: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi4 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
CE: hpet increasing min_delta_ns to 15000 nsec
usb-storage: device scan complete
scsi 4:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0
sr0: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 4:0:0:0: Attached scsi CD-ROM sr0
sr 4:0:0:0: Attached scsi generic sg1 type 5
ISO 9660 Extensions: Microsoft Joliet Level 1
ISOFS: changing to secondary root
SELinux: initialized (dev sr0, type iso9660), uses genfs_contexts

I waited 60 seconds, nothing happened. So I ran usb_modeswitch. I got this:

** Message: Loaded plugin Ericsson MBM

** Message: (ttyUSB1) opening serial device...
** (modem-manager:19489): DEBUG: (ttyUSB1): probe requested by plugin 'ZTE'
** Message: (ttyUSB0) opening serial device...
** (modem-manager:19489): DEBUG: (ttyUSB0): probe requested by plugin 'ZTE'
** Message: (ttyUSB2) opening serial device...
** (modem-manager:19489): DEBUG: (ttyUSB2): probe requested by plugin 'ZTE'
** (modem-manager:19489): DEBUG: (ttyUSB1): --> 'ATE0+CPMS?<CR>'
** (modem-manager:19489): DEBUG: (ttyUSB1): --> 'ATE0+CPMS?<CR>'
** (modem-manager:19489): DEBUG: (ttyUSB0): --> 'ATE0+CPMS?<CR>'
** (modem-manager:19489): DEBUG: (ttyUSB2): --> 'ATE0+CPMS?<CR>'
** (modem-manager:19489): DEBUG: (ttyUSB2): <-- 'ATE0+CPMS?<CR><CR><LF>+CPMS: "SM",0,20,"SM",0,20,"ME",10,23<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:19489): DEBUG: (ttyUSB1): --> 'ATE0+CPMS?<CR>'
** (modem-manager:19489): DEBUG: (ttyUSB0): --> 'ATE0+CPMS?<CR>'
** (modem-manager:19489): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>'
** (modem-manager:19489): DEBUG: (ttyUSB2): <-- '<CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:19489): DEBUG: (ttyUSB1): --> 'ATE0+CPMS?<CR>'
** (modem-manager:19489): DEBUG: (ttyUSB0): --> 'ATE0+CPMS?<CR>'
** (modem-manager:19489): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>'
** (modem-manager:19489): DEBUG: (ttyUSB0): --> 'ATE0+CPMS?<CR>'
** Message: (ttyUSB2) closing serial device...
** (modem-manager:19489): DEBUG: (ttyUSB0): --> 'AT+GCAP<CR>'
** Message: (ZTE): GSM modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2 claimed port ttyUSB2
** (modem-manager:19489): DEBUG: Added modem /sy...

[Fedora (fedora-redhat-bugs)]

ModemManager-0.2.997-5.git20100101.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/ModemManager-0.2.997-5.git20100101.fc12

[Fedora (fedora-redhat-bugs)]

ModemManager-0.2.997-5.git20100101.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with
 su -c 'yum --enablerepo=updates-testing update ModemManager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0121

[Need (need-redhat-bugs)]

For this to work out of the box, something needs to call usb_modeswitch. Is this planned?

[Dan (dan-redhat-bugs)]

(In reply to comment #27)
> For this to work out of the box, something needs to call usb_modeswitch. Is
> this planned?

Upstream usb_modeswitch now has nicely generated udev rules files to automatically switch any known devices. So that would be handled by the usb_modeswitch package.

[Dan (dan-redhat-bugs)]

*** Bug 545638 has been marked as a duplicate of this bug. ***

[Fedora (fedora-redhat-bugs)]

ModemManager-0.3-1.git20100119.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/ModemManager-0.3-1.git20100119.fc12

[Fedora (fedora-redhat-bugs)]

ModemManager-0.3-1.git20100119.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with
 su -c 'yum --enablerepo=updates-testing update ModemManager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0847

[Jhonny (jhonny-redhat-bugs)]

OK, I just couldn't wait for modemmanager to come out as a stable update. I've updated as described in the previous comment (31), and now my GSM modem ZTE MF636 is being recognized as it should. I've only noticed that, after ejecting, it takes a little longer to become available in NetworkManager than my previous GSM modems.

As for having to "eject" the device in order to have it recognized as a modem, I don't see much of an issue in here, actually the device is also a mass-store device...

[Fedora (fedora-redhat-bugs)]

ModemManager-0.3-1.git20100119.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.

[Need (need-redhat-bugs)]

Just to add my 2 cents.. this works! But ejecting doesn't make it work, I have to run usb_modeset manually, which means it doesn't work out of the box :/

[Dan (dan-redhat-bugs)]

(In reply to comment #34)
> Just to add my 2 cents.. this works! But ejecting doesn't make it work, I have
> to run usb_modeset manually, which means it doesn't work out of the box :/

Interesting; my MF626 and MF622 work with a simple eject, but never assume that things will stay the same :) Thanks for testing!

[Alfredo (alfredo-redhat-bugs)]

I have a ZTE MF636, vedor=19d2, product=0033. It doesn't show up in NetworkManager with Fedora 12 fully up-to-date as of today (March 2nd). My vendor/product id does not show up both in /etc/usb_modeswitch or in
/lib/udev/rules.d/61-option-modem-modeswitch.rules. I set up usb_modeswitch so as to switch the device and /dev/ttyUSB0-3 appear, however NetworkManager stubbornly refuses to "see" the device whatever I do. Please note that this is a MF636 with id 0033. I would appreciate any hint, please let me know which further useful infos/logs I can provide

[Dipak (dipak-redhat-bugs)]

I am also not able to use USB modem from Huawei. It is a Huawei EC1261 HSIA device.

Following are the o/p of dmesg after device put in port

#dmesg
usb 2-2: USB disconnect, address 3
usb 2-2: new full speed USB device using uhci_hcd and address 4
usb 2-2: New USB device found, idVendor=12d1, idProduct=1446
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=4
usb 2-2: Product: HUAWEI Mobile
usb 2-2: Manufacturer: HUAÿWEI TECHNOLOGIES
usb 2-2: SerialNumber: ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
usb 2-2: configuration #1 chosen from 1 choice
scsi6 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 6:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 0
sr2: scsi-1 drive
sr 6:0:0:0: Attached scsi CD-ROM sr2
sr 6:0:0:0: Attached scsi generic sg2 type 5
ISO 9660 Extensions: Microsoft Joliet Level 1
ISOFS: changing to secondary root
SELinux: initialized (dev sr2, type iso9660), uses genfs_contexts

and o/p after #modprobe usbserial vendor=0x12d1 product=0x1446

it runs successfully and then

# wvdialconf
Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S1 S2 S3

Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?

Please read the FAQ at http://open.nit.ca/wiki/?WvDial

If you still have problems, send mail to <email address hidden>.

[Marius B. Kotsbak (mariusko)]

Please add debug logs:

https://wiki.ubuntu.com/DebuggingModemmanager

[Gareth Williams (gareththered)]

Running 'nm-connection-editor' opens the Network Connections dialog.

Selecting the Mobile Broadband tab and clicking on Add opens the New Mobile Broadband Connection wizard which allows the modem to be configured to the service provider.

After this, everything works as it should.

[Tim Lunn (darkxst)]

Are you able to configure the modem if you go to: System Settings -> Network -> add ?

[Gareth Williams (gareththered)]

Tim - the System Setting -> Network dialog is the same as the one available in the 'Network Settings' menu (top right). This shows Mobile Broadband which (until post #3 above) shows the modem as disconnected and with the 'Options...' button greyed out.

[Tim Lunn (darkxst)]

So the backend stuff is working fine (modem manager/network manager)

In which case it Looks like this bug is in gnome-control-center, gnome-shell should spawn the mobile connection wizard from the network panel, however according to comment #5, it appears not possible to configure the modem in g-c-c.

[Gareth Williams (gareththered)]

I've checked that this is not a Gnome 3 issue by running Fedora 17 in VirtualBox.

On that setup, the Network Menu has an 'Auto broadband' entry under 'Mobile broadband'. Clicking this 'Auto broadband' launches the network settings utility which launches the Mobile Broadband Configuration Wizard.

This 'Auto broadband' menu entry is in Gnome Remix, but clicking on it has no effect.

[Tim Lunn (darkxst)]

Ubuntu still has gnome-control-center 3.4, so its quite possible the bug has been fixed upstream in the last cycle.

[Marius B. Kotsbak (mariusko)]

That means the modem works fine with Unity and Gnome classic?

[Gareth Williams (gareththered)]

The modem works fine. But that was never in doubt.

The problem is that on Gnome Remix, ModemManager doesn't open the Network
Configuration application when an unconfigured modem is connected to the
system, whereas it does on Unity (and Gnome 3 on Fedora 17).

Therefore, this shouldn't be closed in my humble opinion.
On Oct 23, 2012 9:30 AM, "Marius Kotsbak" <email address hidden>
wrote:

> That means the modem works fine with Unity and Gnome classic?
>
> ** Changed in: modemmanager (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1070006
>
> Title:
> Mobile Broadband Fails to Configure on Ubuntu-Gnome (ZTE MF622)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070006/+subscriptions
>

[Tim Lunn (darkxst)]

It's not closed, just re-assigned to (hopefully) the correct package.

--
Tim

On Tuesday, 23 October 2012 at 7:37 PM, Gareth Williams wrote:

> The modem works fine. But that was never in doubt.
>
> The problem is that on Gnome Remix, ModemManager doesn't open the Network
> Configuration application when an unconfigured modem is connected to the
> system, whereas it does on Unity (and Gnome 3 on Fedora 17).
>
> Therefore, this shouldn't be closed in my humble opinion.
> On Oct 23, 2012 9:30 AM, "Marius Kotsbak" <email address hidden>
> wrote:
>
> > That means the modem works fine with Unity and Gnome classic?
> >
> > ** Changed in: modemmanager (Ubuntu)
> > Status: Incomplete => Invalid
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1070006
> >
> > Title:
> > Mobile Broadband Fails to Configure on Ubuntu-Gnome (ZTE MF622)
> >
> > To manage notifications about this bug go to:
> >
> > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070006/+subscriptions
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1070006
>
> Title:
> Mobile Broadband Fails to Configure on Ubuntu-Gnome (ZTE MF622)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070006/+subscriptions
>
>

[Stefan Thomas (justmoon)]

I have the same issue as Gareth - modem (Ericsson H5321gw) is detected, network (Swisscom) shows up in the list including signal strength. The network name has no mouse-over effect and nothing happens when clicked. The "Auto broadband" option does have the normal mouseover highlighting, but also nothing happens when clicked. In Network Settings the Options... button under Mobile Broadband is greyed out.

Release is Ubuntu 12.10 GNOME Remix x64.

[Gareth Williams (gareththered)]

Fedora 17 and Ubuntu Unity has Gnome-Control-Center 3.4 and modems work fine on those distros. This suggests that the issue is not down to the version of Gnome-Control-Center that is used.

Stefan - did you try running nm-connection-editor?

[Aleksander Morgado (aleksander-m)]

Try to run nm-connection-editor and create a mobile broadband connection setup for your provider. Once done, it should appear in the shell menu and it also may be activated.

[Sebastien Bacher (seb128)]

is that still an issue? the comment suggest it's working under unity, is the issue specific to gnome-shell?

[Daniel van Vugt (vanvugt)]

If this bug is still valid, please attach details of your system by using the following command:

apport-collect 1070006