Laptop completely freezes.

[Robin Rawat]

It usually happens when i watch videos in full screen mode.

journalctl before crash:

Jul 20 20:12:16 bits pkexec[356131]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
Jul 20 20:12:16 bits pkexec[356131]: robin: Executing command [USER=root] [TTY=unknown] [CWD=/home/robin] [COMMAND=/usr/lib/update-notifier/package-system-locked]
Jul 20 20:15:01 bits CRON[357760]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul 20 20:15:01 bits CRON[357761]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 20 20:15:01 bits CRON[357760]: pam_unix(cron:session): session closed for user root
Jul 20 20:16:30 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jul 20 20:16:30 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jul 20 20:16:30 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jul 20 20:16:30 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jul 20 20:16:30 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jul 20 20:16:30 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jul 20 20:16:30 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jul 20 20:16:30 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jul 20 20:16:30 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jul 20 20:16:43 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jul 20 20:16:43 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jul 20 20:16:43 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jul 20 20:16:43 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jul 20 20:16:43 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jul 20 20:16:43 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jul 20 20:16:43 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jul 20 20:16:43 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jul 20 20:16:43 bits gnome-shell[2328]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jul 20 20:17:01 bits CRON[359073]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul 20 20:17:01 bits CRON[359074]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 20 20:17:01 bits CRON[359073]: pam_unix(cron:session): session closed for user root
Jul 20 20:19:16 bits NetworkManager[834]: <info> [1658328556.7328] manager: NetworkManager state is now CONNECTED_SITE
Jul 20 20:19:16 bits whoopsie[1302]: [20:19:16] offline
Jul 20 20:19:16 bits dbus-daemon[833]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (>
Jul 20 20:19:16 bits systemd[1]: Starting Network Manager Script Dispatcher Service...
Jul 20 20:19:16 bits dbus-daemon[833]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jul 20 20:19:16 bits systemd[1]: Started Network Manager Script Dispatcher Service.
Jul 20 20:19:17 bits NetworkManager[834]: <info> [1658328557.4981] manager: NetworkManager state is now CONNECTED_GLOBAL
Jul 20 20:19:17 bits whoopsie[1302]: [20:19:17] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/7
Jul 20 20:19:17 bits whoopsie[1302]: [20:19:17] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/7
Jul 20 20:19:17 bits whoopsie[1302]: [20:19:17] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/7
Jul 20 20:19:17 bits whoopsie[1302]: [20:19:17] online
Jul 20 20:19:27 bits systemd[1]: NetworkManager-dispatcher.service: Succeeded.
-- Reboot --
Jul 20 20:26:38 bits kernel: microcode: microcode updated early to revision 0xf0, date = 2021-11-12
Jul 20 20:26:38 bits kernel: Linux version 5.15.0-41-generic (buildd@lcy02-amd64-105) (gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #44~20.04.1-Ubuntu S>
Jul 20 20:26:38 bits kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=3ce91244-c568-455b-b312-186610cba9d7 ro quiet splash vt.handoff=7
Jul 20 20:26:38 bits kernel: KERNEL supported cpus:

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 21 06:31:43 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-05-11 (70 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]