Bug #16620
Wi-Fi passphrase prompt is sometimes not displayed on Buster
100%
Description
Sometimes I can select a Wi-Fi network but then the dialog to enter the password is never displayed. Instead, I see a GNOME Shell stacktrace in the Journal, very similar to those we have attributed to topIcons so far. Disabling topIcons fixes the problem immediately.
Files
Subtasks
Related issues
Related to Tails - |
Resolved | 2019-03-15 |
History
#1 Updated by intrigeri 2019-04-03 11:23:02
This prevents me from doing Buster-related work that’s way more critical than the functionality provided by topIcons, so I’ll disable topIcons on feature/buster until we have a clearer plan on Bug #16608 and friends.
#2 Updated by intrigeri 2019-04-03 12:53:28
- Subject changed from topIcons sometimes prevents Wi-Fi configuration on Buster to Wi-Fi passphrase prompt is sometimes not displayed on Buster
I’ve seen this problem without topIcons. Trying to set up the password via GNOME Control Center made it crash, apparently due to a missing package. I’ll investigate.
#3 Updated by intrigeri 2019-04-03 13:55:13
- Status changed from Confirmed to In Progress
Applied in changeset commit:tails|40290be3651eaa6f08346231aef80eddd8b33c64.
#4 Updated by intrigeri 2019-04-03 13:57:16
I’ve fixed the GNOME Control Center part of this bug but the problem remains wrt. the passphrase prompt when selecting a Wi-Fi network via the GNOME Shell interface.
Restarting GNOME Shell (Alt + F2, r, ENTER) seems to fix this problem reliably.
#6 Updated by intrigeri 2019-04-03 17:33:11
I’ve seen another failure mode: the modal dialog with the prompt shows up, but neither clicking “Connect” nor “Cancel” has any effect.
I’ve tried a few things in the hope they would fix things, but they didn’t: without TopIcons enabled, without setting an administration password, without MAC spoofing, without ~/.gnome2/keyrings/
, and on a different laptop (ThinkPad X200).
But if I restart GNOME Shell (alt+f2) once logged in, before trying to connect to the Wi-Fi, then my first connection attempt works.
I can’t reproduce this bug with a pristine Debian Buster Live image.
#7 Updated by intrigeri 2019-04-03 18:55:01
Upgrading to GNOME Shell 3.32 from Debian experimental does not help.
#8 Updated by intrigeri 2019-04-03 21:08:37
- Assignee changed from intrigeri to alant
- QA Check set to Ready for QA
@alant, can you please review https://git.tails.boum.org/greeter/commit/?h=feature/buster aka. https://gitlab.com/Tails/tails/commit/91009b5a39884d4c90cf0d458eba454ed6c1a3fd?
#9 Updated by alant 2019-04-04 09:02:48
- QA Check changed from Ready for QA to Pass
#10 Updated by intrigeri 2019-04-05 10:54:37
- Status changed from In Progress to Resolved
- Assignee deleted (
alant) - % Done changed from 0 to 100
#11 Updated by intrigeri 2019-06-18 07:25:40
- related to
Bug #16560: MAC spoofing failure sometimes does not disable networking added