Wifi connection status icon shows a "?" question mark when connected

[Ignacio]

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

[Chris Murphy (dr4-b5gpiyla-tff)]

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.

[Chris Murphy (dr4-b5gpiyla-tff)]

Created attachment 304402
journal for this boot

[Bugzilla-x (bugzilla-x)]

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.

[Thomas Haller (thaller-1)]

This is the same as downstream bug https://bugzilla.redhat.com/show_bug.cgi?id=1176316

[Jan Vlug (jan-vlug)]

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).

[Thomas Haller (thaller-1)]

(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.

[Bugzilla-x (bugzilla-x)]

(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.

[Thomas Haller (thaller-1)]

(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

[Thomas Haller (thaller-1)]

(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

[Bugzilla-x (bugzilla-x)]

(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.

[Jan Vlug (jan-vlug)]

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

[Jan Vlug (jan-vlug)]

See also:
https://bugzilla.gnome.org/show_bug.cgi?id=738694

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

Confirmed. But also...

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1722256

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Ignacio (iguarna)]

apport information

[Ignacio (iguarna)]

apport information

[Ignacio (iguarna)]

apport information

[Ignacio (iguarna)]

apport information

[Ignacio (iguarna)]

apport information

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Max Waterman (dwater)]

https://bugzilla.gnome.org/show_bug.cgi?id=750260

[Artem Chekunov (scorp-dev-null)]

The problem was solved for me when I set `dns=default` in NetworkManager.conf

```
cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile
; dns=dnsmasq
dns=default

[ifupdown]
managed=false

[device]
wifi.scan-rand-mac-address=no
```

P.S. It also solve other DNS problems for me.

[Daniel van Vugt (vanvugt)]

Thanks for that. I'm seeing this bug on maybe 2/3 laptops I've tried with Ubuntu 18.04.

[Casey (sometimescasey)]

Confirming that adding dns=default to /etc/NetworkManager/NetworkManager.conf solved the problem for me as well - thank you Scorpius!

[Ken VanDine (ken-vandine)]

This was affecting me on 17.10 as well. Added dns=default did resolve it. Without that there was no nameserver being set.

[Daniel van Vugt (vanvugt)]

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.

[Anonymous (dermart)]

Same problem here on Ubuntu 18.04. However adding dns=default to the [main] section of /etc/NetworkManager/NetworkManager.conf makes it worse. 1. The question mark shows even if connected 2. DNS does not work anymore.

[Sebastien Bacher (seb128)]

Could those having the issue add their journalctl log after triggering the bug?

[Farzad Aqajani (farzad98a)]

I recently realized that the problem with the Wi-Fi icon will be resolved by adding a VPN configuration from Network Settings and connecting to it.
After that, the problem will be fixed forever. Even without connecting to the VPN.
Also, after logging off, the problem will not come back.
But restarting and shutting down the system will bring the problem back.

[Sandor Rozsa (gsrozsa)]

Questionmark changes back to normal after updating the system through update manager, but it happened to me at least twice, so it was not a fix that solved some connectivity issue, since the update went fine both times.

[praesepe (praesepe)]

Is this related ?

"...a Connectivity Checking feature was introduced. Ubuntu 17.10 and onwards, you are presented with a question mark in network status whenever a Captive Portal is detected. This new feature works by pinging the http://connectivity-check.ubuntu.com URL, time to time, in order to detect a captive portal."
https://vitux.com/disable-connectivity-checking-on-ubuntu-for-public-wifi-captive-portals/

[Daniel van Vugt (vanvugt)]

Sounds related, and maybe that's where the bug is. Although it's not an Ubuntu-specific issue...

https://bugzilla.gnome.org/show_bug.cgi?id=750260

That said, I haven't seen this bug in a long time. If you do see it, what release are you using?

[Sandor Rozsa (gsrozsa)]

Hi,

I am using Ubuntu 18.04 LTS.

Cheers
Sándor

Daniel van Vugt <email address hidden> ezt írta (időpont: 2019.
júl. 11., Cs 3:50):

> Sounds related, and maybe that's where the bug is. Although it's not an
> Ubuntu-specific issue...
>
> https://bugzilla.gnome.org/show_bug.cgi?id=750260
>
> That said, I haven't seen this bug in a long time. If you do see it,
> what release are you using?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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/+bug/1722256/+subscriptions
>

[Sandor Rozsa (gsrozsa)]

I will gather more info next time I see this.

Rózsa Sándor <email address hidden> ezt írta (időpont: 2019. júl. 11., Cs
15:42):

> Hi,
>
> I am using Ubuntu 18.04 LTS.
>
> Cheers
> Sándor
>
> Daniel van Vugt <email address hidden> ezt írta (időpont: 2019.
> júl. 11., Cs 3:50):
>
>> Sounds related, and maybe that's where the bug is. Although it's not an
>> Ubuntu-specific issue...
>>
>> https://bugzilla.gnome.org/show_bug.cgi?id=750260
>>
>> That said, I haven't seen this bug in a long time. If you do see it,
>> what release are you using?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> 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/+bug/1722256/+subscriptions
>>
>

[Jan Vlug (z-j)]

I had not seen this issue for a long time. But now I see it again.
Note that I am using Fedora 30 instead of Ubuntu, but this could very well be a non-distribution dependent issue, therefore I'm reporting here instead of opening a new issue in another bug tracker.

The question mark appeared after I had been fiddling with the wireless connection settings in an attempt to connect to a Ziggo Wifispot via WPA2-enterprise (in the end I did not manage to connect).

After that I connected to another wifi (that is now fully functional), I see the question mark.

Some output from nmcli monitor:
'Aquaris X5 Plus' is now the primary connection
wlp3s0: deactivating
Networkmanager is now in the 'connected (local only)' state
wlp3s0: disconnected
Networkmanager is now in the 'connected (site only)' state
'Linksys WRE (Johan)' is now the primary connection
wlp3s0: using connection 'Ziggo3F1518C'
wlp3s0: connecting (prepare)
wlp3s0: connecting (need authentication)
wlp3s0: connection failed
wlp3s0: disconnected
wlp3s0: using connection 'Aquaris X5 Plus'
wlp3s0: connecting (prepare)
wlp3s0: connecting (configuring)
wlp3s0: connecting (need authentication)
wlp3s0: connecting (prepare)
wlp3s0: connecting (configuring)
wlp3s0: connecting (getting IP configuration)
wlp3s0: connecting (checking IP connectivity)
wlp3s0: connecting (starting secondary connections)
wlp3s0: connected
Networkmanager is now in the 'connected (local only)' state
Networkmanager is now in the 'connected (site only)' state
'Aquaris X5 Plus' is now the primary connection

[Jan Vlug (jan-vlug)]

I just made a comment in Launchpad, which on second thought probably could have better been made here.

See: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722256/comments/35

[Heather Ellsworth (hellsworth)]

Updated the bug link

[Mohit Pathak (aystic)]

I tried "nmcli monitor" to monitor the wifi
I noticed that it changed from

----------------
Networkmanager is now in the 'connected' state
Connectivity is now 'full'
----------------

to

----------------
Networkmanager is now in the 'connected (site only)' state
Connectivity is now 'limited'
----------------

and then the internet stopped working and a ? icon replaced the wifi icon

I am using Ubuntu 22.10, Kernel: 5.19.0-23-generic