gnome-shell crashes with signal 5 in windowManager.js:1384
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When launching CSGO via Steam (installed from the repositories via the steam metapackage), the session begins hanging for a bit before a fullscreen popup says "Something has gone wrong" and "the system could not recover", a logout button, and I am sent back to GDM.
This does not happen under Wayland, BTW. But I was not sure whether to report this as a GNOME Shell issue, a Mutter issue, or an X11/Xorg issue.
GNOME Shell version:
gnome-shell:
Installed: 3.38.1-1ubuntu1
System information:
System: Kernel: 5.8.0-25-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: N/A
Distro: Ubuntu 20.10 (Groovy Gorilla)
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 5407 date: 12/31/2019
CPU: Info: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ rev: 2
L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 108799
Speed: 1376 MHz min/max: 1550/3400 MHz boost: disabled Core speeds (MHz): 1: 1377 2: 1377
3: 1378 4: 1378 5: 1377 6: 1377 7: 1378 8: 1375 9: 1377 10: 1377 11: 1376 12: 1377 13: 1376
14: 1377 15: 1378 16: 1377
Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: XFX Pine
driver: amdgpu v: kernel bus ID: 0c:00.0
Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati
OpenGL: renderer: AMD Radeon RX 5700 XT (NAVI10 DRM 3.38.0 5.8.0-25-generic LLVM 11.0.0)
v: 4.6 Mesa 20.2.1 direct render: Yes
Audio: Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
driver: snd_hda_intel v: kernel bus ID: 09:00.0
bus ID: 0e:00.3
bus ID: 1-1.3:4
bus ID: 3-4:2
bus ID: 1-9:6
Sound Server: ALSA v: k5.8.0-25-generic
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK
driver: r8169 v: kernel port: f000 bus ID: 04:00.0
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 6.60 TiB used: 625.28 GiB (9.3%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB size: 232.89 GiB
ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB
temp: 28 C
ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB
temp: 25 C
ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB
temp: 26 C
ID-5: /dev/sdd type: USB vendor: Western Digital model: WD easystore 2624 size: 4.55 TiB
ID-6: /dev/sde vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB
temp: 26 C
Partition: ID-1: / size: 223.52 GiB used: 28.67 GiB (12.8%) fs: btrfs dev: /dev/nvme0n1p3
ID-2: /boot size: 945.6 MiB used: 79.6 MiB (8.4%) fs: ext4 dev: /dev/nvme0n1p2
ID-3: /home size: 223.52 GiB used: 28.67 GiB (12.8%) fs: btrfs dev: /dev/nvme0n1p3
Swap: ID-1: swap-1 type: partition size: 7.46 GiB used: 4.0 MiB (0.1%) dev: /dev/nvme0n1p4
Sensors: System Temperatures: cpu: 30.6 C mobo: N/A gpu: amdgpu temp: 48.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info: Processes: 442 Uptime: 1h 51m Memory: 31.36 GiB used: 2.55 GiB (8.1%) Init: systemd
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.1-1ubuntu1
ProcVersionSign
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 24 04:34:09 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-10-24 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageV
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1897765, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.