Launchpad has imported 13 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=750260.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2015-06-02T03:12:42+00:00 Chris Murphy wrote: Created attachment 304401 screen shot control-center-3.16.2-1.fc22.x86_64 There is a question mark icon in the upper right corner that turns out to be for the wired connection. A ? used in this manner suggests the system is confused about something, and wants me to know that it's confused, hoping I can do something about it. So I'd expect there'd be a notification or a way to get more information about what the confusion is about. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1722256/comments/0 ------------------------------------------------------------------------ On 2015-06-02T03:15:42+00:00 Chris Murphy wrote: Created attachment 304402 journal for this boot Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1722256/comments/1 ------------------------------------------------------------------------ On 2015-06-02T10:14:57+00:00 Bugzilla-x wrote: The menu bar is part of gnome-shell. The "?" you're seeing though means that the connectivity check failed. [ 3920.153840] f21v.localdomain NetworkManager[826]: <info> Connectivity check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with 'Peer failed to perform TLS handshake'. It's either a Fedora infrastructure problem, or a NetworkManager one. Reassigning to NetworkManager. See bug 750268 for a follow-up on the icon not being self-explanatory enough. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1722256/comments/2 ------------------------------------------------------------------------ On 2015-06-03T09:56:08+00:00 Thomas Haller wrote: This is the same as downstream bug https://bugzilla.redhat.com/show_bug.cgi?id=1176316 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1722256/comments/3 ------------------------------------------------------------------------ On 2015-08-31T09:48:34+00:00 Jan Vlug wrote: I have a similar problem with an unexplained question mark for a wireless connection that works fine. I seem to have this issue when I'm behind a proxy (both for wired and wireless network connections). Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1722256/comments/4 ------------------------------------------------------------------------ On 2015-09-08T10:38:43+00:00 Thomas Haller wrote: (In reply to Bastien Nocera from comment #2) > > [ 3920.153840] f21v.localdomain NetworkManager[826]: <info> Connectivity > check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with > 'Peer failed to perform TLS handshake'. In this case, the connectivity check failed because of the SSL connection. It is anyway a bad idea to use https for connectivity checking. We fixed that upstream in bug 747866 and commit http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2a3a4eb16f9119bf434a28adc94c2684da8fd5e4 Note that this is largely a configuration issue. So, users must rectify their configuration, or (if the distribution installed configuration snippets) the distribution must fix the configuration file. For downstream/Fedora, https://bugzilla.redhat.com/show_bug.cgi?id=1176316 this will be done. Closing BZ as fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1722256/comments/5 ------------------------------------------------------------------------ On 2015-09-08T14:34:09+00:00 Bugzilla-x wrote: (In reply to Thomas Haller from comment #5) > (In reply to Bastien Nocera from comment #2) > > > > [ 3920.153840] f21v.localdomain NetworkManager[826]: <info> Connectivity > > check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with > > 'Peer failed to perform TLS handshake'. > > In this case, the connectivity check failed because of the SSL connection. > > It is anyway a bad idea to use https for connectivity checking. Why? It protects the user's privacy, at least a tiny bit. > We fixed that upstream in bug 747866 and commit > http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/ > ?id=2a3a4eb16f9119bf434a28adc94c2684da8fd5e4 If by "fixed" you mean "worked around", then yes. > Note that this is largely a configuration issue. So, users must rectify > their configuration, or (if the distribution installed configuration > snippets) the distribution must fix the configuration file. > > > For downstream/Fedora, https://bugzilla.redhat.com/show_bug.cgi?id=1176316 > this will be done. > > > > Closing BZ as fixed. This really isn't fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1722256/comments/6 ------------------------------------------------------------------------ On 2015-09-08T14:45:12+00:00 Thomas Haller wrote: (In reply to Bastien Nocera from comment #6) > (In reply to Thomas Haller from comment #5) > > (In reply to Bastien Nocera from comment #2) > > > > > > [ 3920.153840] f21v.localdomain NetworkManager[826]: <info> Connectivity > > > check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with > > > 'Peer failed to perform TLS handshake'. > > > > In this case, the connectivity check failed because of the SSL connection. > > > > It is anyway a bad idea to use https for connectivity checking. > > Why? It protects the user's privacy, at least a tiny bit. there is nothing private about the connectivity-check request. Especially does the HTTP header not contain fields beside: GET /static/hotspot.txt HTTP/1.1 Host: fedoraproject.org Connection: close Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1722256/comments/7 ------------------------------------------------------------------------ On 2015-09-08T15:00:14+00:00 Thomas Haller wrote: (In reply to Bastien Nocera from comment #6) > (In reply to Thomas Haller from comment #5) > > (In reply to Bastien Nocera from comment #2) > > > > > > [ 3920.153840] f21v.localdomain NetworkManager[826]: <info> Connectivity > > > check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with > > > 'Peer failed to perform TLS handshake'. > > > > In this case, the connectivity check failed because of the SSL connection. > > > > It is anyway a bad idea to use https for connectivity checking. > > Why? It protects the user's privacy, at least a tiny bit. it's a bad idea, because it works bad with detecting captive portals. And a portal might not handle SSL connections at all (which means we would detect "no-connectivity", instead of "portal"). If the portal does handle SSL connections it present an invalid certificate and the connection fails again (and to NM it's again not clear that this indicates "portal"). Also, we warn now about HTTPS use: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=eab32a5252e82361a563154cd8bfc3949aaad119 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1722256/comments/8 ------------------------------------------------------------------------ On 2015-09-08T15:27:34+00:00 Bugzilla-x wrote: (In reply to Thomas Haller from comment #8) > (In reply to Bastien Nocera from comment #6) > > (In reply to Thomas Haller from comment #5) > > > (In reply to Bastien Nocera from comment #2) > > > > > > > > [ 3920.153840] f21v.localdomain NetworkManager[826]: <info> > > > > Connectivity > > > > check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with > > > > 'Peer failed to perform TLS handshake'. > > > > > > In this case, the connectivity check failed because of the SSL connection. > > > > > > It is anyway a bad idea to use https for connectivity checking. > > > > Why? It protects the user's privacy, at least a tiny bit. > > it's a bad idea, because it works bad with detecting captive portals. > > And a portal might not handle SSL connections at all (which means we would > detect "no-connectivity", instead of "portal"). > > If the portal does handle SSL connections it present an invalid certificate > and the connection fails again (and to NM it's again not clear that this > indicates "portal"). > > Also, we warn now about HTTPS use: > http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/ > ?id=eab32a5252e82361a563154cd8bfc3949aaad119 I'd rather have a fallback to HTTP in those cases where HTTPS fails, to ensure the problem is actually with the network and not with the connection, rather than actually hit HTTP in the wide internet all the time when connected. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1722256/comments/9 ------------------------------------------------------------------------ On 2015-10-05T09:12:31+00:00 Jan Vlug wrote: A question marks occurs also when you are behind a proxy, because the proxy settings are not being used when testing the connectivity. See this issue in the Fedora Bugzilla for more details: https://bugzilla.redhat.com/show_bug.cgi?id=1184406 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1722256/comments/10 ------------------------------------------------------------------------ On 2015-10-05T09:18:45+00:00 Jan Vlug wrote: See also: https://bugzilla.gnome.org/show_bug.cgi?id=738694 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1722256/comments/11 ------------------------------------------------------------------------ On 2018-02-22T05:00:14+00:00 Daniel van Vugt wrote: Also tracking in Ubuntu bug: https://launchpad.net/bugs/1722256 I'm seeing inconsistent behaviour between different machines on the same network. Plus no other desktop environment besides Gnome exhibits the problem, so it's a bad look regardless of the cause. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1722256/comments/26 ** Changed in: gnome-shell-legacy-bugs Status: Unknown => Confirmed ** Changed in: gnome-shell-legacy-bugs Importance: Unknown => Medium ** Bug watch added: Red Hat Bugzilla #1176316 https://bugzilla.redhat.com/show_bug.cgi?id=1176316 ** Bug watch added: Red Hat Bugzilla #1184406 https://bugzilla.redhat.com/show_bug.cgi?id=1184406 ** Bug watch added: bugzilla.gnome.org/ #738694 https://bugzilla.gnome.org/show_bug.cgi?id=738694 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1722256 Title: Wifi connection status icon shows a "?" question mark when connected Status in GNOME Shell: Confirmed Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: https://bugzilla.gnome.org/show_bug.cgi?id=750260 Wifi connection status icon on the top bar shows a "?" even when connected to a wifi network. --- ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Package: gnome-shell 3.26.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1722256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
