Temporary screen freeze when gnome-shell logs "Removing a network device that was not added"

[Vivek Gani]

As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769981/comments/25 , I've been observing an issue when unlocking my computer (usually from a screen lock state, not hibernation/sleep) where after entering the first few characters of my password the screen freezes for 10-20 seconds before I can do any type of input (mouse, touch, keyboard).

I've also seen it happen when having touch / gesture input switch between displaying the user name and the password field - where the screen can get stuck in the animation in an interstitial state for a number of seconds.

I've largely been noticing this since upgrading from Ubuntu 21.10 to 22.04. It doesn't happen all the time, but often enough to file an issue for.

So far I've tried:
- Disabling the 'blur my shell' extension - still encountered the issue again eventually.
- Looking for anything associated with this in /var/crash - couldn't find anything.
- Looking for anything associated at errors.ubuntu.com for my id.

What I may eventually try:
- Seeing if this may depend on having too many browser tabs / apps open. Currently not in a position to do this.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
Uname: Linux 5.15.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May 26 19:19:28 2022
DisplayManager: gdm3
InstallationDate: Installed on 2021-07-15 (315 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago)

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. I can see from the attached files that you have a lot of unsupported extensions enabled and at least some of them are buggy according to the log messages.

The first thing to try is always to REMOVE ALL unsupported extensions and then log in again. Please run:

  cd ~/.local/share/gnome-shell
  rm -rf extensions
  gsettings set org.gnome.shell enabled-extensions "[]"
  gsettings set org.gnome.shell disabled-extensions "[]"

and then log in again.

If the freeze persists after that then next time it happens please:

  1. Wait 10 seconds.

  2. Reboot.

  3. Run: journalctl -b-1 > prevboot.txt

  4. Attach the resulting text file here.

[Vivek Gani (vivekgani2)]

Got it, thanks. I haven't tried to 'remove all' unsupported extensions per your instructions yet, but did disable all non-system extensions via the 'Extensions Manager' app and still noticed the issue (without logging in again). Will now try removing all per your instructions, logging in again/rebooting and see.

EDIT: haven't logged out or rebooted yet, but noticing a slight (not as much) delay still. Could be associated with having a large number of apps/browser tabs open.

[Vivek Gani (vivekgani2)]

Just noticed the screenlock freeze again, worked fine most of yesterday (mostly only had firefox open), then later installed GSConnect extension (was essential for getting an errand done) and had sublimetext open (around 15 workspaces open). See https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976163 for associated info.

[Feenics Dev (feenicsdev)]

I've been seeing the same behaviour since installing 22.04.

What information can I provide to help diagnose?

[stelian (stelian)]

Same here, but in my setup I also have an external HDMI monitor (over a USB-C extension port).

When it hangs, I can immediately unblock it by disconnecting the HDMI monitor.

This happens quite often, I would say about 1 in 4 screen locks.

I only use 2 extensions: <email address hidden> and <email address hidden>

[Timo Hilden (stgermain77)]

I have this too. Upgraded from 21.10. Installed into a laptop, no external monitors. Login screen freezes around letter number 5 for perhaps 30 seconds. Then black screen for some time. When the screen is black it wakes up with mouse movement or key press. The password is is still processed and the desktop is open after the freeze.

[Daniel van Vugt (vanvugt)]

The repetition of this message in Vivek's logs may be relevant:

  Removing a network device that was not added

But we are still waiting for Vivek to remove all extensions to exclude the most common source of gnome-shell bugs.

Everyone else please be sure to open your own bugs for separate investigation.

[Vivek Gani (vivekgani2)]

Will remove all extensions again to help with testing. I currently just have three non-system extensions enabled (freon, gsconnect, improved osk) but have observed the something similar as what Timo has mentioned in https://bugs.launchpad.net/ubuntu/+bug/1975884/comments/7 where the screen freezes (WITHOUT a black screen) showing only the first few password characters indicated typed, then after the password processes the desktop opens up after the freeze.

One thing to note is I've been using my device sometimes in a rather warm environment (80-90 degF) at times with a low-power charger. Worth also noting in some of these scenarios I'm using usb tethering with an android device (in case "Removing a network device that was not added" carries relevance).

[Vivek Gani (vivekgani2)]

Experienced a login freeze just now with no other extensions and tried to followed the instructions of rebooting then:

  3. Run: journalctl -b-1 > prevboot.txt

  4. Attach the resulting text file here.

Here's what I've got. The freeze I experienced happened around/before Jul 04 09:31:23, will attach another excerpt of just that timeframe.

[Vivek Gani (vivekgani2)]

Attachment around Jul 04 09:31:23 , note that when encountering this I did not have internet access.

[Vivek Gani (vivekgani2)]

Another freeze, again while not having internet. Happens around Jul 05 20:08 or Jul 05 20:09 and lasts for at least 20-30 seconds, possibly a minute.

[Daniel van Vugt (vanvugt)]

I guess just confirm you don't have "gsconnect" loaded when the bug occurs?

[Vivek Gani (vivekgani2)]

Confirming I did not have gsconnect or any non-system extensions installed for the journalctl's shared in comments #10 ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975884/comments/10 ) or #11 ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975884/comments/11 ) or #12 ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975884/comments/12 ).

I did have Ubuntu Dock disabled but wouldn't expect that to make a difference.

[Launchpad Janitor (janitor)]

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

[Mossroy (mossroy)]

I have the same symptoms on 3 different computers (all upgraded from Ubuntu 20.04).

I do have the error message "Removing a network device that was not added" in /var/log/syslog, but not at the time when the problem occurs.

My computers are always plugged to the network with an ethernet cable.

I only have one gnome extension (on the 3 of them): https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet

I found the workaround to hit ctrl-alt-F1 then ctrl-alt-F2: after typing my password again, my session is back

[Martin D. Weinberg (martin-weinberg-5)]

I have the same problem on 2 installs out of 3. And no "Removing a network device that was not added" in /var/log/syslog.

I also found that the problem does not seem to occur on Xorg, only on Wayland.

And I also found that the work around is to go to a console and then back using (e.g.) ctrl-alt-F1 then ctrl-alt-F2.

[Vivek Gani (vivekgani2)]

While others are commenting on this, it's worth noting that during this freeze issue on the lockscreen the computer may still be responsive to keyboard input when a correct password + enter was inputted.

For example, if I have an application (e.g. calendar reminder notifications, or a browser + url bar active), I'll notice the related responses to my keystrokes during the freeze (calendar - sounds for most keystrokes, browser url - keystroke presses observed after freeze/unlock) if I enter the correct password.

[betteropensource (betteropensource)]

I have the same problem on a tower pc where I installed days ago ubunt 20.04 and then upgraded it to 22.04. This issue happened after some hour I left the pc powered on with the monitor halted. When I returned for use it, I was able to write the password to unlock the screen and press enter but the scree n appeared freezed with half * password chars inserted and with the aspect of loading something.
I checked that on energy settings I already have these:
- "shut down the screen": Off
- "automatic suspension": never

CTRL+ALT+F* did nothing. Around 20 seconds after I hit enter on the unlock screen, it come back and I'm now writing here.

[Marten (martenp-bewildered)]

I have observed the issue described in this report on three separate installations of 22.04 (clean install & upgrade from 20.04) from release until now. Given the highly user impacting nature of it, I am surprised it remains of undecided importance and unassigned.