Public bug reported:

### Affected version
* Your OS and version: ubuntu 22.04 (dev series, before release)
* Affected GNOME Shell version: 41.3-1ubuntu1
* Issue appears in Wayland

### Bug summary

Sometimes gnome-shell hangs when I open the laptop to login from the
suspend state, preventing the rest of gdm to load. Because I am running
wayland, I cannot open another tty either. If I close the laptop lid
again and wait 30s or so and reopen to retry, it will work.

### Steps to reproduce
Not 100% reproducible, happens sometimes.
1. open laptop to login from suspend
2. see login screen with time and all looks normal but is unresponsive

### What happened


The login screen is hung and unresponsive to clicks/touches(touchscreen)/any 
keyboard input events.

### What did you expect to happen

The login screen should be responsive to input.

### Relevant logs, screenshots, screencasts etc.

After a successful login, I see a crash in journalctl:

```
Mar 01 09:58:40 fenrir gnome-shell[2799]: JS ERROR: Gio.DBusError: Error 
calling StartServiceByName for net.reactivated.Fprint: Failed to activate 
service 'net.reactivated.>
                                          
_injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25
                                          
_makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17
                                          
ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:154:31
                                          
_init@resource:///org/gnome/shell/gdm/authPrompt.js:72:30
                                          
_ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:691:28
                                          
_showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:730:14
                                          
vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:630:14
```

<!-- Do not remove the following line. -->

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: fprintd 1.94.2-1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
CrashCounter: 1
Date: Tue Mar  1 09:58:16 2022
ExecutablePath: /usr/libexec/fprintd
ExecutableTimestamp: 1645749862
InstallationDate: Installed on 2020-06-29 (609 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcCmdline: /usr/libexec/fprintd
ProcCwd: /
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: fprintd
UpgradeStatus: Upgraded to jammy on 2022-01-04 (55 days ago)
UserGroups: N/A

** Affects: gnome-shell
     Importance: Unknown
         Status: Unknown

** Affects: gnome-shell (Ubuntu)
     Importance: Undecided
         Status: In Progress


** Tags: amd64 apport-crash jammy

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5168
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5168

** Also affects: fprintd via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5168
   Importance: Unknown
       Status: Unknown

** Description changed:

  ### Affected version
  * Your OS and version: ubuntu 22.04 (dev series, before release)
  * Affected GNOME Shell version: 41.3-1ubuntu1
  * Issue appears in Wayland
  
  ### Bug summary
  
  Sometimes gnome-shell hangs when I open the laptop to login from the
  suspend state, preventing the rest of gdm to load. Because I am running
  wayland, I cannot open another tty either. If I close the laptop lid
  again and wait 30s or so and reopen to retry, it will work.
  
  ### Steps to reproduce
  Not 100% reproducible, happens sometimes.
  1. open laptop to login from suspend
  2. see login screen with time and all looks normal but is unresponsive
  
  ### What happened
  
- The bug has been filed upstream as well: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5168
- ---------------------------------
+ 
  The login screen is hung and unresponsive to clicks/touches(touchscreen)/any 
keyboard input events.
  
  ### What did you expect to happen
  
  The login screen should be responsive to input.
  
  ### Relevant logs, screenshots, screencasts etc.
  
  After a successful login, I see a crash in journalctl:
  
  ```
  Mar 01 09:58:40 fenrir gnome-shell[2799]: JS ERROR: Gio.DBusError: Error 
calling StartServiceByName for net.reactivated.Fprint: Failed to activate 
service 'net.reactivated.>
-                                           
_injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25
-                                           
_makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17
-                                           
ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:154:31
-                                           
_init@resource:///org/gnome/shell/gdm/authPrompt.js:72:30
-                                           
_ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:691:28
-                                           
_showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:730:14
-                                           
vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:630:14
+                                           
_injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25
+                                           
_makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17
+                                           
ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:154:31
+                                           
_init@resource:///org/gnome/shell/gdm/authPrompt.js:72:30
+                                           
_ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:691:28
+                                           
_showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:730:14
+                                           
vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:630:14
  ```
- 
  
  <!-- Do not remove the following line. -->
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: fprintd 1.94.2-1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  Date: Tue Mar  1 09:58:16 2022
  ExecutablePath: /usr/libexec/fprintd
  ExecutableTimestamp: 1645749862
  InstallationDate: Installed on 2020-06-29 (609 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcCmdline: /usr/libexec/fprintd
  ProcCwd: /
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: fprintd
  UpgradeStatus: Upgraded to jammy on 2022-01-04 (55 days ago)
  UserGroups: N/A

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962566

Title:
  gnome-shell crash after resume from suspend in util.js:154

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1962566/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to