Description of problem:
Clicking on Network settings from the taskbar and then on the options button in the Mobile Broadband page does not open any other dialog.
Version-Release number of selected component (if applicable):
Fedora 15 Beta Live CD x86_64
Steps to Reproduce:
1. Plugin any Mobile Broadband device recognised by Fedora. You should see "attached to ttyUSB0" etc in dmesg | tail. Also /var/log/messages will say that the port will now be used by NetworkManager.
2. Open Network Settings from the taskbar and goto Mobile Broadband page. Click on options. Nothing happens !
An options dialog/window should open.
Options dialog/window does not open.
To connect by Wireless USB Broadband stick (Manufacturer : Huawei, Service Provider : Reliance, Country : India) I had to do it via the old network manager settings pane (that available in fedora 14). Just press super(windows logo) and type net. There are 2 results; the first is the new network manager (gnome3), the second is network connections. From the network connections, I could add a new connection, enter username password etc and then connect to the internet.
This bug also occurs for Fedora-15-Beta-i686-Live-Desktop running as a Live CD.
Wireless USB Broadband stick:
Service Provider: Virgin Mobile USA (Sprint CDMA 3G Network)
Tried Elison Niven's work around for setting up a Mobile Broadband connection. Doing that allowed me to set up a connection but I could not establish a connection.
Instead, I was able to make a connection after setting up the files /etc/wvdial.conf and /etc/resolv.conf and then executing wvdial from a terminal window.
The same happens in a freshly updated Fedora 15 system.
I successfuly connected after setting up connection through nm-connection-editor.
Bus 001 Device 009: ID 12d1:1406 Huawei Technologies Co., Ltd.
The modem is correctly enabled and automatically registered in the network: a new list item "Orange@" (in my case) is added after the ModemManager switch in the NM applet.
But then there is no way to tell NM to really connect to that network, as that newly created list item is not clickable.
As Pavel said, creating a new broadband connection setup with nm-connection-editor solved the issue. Once created the new connection, it is shown in the NM applet after the non-clickable one, but the new one is really clickable and will make the modem connect.
This is kind of an important bug I would say, it's completely preventing normal usage of broadband modems.
Thanks Aleksander for a more precise description than I provided.
Yep, the important point is when the network information shows up but is not clickable and thus not connectable.
I cannot guess what was the autors' intention. But that also means the current system is not intuitive at all, otherwise it should be easy tu guess what & how to do.
I can reproduce this.
The following patches implement the missing bits for Mobile Broadband in control-center. Namely, Options button opens the connection (when it's active) in editor the same way Wired, etc do. Also, On/Off switch is implemented and displaying info is fixed.
The main issue of the bug is not addressed, though. If there is no connection present for Mobile Broadband, then Options button is disabled.
The issue should be probably solved by applet that should create a connection when mobile network entry is clicked.
Created attachment 496724 [details]
network: fix On/Off switch, Options button and info for Mobile Broadband
Created attachment 496725 [details]
network: fix displaying IP info to work also for static and PPP configurations
This fixes displaying IPv4 stuff for static configurations (no DHCP) and also for Mobile Broadband.
*** Bug 698975 has been marked as a duplicate of this bug. ***
Have a same problem with Nokia 6120c
Although everything worked automatically, that is the mobile connection was created and clickable after the provider dialog, the open button still does not work so I could enter the DNS addresses. I did set it via nm-connection-editor
Hello, in my case the mobile broadband device is not recognized at all..
Bus 002 Device 006: ID 12d1:14c5 Huawei Technologies Co., Ltd.
and the model is Vodafone Italy branded, Huawei model K4510
In messages I only have:
Jul 21 12:43:58 ope46 kernel: [16547.477255] usb 2-2: new high speed USB device using ehci_hcd and address 6
Jul 21 12:43:58 ope46 kernel: [16547.593683] usb 2-2: New USB device found, idVendor=12d1, idProduct=14c5
Jul 21 12:43:58 ope46 kernel: [16547.593693] usb 2-2: New USB device strings: Mfr=3, Product=2, SerialNumber=0
Jul 21 12:43:58 ope46 kernel: [16547.593701] usb 2-2: Product: Vodafone Mobile Broadband (Huawei)
Jul 21 12:43:58 ope46 kernel: [16547.593707] usb 2-2: Manufacturer: Vodafone Group (Huawei)
Jul 21 12:43:58 ope46 kernel: [16547.641512] scsi7 : usb-storage 2-2:1.0
Jul 21 12:43:58 ope46 kernel: [16547.641806] scsi8 : usb-storage 2-2:1.1
Jul 21 12:43:58 ope46 mtp-probe: checking bus 2, device 6: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2"
Jul 21 12:43:58 ope46 mtp-probe: bus: 2, device: 6 was not an MTP device
Jul 21 12:43:59 ope46 kernel: [16548.642297] scsi 7:0:0:0: CD-ROM Vodafone CD ROM (Huawei) 2.31 PQ: 0 ANSI: 2
Jul 21 12:43:59 ope46 kernel: [16548.642787] scsi 8:0:0:0: Direct-Access Vodafone Storage (Huawei) 2.31 PQ: 0 ANSI: 2
Jul 21 12:43:59 ope46 kernel: [16548.646295] sr1: scsi-1 drive
Jul 21 12:43:59 ope46 kernel: [16548.648785] sr 7:0:0:0: Attached scsi generic sg2 type 5
Jul 21 12:43:59 ope46 kernel: [16548.650423] sd 8:0:0:0: Attached scsi generic sg3 type 0
Jul 21 12:43:59 ope46 kernel: [16548.653172] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[16547.477255] usb 2-2: new high speed USB device using ehci_hcd and address 6
[16547.593683] usb 2-2: New USB device found, idVendor=12d1, idProduct=14c5
[16547.593693] usb 2-2: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[16547.593701] usb 2-2: Product: Vodafone Mobile Broadband (Huawei)
[16547.593707] usb 2-2: Manufacturer: Vodafone Group (Huawei)
[16547.641512] scsi7 : usb-storage 2-2:1.0
[16547.641806] scsi8 : usb-storage 2-2:1.1
[16548.642297] scsi 7:0:0:0: CD-ROM Vodafone CD ROM (Huawei) 2.31 PQ: 0 ANSI: 2
[16548.642787] scsi 8:0:0:0: Direct-Access Vodafone Storage (Huawei) 2.31 PQ: 0 ANSI: 2
[16548.646295] sr1: scsi-1 drive
[16548.648383] sr 7:0:0:0: Attached scsi CD-ROM sr1
[16548.648785] sr 7:0:0:0: Attached scsi generic sg2 type 5
[16548.650423] sd 8:0:0:0: Attached scsi generic sg3 type 0
[16548.653172] sd 8:0:0:0: [sdb] Attached SCSI removable disk
I don't see anything about broadband in network settings taskbar and if I run
nm-connection-editor I have to stop in the window when you choose the device, because no device seems to be detected...
I have at this time:
Do I have to file a different bug, or can I stick to this?
Gianluca that is a different bug. I would suggest filing it against usb_modeswitch. You should google and see if your device is allready supported by upstream.
Created attachment 514689 [details]
network: fix displaying IP info to work also for static and PPP configurations
This fixes displaying IPv4 stuff for static configurations (no DHCP) and also
for Mobile Broadband.
[updated to apply cleanly on current master]
Patches (comment #7 and comment #14) committed upstream. See https://bugzilla.gnome.org/show_bug.cgi?id=657303
This bugreport is pretty old, patches upstream, older Fedora release. Worth closing?
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: