Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forces to logout and login again after lid close #335

Open
gauranshkumar opened this issue Jul 3, 2024 · 2 comments
Open

Forces to logout and login again after lid close #335

gauranshkumar opened this issue Jul 3, 2024 · 2 comments
Labels

Comments

@gauranshkumar
Copy link

Hello, I am using this extension on the latest Gnome 46 (on x11 with Nvidia), and as soon as I close my laptop lid and open it again, it gives me a white screen with the text: System crashed and cannot be recovered Please log out and log in again. Logging in again gives me a new session, and the behavior repeats each time I close the lid. It just made the machine unusable. Please fix this, as it was a nice extension.

journalctl logs for GDM

Jul 02 12:09:51 prometheus systemd[1]: Starting GNOME Display Manager...
Jul 02 12:09:51 prometheus systemd[1]: Started GNOME Display Manager.
Jul 02 12:09:51 prometheus gdm-launch-environment][1107]: pam_systemd(gdm-launch-environment:session): New sd-bus connection (system-bus-pam-systemd-1107) opened.
Jul 02 12:09:57 prometheus gdm-password][1607]: pam_systemd_home(gdm-password:auth): New sd-bus connection (system-bus-pam-systemd-home-1607) opened.
Jul 02 12:10:00 prometheus gdm-password][1607]: gkr-pam: unable to locate daemon control file
Jul 02 12:10:00 prometheus gdm-password][1607]: gkr-pam: stashed password to try later in open session
Jul 02 12:10:00 prometheus gdm-password][1607]: pam_unix(gdm-password:session): session opened for user gauransh(uid=1000) by gauransh(uid=0)
Jul 02 12:10:00 prometheus gdm-password][1607]: pam_systemd(gdm-password:session): New sd-bus connection (system-bus-pam-systemd-1607) opened.
Jul 02 12:10:00 prometheus gdm-password][1607]: gkr-pam: unlocked login keyring
Jul 02 12:10:00 prometheus gdm[1090]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Jul 02 12:10:10 prometheus gdm[1090]: Gdm: Child process -1126 was already dead.
Jul 02 12:10:10 prometheus gdm[1090]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Jul 02 19:28:07 prometheus gdm[1090]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Jul 02 19:28:07 prometheus gdm-launch-environment][56824]: pam_systemd(gdm-launch-environment:session): New sd-bus connection (system-bus-pam-systemd-56824) opened.
Jul 02 19:28:18 prometheus gdm[1090]: GLib: Source ID 82 was not found when attempting to remove it
Jul 02 19:28:29 prometheus gdm[1090]: Gdm: Child process -56844 was already dead.
Jul 02 19:28:29 prometheus gdm[1090]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Jul 02 22:38:27 prometheus gdm[1090]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Jul 02 22:38:28 prometheus gdm-launch-environment][61845]: pam_systemd(gdm-launch-environment:session): New sd-bus connection (system-bus-pam-systemd-61845) opened.
Jul 02 22:38:37 prometheus gdm[1090]: GLib: Source ID 127 was not found when attempting to remove it
Jul 02 22:38:48 prometheus gdm[1090]: Gdm: Child process -61863 was already dead.
Jul 02 22:38:48 prometheus gdm[1090]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Jul 02 22:38:53 prometheus gdm[1090]: GLib: Source ID 186 was not found when attempting to remove it
Jul 02 22:40:35 prometheus gdm[1090]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Jul 02 22:40:35 prometheus systemd[1]: Stopping GNOME Display Manager...
Jul 02 22:40:35 prometheus gdm[1090]: Gdm: Freeing conversation 'gdm-password' with active job
Jul 02 22:40:35 prometheus gdm[1090]: GLib: Source ID 202 was not found when attempting to remove it
Jul 02 22:40:35 prometheus systemd[1]: gdm.service: Deactivated successfully.
Jul 02 22:40:35 prometheus systemd[1]: Stopped GNOME Display Manager.

inxi -b

System:
  Host: prometheus Kernel: 6.9.7-arch1-1 arch: x86_64 bits: 64
  Desktop: GNOME v: 46.3.1 Distro: EndeavourOS
Machine:
  Type: Laptop System: Micro-Star product: GP65 Leopard 10SFK v: REV:1.0
    serial: <superuser required>
  Mobo: Micro-Star model: MS-16U7 v: REV:1.0 serial: <superuser required>
    UEFI: American Megatrends v: E16U7IMS.10C date: 11/17/2020
Battery:
  ID-1: BAT1 charge: 24.4 Wh (64.2%) condition: 38.0/51.6 Wh (73.6%)
    volts: 10.8 min: 10.9
CPU:
  Info: 6-core Intel Core i7-10750H [MT MCP] speed (MHz): avg: 1125
    min/max: 800/5000
Graphics:
  Device-1: Intel CometLake-H GT2 [UHD Graphics] driver: i915 v: kernel
  Device-2: NVIDIA TU106M [GeForce RTX 2070 Mobile / Max-Q Refresh]
    driver: nvidia v: 555.58
  Device-3: Chicony HD Webcam driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0 driver: X:
    loaded: modesetting,nvidia dri: iris gpu: i915 resolution: 1920x1080~144Hz
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 555.58
    renderer: NVIDIA GeForce RTX 2070/PCIe/SSE2
Network:
  Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
Drives:
  Local Storage: total: 1.14 TiB used: 74.17 GiB (6.3%)
Info:
  Memory: total: 24 GiB available: 23.29 GiB used: 4.18 GiB (17.9%)
  Processes: 411 Uptime: 17m Shell: Zsh inxi: 3.3.35
@stuarthayhurst
Copy link
Collaborator

Was this caused by the upgrade to GNOME / Mutter 46.3.1?

@careca1970
Copy link

careca1970 commented Sep 1, 2024

Hi there, I want to believe I have the same issue here.

Since I upgraded to Fedora 40 (Gnome 46.4), sims like Caffeine make the shell crash every time it tries to go to sleep.
After reinstalling the extensions a couple of times, I just left it uninstalled now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants