GNOME Bugzilla – Bug 647553
can't close BT DUN connection
Last modified: 2013-01-03 01:00:44 UTC
While it properly shows that it's connected (with the mobile phone icon), selecting the 'off' switch in mobile broadband didn't work; while it sets the mobile broadband switch to off/on, it has no effect on the connection. I had to drop the connection with nmcli. No errors in .xsession-errors. gnome-shell-3.0.0.1-1.fc15.x86_64
Differently from, say, wired section, turning off the Mobile Broadband switch changes the global NetworkManager setting "enable-wwan". The fact that this has no effect at all is not a bug in the shell, and it's also a duplicate, although I don't remember the bug number.
>The fact that this has no effect at all is not a bug in the shell Except that it arguably is, since (assuming it worked as intended) I still have no way to disable my internal 3G modem without disabling my bluetooth DUN connection, or vice versa. Do you have a reference to the bug you mentioned above?
(In reply to comment #2) > >The fact that this has no effect at all is not a bug in the shell > > Except that it arguably is, since (assuming it worked as intended) I still have > no way to disable my internal 3G modem without disabling my bluetooth DUN > connection, or vice versa. That's a different bug. You should see three switches: one master, next to "Mobile Broadband", similar to the physical rf killswitch, and one for each device, next to its name (except that the name of Bluetooth devices is currently empty - I have a patch for that somewhere). > Do you have a reference to the bug you mentioned above? Bug 616285 has a similar issue (although with the older applet). See also bug 640578.
>That's a different bug. You should see three switches: one master, next to >"Mobile Broadband", similar to the physical rf killswitch, and one for each >device, next to its name (except that the name of Bluetooth devices is >currently empty - I have a patch for that somewhere). I see the master switch next to "Mobile Broadband", but this has no effect on my bluetooth connection (which is grouped suggestively under this master switch). I also have a built in 3G modem; I believe the "Mobile Broadband" switch affects this, but will need to double check. I'm not seeing any switch next to the device name. Is this perhaps an upstream feature I'm missing out on? I'm using gnome-shell-3.2.1-2.fc16.x86_64.
(In reply to comment #4) > >That's a different bug. You should see three switches: one master, next to > >"Mobile Broadband", similar to the physical rf killswitch, and one for each > >device, next to its name (except that the name of Bluetooth devices is > >currently empty - I have a patch for that somewhere). > > I see the master switch next to "Mobile Broadband", but this has no effect on > my bluetooth connection (which is grouped suggestively under this master > switch). I also have a built in 3G modem; I believe the "Mobile Broadband" > switch affects this, but will need to double check. If the switch affects the internal 3G modem, but not a bluetooth DUN, I would call it a NetworkManager bug. Would you please file it, including also the output of "nmcli nm", before and after toggling the master switch. > I'm not seeing any switch next to the device name. Is this perhaps an upstream > feature I'm missing out on? I'm using gnome-shell-3.2.1-2.fc16.x86_64. There is a bug that makes the bluetooth device name empty (patch pending review somewhere), but there should definitely be a switch, and I'm seeing it....
Created attachment 201786 [details] NetworkManager screenshot with BT DUN device connected
(In reply to comment #5) > If the switch affects the internal 3G modem, but not a bluetooth DUN, I would > call it a NetworkManager bug. Would you please file it, including also the > output of "nmcli nm", before and after toggling the master switch. Will do... > > I'm not seeing any switch next to the device name. Is this perhaps an upstream > > feature I'm missing out on? I'm using gnome-shell-3.2.1-2.fc16.x86_64. > > There is a bug that makes the bluetooth device name empty (patch pending review > somewhere), but there should definitely be a switch, and I'm seeing it.... I'm not sure if we're misunderstanding each other or if something is actually missing from my NetworkManager applet, but see the screenshot in comment #6 for clarification. Note that my "Mobile Broadband" is switched off, yet I am posting this from my bluetooth DUN connection.
Created attachment 201992 [details] NetworkManager screenshot with Gobi 3G internal modem activated
I have added another screenshot (comment #8) of NetworkManager with my internal 3G modem enabled. I assume that the switch which has no label to the left of it is the bug you mentioned in comment #5, but it's not entirely clear what all of the switches and labels are for: - Does/should the 'Mobile Broadband' switch affect both my internal 3G connection *and* my BT DUN connection? - What is the 'Auto broadband' label for? - What *is* that unlabelled switch supposed to toggle? - Why is there no such switch for my BT DUN (3 Mobiltelefon) device? I will have a play around with the switches once I get a chance, however my system froze while trying to connect with the Gobi on my last attempt. Also, could we perhaps move this bug to 3.2.x? It's still relevant.
Sorry that I didn't reply earlier. In any case... - Yes, the mobile broadband switch should affect any 3G connection that are initiated by the computer. This includes internal 3G, 3G usb keys and bluetooth DUN. This should not include tethered connections, via wifi, usb or bluetooth PAN. - "Auto broadband" is the name of the automatic connection that is added for a device you never used (and thus has no connection configured). By clicking it, you should be able to activate the associated device (in this case, the internal 3G modem). I agree it could be named better - in gnome 2 days, it was "Configure mobile broadband..." - The unlabelled switch is associated with the active connection on your bluetooth device. Bugs aside, design has the bluetooth device name there. - There is, it is the unlabeled one.
Created attachment 206882 [details] Left: Internal 3G enabled. Right: Internal 3G disabled >- Yes, the mobile broadband switch should affect any 3G connection that are >initiated by the computer. This includes internal 3G, 3G usb keys and bluetooth >DUN. This should not include tethered connections, via wifi, usb or bluetooth >PAN. This switch does not affect my bluetooth DUN connection ("3 Mobiltelefon"). >- "Auto broadband" is the name of the automatic connection that is added for a >device you never used (and thus has no connection configured). By clicking it, >you should be able to activate the associated device (in this case, the >internal 3G modem). I agree it could be named better - in gnome 2 days, it was >"Configure mobile broadband..." Agree that this should be named better, but once it is configured it reads okay. >- The unlabelled switch is associated with the active connection on your >bluetooth device. Bugs aside, design has the bluetooth device name there. >- There is, it is the unlabeled one. See attached image. On the left (with my internal 3G modem enabled), I have this switch available. All bugs regarding label position aside, this works as it should. On the right, without my internal 3G modem enabled (i.e. disabled at udev level), I have no such switch and therefore can't disconnect this connection since, as I said above, the "mobile broadband" switch does not affect this connection. There are a number of problems with label/switch positioning/grouping, especially when my internal 3G modem is connected, however I will keep the discussion relevant to this particular bug for now.
If the device specific switch works, then the gnome-shell part is working. The fact that the global "enable-wwan" setting does not affect bluetooth DUN is definitely a NetworkManager bug. Reassigning.
(In reply to comment #12) > If the device specific switch works, then the gnome-shell part is working. > The fact that the global "enable-wwan" setting does not affect bluetooth DUN is > definitely a NetworkManager bug. > Reassigning. But surely the fact that the connection-specific switch does not show up (unless I have an internal 3G connection available) is a gnome-shell bug?
(In reply to comment #13) > (In reply to comment #12) > > If the device specific switch works, then the gnome-shell part is working. > > The fact that the global "enable-wwan" setting does not affect bluetooth DUN is > > definitely a NetworkManager bug. > > Reassigning. > > But surely the fact that the connection-specific switch does not show up > (unless I have an internal 3G connection available) is a gnome-shell bug? No, it's part of the design, the specifics of what connection is used or how it is implemented should not exposed, and all the user decides is "3g yes or no?".
(In reply to comment #14) > No, it's part of the design, the specifics of what connection is used or how it > is implemented should not exposed, and all the user decides is "3g yes or no?". Sorry if this seems pedantic, but I'm trying to understand the design principles here and failing. If all the user decides is "3g yes or no", why am I being presented with a connection-specific switch for my DUN connection at all, ever? It's inconsistent that it's there some times (albeit misaligned) and others not, but according to your above comment we should just be using the "Mobile broadband" master switch to disable/enable DUN connections anyway?
Created attachment 206955 [details] Comparison of mobile broadband switch states For the NM folk - comparison of the NM GUI and output of 'nmcli nm' with BT DUN connection enabled, before and after switching off "Mobile broadband".
(In reply to comment #16) > Created an attachment (id=206955) [details] > Comparison of mobile broadband switch states > > For the NM folk - comparison of the NM GUI and output of 'nmcli nm' with BT DUN > connection enabled, before and after switching off "Mobile broadband". Also note in the screenshot that the signal strength for my internal 3G connection ("Tele2") is displayed, even though my internal 3G modem ("Qualcomm Gobi 2000") is supposedly switched off.
(In reply to comment #15) > (In reply to comment #14) > > No, it's part of the design, the specifics of what connection is used or how it > > is implemented should not exposed, and all the user decides is "3g yes or no?". > > Sorry if this seems pedantic, but I'm trying to understand the design > principles here and failing. If all the user decides is "3g yes or no", why am > I being presented with a connection-specific switch for my DUN connection at > all, ever? It's inconsistent that it's there some times (albeit misaligned) and > others not, but according to your above comment we should just be using the > "Mobile broadband" master switch to disable/enable DUN connections anyway? Yes. In fact, in the common case, there is one 3G device, and all you see is one switch that does the Right Thing. Clearly, if you have more than one, you could need to enable each of them separately, hence the connection-specific switch. The behaviour is similar to wifi, where you have one master switch, and one switch for each device, but normally see only the master one. (In reply to comment #17) > (In reply to comment #16) > > Created an attachment (id=206955) [details] [details] > > Comparison of mobile broadband switch states > > > > For the NM folk - comparison of the NM GUI and output of 'nmcli nm' with BT DUN > > connection enabled, before and after switching off "Mobile broadband". > > Also note in the screenshot that the signal strength for my internal 3G > connection ("Tele2") is displayed, even though my internal 3G modem ("Qualcomm > Gobi 2000") is supposedly switched off. Technically, the modem is enabled and disconnected, not disabled, as long as you have the master switch to on. gnome-shell has no control on the enabled state of the modem (which is controlled by modemmanager, not networkmanager), and that switch only affects data connections, not sms or voice. You may notice that disabling master hides the signal strength though, as that effectly switches off the modem at the hardware level (it's meant to be a software airport mode).
(In reply to comment #18) > Yes. In fact, in the common case, there is one 3G device, and all you see is > one switch that does the Right Thing. Clearly, if you have more than one, you > could need to enable each of them separately, hence the connection-specific > switch. The behaviour is similar to wifi, where you have one master switch, and > one switch for each device, but normally see only the master one. Okay, I guess this makes more sense now that I understand the thought behind it. However, IMHO there could be a better distinction made between the master ("Mobile broadband") label and the internal 3G device ("Qualcomm Gobi 2000"), since they currently look the same. I think this is what was confusing me most. Anyway I'll keep the discussion to the functionality of the "Mobile broadband" switch for this bug now - is there a separate bug already for the label positioning of the BT DUN connection?
I'm marking this a duplicate of a newer bug dealing with a redesign of the 3G section of the network menu. It should fix this and other bugs. *** This bug has been marked as a duplicate of bug 658230 ***