My wireless connection died when I updated to the latest F15 NetworkManager, and I can't get it working again with that version. I connect to a hidden wireless network using wpa-psk. This is with NetworkManager-0.8.997-4.git20110325.fc15.x86_64 I have forced a downgrade to NetworkManager-0.8.2-8.git20101117.fc15.x86_64 (which I fortunately still had RPMs for) and wireless works again for that version.
For Beta blocker consideration: Relevant criterion are Alpha "It must be possible to run the default web browser and a terminal application from the default desktop environment. The web browser must be able to download files, load extensions, and log into FAS" and "The installed system must be able to download and install updates with yum and PackageKit" - both imply a functional network connection. Question here is does this affect all hidden networks, and if so, is that enough configurations for us to consider it a blocker.
I'm not seeing my hidden wireless network either. NetworkManager-0.8.997-7.git20110330.fc15.x86_64
Discussed at the 2011-04-01 blocker bug meeting. Accepted as beta blocker.
(In reply to comment #3) > Discussed at the 2011-04-01 blocker bug meeting. Accepted as beta blocker. Hits Alpha release requirement: It must be possible to run the default web browser and a terminal application from the default desktop environment. No fix proposed yet or additional information asked for. Waiting for devel response.
While we don't have any knob in the ui for it yet, here is a workaround for connecting to hidden aps: gdbus call --session --dest org.gnome.network_manager_applet --object-path /org/gnome/network_manager_applet --method org.gnome.network_manager_applet.ConnectToHiddenNetwork
See https://bugzilla.gnome.org/show_bug.cgi?id=645002
Cool, good to know this is being worked on.
control-center-3.0.0.1-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/control-center-3.0.0.1-2.fc15
Package control-center-3.0.0.1-2.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing control-center-3.0.0.1-2.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/control-center-3.0.0.1-2.fc15 then log in and leave karma (feedback).
Tested with the following setup: - F15 Beta RC1 x86_64 live (control-center-3.0.0.0.1-2.fc15) - 802.11g wireless network (hidden SSID, WPA/WPA2) - Intel Ultimate-N 6300 I am not able to connect to the hidden wireless network. A network named '<unknown>' shows up in the "system tray" network manager icon in the upper right of gnome-shell, but there is no apparent option of connecting to a wireless network with hidden SSID from that menu. If I go into the network settings, I am able to select 'Other...' as a wireless network. If I enter in my hidden wireless network name and WPA secret, both the wired and wireless networking devices disappear from the control panel and the network manager icon disappears from the upper right of gnome-shell. If I exit and reopen the network settings, my wireless and wired devices re-appear and so does the network manager system tray icon. This setup has no issues connecting to the wireless network when the SSID is not hidden.
does it work if you use the gdbus workaround in comment #5? everything 'disappearing' sounds like NM crashed at that point; do you get an abrt crash alert?
on blockeriness of this: i would probably be okay with downgrading it to NTH if the gdbus workaround and/or using nm-connection-editor do the job, those are both pretty usable workarounds we can easily document.
(In reply to comment #10) > I am not able to connect to the hidden wireless network. Owen suggested on #fedora-desktop that this feature wasn't planned and won't be ready for F-15-Beta. I was surprised when early support landed. Unfortunately, tflinks' testing shows it may not be up-to-speed yet. tflink: Owen suggested a possible workaround of using starting nm-connection-editor and specifying the hidden wireless network details manually. I think that might be worth exploring if you are still able to test. Thanks!
(In reply to comment #12) > on blockeriness of this: i would probably be okay with downgrading it to NTH if > the gdbus workaround and/or using nm-connection-editor do the job, those are > both pretty usable workarounds we can easily document. Agreed. Given that upstream is planning to resolve this post beta, it seems our only options are slip for an undetermined period of time, or document "reasonable" workarounds.
(In reply to comment #11) > does it work if you use the gdbus workaround in comment #5? everything > 'disappearing' sounds like NM crashed at that point; do you get an abrt crash > alert? The workaround from comment #5 brings up the same menu that I can get to from the network settings control panel. NetworkManager is indeed crashing, nothing shows up in ABRT, though. Will attach the system logs that show the crash.
Created attachment 490862 [details] System logs from NetworkManager crash when trying to connect to a wireless network with hidden SSID Attaching system logs from NetworkManager crash. Nothing shows up in ABRT, though.
(In reply to comment #13) > tflink: Owen suggested a possible workaround of using starting > nm-connection-editor and specifying the hidden wireless network details > manually. I think that might be worth exploring if you are still able to test. > Thanks! This does work on my system. I am able to connect to the hidden wireless network and use it.
ah - NM runs as root, so you'd only see the crash if you ran abrt-gui as root. So, there's a definite bug here, but we do have what looks like a usable workaround too. I guess if we could get a quick fix for NM that would be good? Dan?
do we have any other +1 / -1 votes to downgrading this to NTH?
(In reply to comment #19) > do we have any other +1 / -1 votes to downgrading this to NTH? I'm +1 on downgrading to NTH. The workaround isn't painful and does work as long as we write it down somewhere :)
(In reply to comment #19) > do we have any other +1 / -1 votes to downgrading this to NTH? The workaround seems reasonable and documentable.
(In reply to comment #21) > (In reply to comment #19) > > do we have any other +1 / -1 votes to downgrading this to NTH? > > The workaround seems reasonable and documentable. That was supposed to be a +1 :)
okay, so we have a consensus on downgrading this (dgilmore is also good with it). so dropping this to NTH. We will have to document the workaround if we don't wind up spinning an RC3 and fixing this.
Package control-center-3.0.0.1-3.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing control-center-3.0.0.1-3.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/control-center-3.0.0.1-3.fc15 then log in and leave karma (feedback).
control-center-3.0.0.1-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
I am reopening this bug as control-center-3.0.0.1-3.fc15 provides a workaround rather than fixing the regression of the "Hidden wireless network" going missing from the network applet - the F14 applet would auto-connect as well if suitably configured but I haven't seen the current one do this. At the very least the workaround should be clearly documented - step by step - because it isn't obvious how to get from the applet to connecting to a hidden network and is a 4 stage process which people could easily get confused.
I don't find a way to delete configured networks through control-center, is there any method to do it? NM creates a new Connection when you try to connect to a wireless network, so my hidden network never gets connected automatically because it tries to connect to some others networks I have used before. I want to delete these networks, but I don't find the way to do it. If I want to connect to my hidden network, I must go to Control Center, select wireless, expand the connections dropbox, select the last entry (Others), select my hidden network AP and wait to get connected. These steps every time I turn on my computer... It could be a lot of easier if you could go directly to Hidden networks as you can do on Gnome 2.30 NM Applet.
(In reply to comment #27) > I don't find a way to delete configured networks through control-center, is > there any method to do it? Try using nm-connection-editor as a workaround for now.
Thanks James!!
*** Bug 697891 has been marked as a duplicate of this bug. ***
Just installed the released f15 (no updates loaded yet since I've been trying to get the network to function :-). I have this same problem which I got around for now by turning back on SSID broadcast in my router. When I tried the Ubuntu 11.04 live USB on this same hardware, the network app looked very similar, but had a "Connect to hidden network..." item at the bottom of the list of potential wireless networks. It popped up a place where I could type the SSID and passphrase and then worked perfectly. (Ubuntu also already had the broadcom driver I had to fetch from rpmfusion :-). Don't know how much code is shared between the NM versions, but the Ubuntu approach to this looked pretty good to me.
Ubuntu uses a older version of NM. NM 0.9 was a rewrite and Fedora 15 uses in part because of integration with GNOME Shell. However the Shell UI doesn't support all of the functionality yet. Using nm-connection-editor is a workaround till the point the missing features are adding back. Other than that, NM is just 99% the same across distros having the same versions.
in final F15, there's an Other... option in the network list in Network Settings which should let you connect to a hidden network. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
(In reply to comment #33) > in final F15, there's an Other... option in the network list in Network > Settings which should let you connect to a hidden network. > > > > -- > Fedora Bugzappers volunteer triage team > https://fedoraproject.org/wiki/BugZappers Yes, but Does it auto connecto to hidden networks? Every time I turn on my computer, I must go to Network Settings -> Others -> Select my hidden network... Will it change on F15 final?
I didn't notice an "Other..." option in my list, maybe I missed it. Anyway, it was simpler just to start broadcasting my SSID again :-).
tom: it's not in the list in the Shell 'panel applet', only the control center applet (which you can get to by clicking Network Settings in the Shell applet). doesn't seem like a great design to me either, before you ask =) -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I also encountered the same situation yesterday on new installation of Fedora 15 (fully updated). Each time I rebooted I would have to recreate my hidden wireless information. I enabled broadcasting on wireless AP and connection is found automatically on reboot. Basically, I am just confirming the bug again.
I can confirm the problem on an updated F14 (using preupgrade). It had stored the credentials but after reboot it refuses to connect to my hidden SSID. gdbus call --session --dest org.gnome.network_manager_applet --object-path /org/gnome/network_manager_applet --method org.gnome.network_manager_applet.ConnectToHiddenNetwork Is the only way to get around it, and there I can select the stored settings from the list and it works.
Is this not a duplicate of Bugs 516788 & 448437? If so, this bug has been around since F9... Can't someone at Redhat (Dan Williams?) extract their digit? My workaround (that worked in F12/14, see comment 35 of Bug 448437) appears not to work for F15 :o(
(In reply to comment #39) > Is this not a duplicate of Bugs 516788 & 448437? > > If so, this bug has been around since F9... Can't someone at Redhat (Dan > Williams?) extract their digit? > > My workaround (that worked in F12/14, see comment 35 of Bug 448437) appears not > to work for F15 :o( No, you have an additional problem. Do any of the workarounds given in this bug help you?
(In reply to comment #39) > Is this not a duplicate of Bugs 516788 & 448437? > > If so, this bug has been around since F9... Can't someone at Redhat (Dan > Williams?) extract their digit? > > My workaround (that worked in F12/14, see comment 35 of Bug 448437) appears not > to work for F15 :o( What this bug is about seems to be there's no knob for connecting to hidden networks in gnome-shell applet. So, maybe we should reassign it to the gnome-shell and edit the title accordingly. Mike, the bug you are experiencing is "NM doesn't *automatically* connect to a hidden network". That is addressed in bug 707406.
(In reply to comment #41) > (In reply to comment #39) > > Is this not a duplicate of Bugs 516788 & 448437? > > > > If so, this bug has been around since F9... Can't someone at Redhat (Dan > > Williams?) extract their digit? > > > > My workaround (that worked in F12/14, see comment 35 of Bug 448437) appears not > > to work for F15 :o( > > What this bug is about seems to be there's no knob for connecting to hidden > networks in gnome-shell applet. So, maybe we should reassign it to the > gnome-shell and edit the title accordingly. Yes, though this bug pre-dates the control-center fix that allowed the connection to be made at all except by manually typing a command. > Mike, the bug you are experiencing is "NM doesn't *automatically* connect to a > hidden network". That is addressed in bug 707406. I had assumed the applet was still provided by NetworkManager. Reassigning to gnome-shell.
There is not going to be a 'know for connecting to hidden networks' in gnome-shell, so reassigning the bug there is not going to help...
The easiest and fastest solution in my opinion is to list the hidden networks added via the Other option with all the not hidden wireless network on the applet. Maybe the icon shown on the applet for manually configured hidden networks could represent that is a hidden network (as the lock that the applet shows with protected networks).
matthias: why not? it seems oddly byzantine to force people to go into the the control center applet to find the special list of wireless networks which has the 'More...' entry that lets you connect to a hidden network. Why is it better design to have two different lists of wireless networks for the Shell 'applet' and the control center applet, with the one that's more obscure being more useful?
Because the shell menu needs most of all to be simple and quick to use. It is is already bordering on too complicated for a menu. We don't want to repeat all the mistakes of the nm-applet do-it-all-from-the-statusicon UI here...
I can see that concern, but still, the workflow for connecting to a hidden network is now pretty convoluted, especially if you're used to the existing one. So you look at the SSID list and the entry you expect to see is gone; even if you now figure out 'hmm, maybe I should go to Network Settings and look for something there', it's pretty counter-intuitive to then look at the SSID list in the Network Settings applet - it seems unlikely that people will expect it to be different. They'd probably be looking for something else.
Matthias, could the applet show your configured hidden networks on the SSID list with the visible ones? The applet remains as simple as it is now and the hidden networks users don't need to go through 3 or 4 screens to get connected.
FWIW, I agree with Juan (Comment 48). The current setup is a PITA for connecting to pre-configured hidden networks. Clean menus are all well and good, but I want to be able to connect to my pre-configured WLAN at home without having to go through 3/4 steps every time. I'd like my FC15 laptop to automatically connect to the default wireless network (hidden or not), but that seems too much to ask in FC15 (unlike FC14 and earlier where it all worked beautifully....)
I also agree. a) There should be no more than 2 or 3 hidden networks configured in a normal setup. So it would not clutter the list. b) Even if there were more, this makes it even more imperative to have them easily accessible. Moreover, I suggest to mark them, so that the user knows that they may not be available. For instance, they could have a special icon (an eye with a cross on top comes to mind) or have them slightly grayed out in some way. As soon as the SSID is verified to be available, it would change to the normal mode. The user would readily understand the message, since he configured it himself.
(In reply to comment #22) > (In reply to comment #21) > > (In reply to comment #19) > > > do we have any other +1 / -1 votes to downgrading this to NTH? > > > > The workaround seems reasonable and documentable. > > That was supposed to be a +1 :) The workaround does not work for me. This is a regression from F14 anyway - workarounds should not be needed.
(In reply to comment #5) > While we don't have any knob in the ui for it yet, here is a workaround for > connecting to hidden aps: > > gdbus call --session --dest org.gnome.network_manager_applet --object-path > /org/gnome/network_manager_applet --method > org.gnome.network_manager_applet.ConnectToHiddenNetwork Doesn't work for me:" [root@localhost ~]# sh -x /tmp/x + gdbus call --session --dest org.gnome.network_manager_applet --object-path /org/gnome/network_manager_applet --method org.gnome.network_manager_applet.ConnectToHiddenNetwork Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.network_manager_applet was not provided by any .service files [root@localhost ~]#
if you're in F16, I think the command may need updating.
(In reply to comment #53) > if you're in F16, I think the command may need updating. No, I have F15. [charlieb@localhost ~]$ rpm -qf /etc/system-release fedora-release-15-3.noarch [charlieb@localhost ~]$
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping