Gnome 3.34 bugs (?)

Vectorlocity · 2019-09-30 20:07:01

I upgraded my system to Gnome 3.34 recently, and have been noticing a bug with my system.
Whenever I launch a game from Steam such as Insurgency (it always happens with Insurgency in this case), it will get to its splash screen, and then freeze. I can't do anything in the current tty the game is in.
I usually only use tty1, but whenever that bug with the game occurs gdm starts using tty1 and gnome-shell switches to tty2. I ctrl-alt-f3 to tty3 and I login, and check the journals and I see this:

Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1:   device [1022:1453] error status/mask=00001000/00006000
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1:    [12] Timeout               
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1:   device [1022:1453] error status/mask=00000040/00006000
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1:    [ 6] BadTLP                
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1:   device [1022:1453] error status/mask=00001000/00006000
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1:    [12] Timeout               
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1:   device [1022:1453] error status/mask=00001000/00006000
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1:    [12] Timeout               
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1:   device [1022:1453] error status/mask=00001000/00006000
Sep 30 20:45:39 Kevin-B350MA kernel: pcieport 0000:00:03.1:    [12] Timeout               
Sep 30 20:45:41 Kevin-B350MA kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Sep 30 20:45:41 Kevin-B350MA kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Sep 30 20:45:41 Kevin-B350MA kernel: pcieport 0000:00:03.1:   device [1022:1453] error status/mask=00001000/00006000
Sep 30 20:45:41 Kevin-B350MA kernel: pcieport 0000:00:03.1:    [12] Timeout               
Sep 30 20:45:41 Kevin-B350MA kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0

A bunch of PCI-e errors. So I check lspci:

kevin@Kevin-B350MA ~ % lspci                                                                                                                                                                                                           :(
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset USB 3.1 xHCI Controller (rev 02)
01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset SATA Controller (rev 02)
01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b2 (rev 02)
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
02:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
03:00.0 USB controller: ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
08:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1)
08:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1)
09:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function
09:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor
09:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller
0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function
0a:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
0a:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller

I'm not entirely sure what device 00:03.1 is.

Another thing I see in the journals is:

Sep 30 18:08:54 Kevin-B350MA gnome-shell[4557]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can als>
Sep 30 18:08:54 Kevin-B350MA gnome-shell[4557]: The offending signal was hit on MetaBarrier 0x564a6bb707a0.
Sep 30 18:08:54 Kevin-B350MA gnome-shell[4557]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can als>
Sep 30 18:08:54 Kevin-B350MA gnome-shell[4557]: The offending signal was hit on MetaBarrier 0x564a6b9f8e60.
Sep 30 18:08:54 Kevin-B350MA gnome-shell[4557]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can als>
Sep 30 18:08:54 Kevin-B350MA gnome-shell[4557]: The offending signal was hit on MetaBarrier 0x564a6bb707a0.

And most importantly, this, which seems to be the source of all errors (except for the PCI-e stuff):

Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Sep 30 17:55:25 Kevin-B350MA gnome-shell[3360]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed

I googled this and it seems to be a bug with Gnome 3.34, but I'm not sure. I've tried downgrading to 3.32 but am unable to since it is difficult to trawl through pacman logs and determine which packages need to be downgraded. (gdm, gnome-shell, mutter, libgdm, ???)
It also seemed that after my desktop froze, this would occur:

Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "32"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) event1  - Power Button: device removed
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "35"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) event0  - Power Button: device removed
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "36"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) event7  - Logitech Gaming Mouse G502: device removed
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "37"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "38"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) event10 - Logitech Gaming Mouse G502 System Control: device removed
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "39"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) event8  - Logitech Gaming Mouse G502 Keyboard: device removed
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "40"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) event2  - Kingston HyperX Alloy FPS Mechanical Gaming Keyboard: device removed
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "41"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) event3  - Kingston HyperX Alloy FPS Mechanical Gaming Keyboard Mouse: device removed
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "42"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) event4  - Kingston HyperX Alloy FPS Mechanical Gaming Keyboard System Control: device removed
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "43"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "44"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) event6  - Kingston HyperX Alloy FPS Mechanical Gaming Keyboard Keyboard: device removed
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "45"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) event12 - Eee PC WMI hotkeys: device removed
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "37"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) event9  - Logitech Gaming Mouse G502 Consumer Control: device removed
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (**) Option "fd" "43"
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) event5  - Kingston HyperX Alloy FPS Mechanical Gaming Keyboard Consumer Control: device removed
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) systemd-logind: got pause for 13:72
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) systemd-logind: got pause for 13:67
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) systemd-logind: got pause for 13:65
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) systemd-logind: got pause for 13:66
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) systemd-logind: got pause for 13:64
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) systemd-logind: got pause for 13:74
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) systemd-logind: got pause for 13:71
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) systemd-logind: got pause for 13:68
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) systemd-logind: got pause for 13:69
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) systemd-logind: got pause for 13:70
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) systemd-logind: got pause for 13:76
Sep 30 19:04:48 Kevin-B350MA /usr/lib/gdm-x-session[8193]: (II) systemd-logind: got pause for 13:73
Sep 30 19:04:48 Kevin-B350MA kernel: rfkill: input handler enabled

Other stuff that may be useful:

Sep 30 17:56:54 Kevin-B350MA /usr/lib/gdm-x-session[4507]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Sep 30 17:56:54 Kevin-B350MA /usr/lib/gdm-x-session[4507]: > Internal error:   Could not resolve keysym XF86MonBrightnessCycle
Sep 30 17:56:54 Kevin-B350MA /usr/lib/gdm-x-session[4507]: > Internal error:   Could not resolve keysym XF86RotationLockToggle
Sep 30 17:56:54 Kevin-B350MA /usr/lib/gdm-x-session[4507]: Errors from xkbcomp are not fatal to the X server
Sep 30 17:56:54 Kevin-B350MA /usr/lib/gdm-x-session[4507]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Sep 30 17:56:54 Kevin-B350MA /usr/lib/gdm-x-session[4507]: > Internal error:   Could not resolve keysym XF86MonBrightnessCycle
Sep 30 17:56:54 Kevin-B350MA /usr/lib/gdm-x-session[4507]: > Internal error:   Could not resolve keysym XF86RotationLockToggle
Sep 30 17:56:54 Kevin-B350MA /usr/lib/gdm-x-session[4507]: Errors from xkbcomp are not fatal to the X server

Sep 30 17:46:58 Kevin-B350MA /usr/lib/gdm-x-session[449]: (WW) Failed to open protocol names file lib/xorg/protocol.txt

Sep 30 17:46:04 Kevin-B350MA systemd[436]: gsd-media-keys.service: Triggering OnFailure= dependencies.
Sep 30 17:46:04 Kevin-B350MA systemd[436]: Requested transaction contradicts existing jobs: Transaction for gnome-session-failed.target/start is destructive (gsd-keyboard.target has 'stop' job queued, but 'start' is included in transacti>
Sep 30 17:46:04 Kevin-B350MA systemd[436]: gsd-media-keys.service: Failed to enqueue OnFailure= job, ignoring: Transaction for gnome-session-failed.target/start is destructive (gsd-keyboard.target has 'stop' job queued, but 'start' is in>
Sep 30 17:46:04 Kevin-B350MA systemd[436]: gsd-power.service: Main process exited, code=exited, status=1/FAILURE

Sep 30 17:46:04 Kevin-B350MA gsd-xsettings[520]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Sep 30 17:46:04 Kevin-B350MA unknown[511]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Sep 30 17:46:04 Kevin-B350MA unknown[518]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Sep 30 17:46:04 Kevin-B350MA unknown[509]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Sep 30 17:46:04 Kevin-B350MA gsd-color[507]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Sep 30 17:46:04 Kevin-B350MA unknown[508]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Sep 30 17:45:37 Kevin-B350MA gnome-shell[916]: ../mutter/clutter/clutter/clutter-offscreen-effect.c:225: Unable to create an Offscreen buffer
Sep 30 17:45:38 Kevin-B350MA gnome-shell[916]: ../mutter/clutter/clutter/clutter-offscreen-effect.c:225: Unable to create an Offscreen buffer
Sep 30 17:45:39 Kevin-B350MA gnome-shell[916]: ../mutter/clutter/clutter/clutter-offscreen-effect.c:225: Unable to create an Offscreen buffer
Sep 30 17:45:40 Kevin-B350MA gnome-shell[916]: ../mutter/clutter/clutter/clutter-offscreen-effect.c:225: Unable to create an Offscreen buffer
Sep 30 17:45:41 Kevin-B350MA gnome-shell[916]: ../mutter/clutter/clutter/clutter-offscreen-effect.c:225: Unable to create an Offscreen buffer
Sep 30 17:45:42 Kevin-B350MA gnome-shell[916]: ../mutter/clutter/clutter/clutter-offscreen-effect.c:225: Unable to create an Offscreen buffer
Sep 30 17:45:43 Kevin-B350MA gnome-shell[916]: ../mutter/clutter/clutter/clutter-offscreen-effect.c:225: Unable to create an Offscreen buffer
Sep 30 17:45:44 Kevin-B350MA gnome-shell[916]: ../mutter/clutter/clutter/clutter-offscreen-effect.c:225: Unable to create an Offscreen buffer
Sep 30 17:45:45 Kevin-B350MA gnome-shell[916]: ../mutter/clutter/clutter/clutter-offscreen-effect.c:225: Unable to create an Offscreen buffer
Sep 30 17:45:46 Kevin-B350MA gnome-shell[916]: ../mutter/clutter/clutter/clutter-offscreen-effect.c:225: Unable to create an Offscreen buffer
Sep 30 17:45:47 Kevin-B350MA gnome-shell[916]: ../mutter/clutter/clutter/clutter-offscreen-effect.c:225: Unable to create an Offscreen buffer

Swiggles · 2019-09-30 20:56:34

I don't think this is related to gnome, but hardware that is behaving badly. Try setting

pci=nommconf

to your kernel cmdline.

Vectorlocity · 2019-10-01 15:42:11

Swiggles wrote:

I don't think this is related to gnome, but hardware that is behaving badly. Try setting
pci=nommconf
to your kernel cmdline.

Where is the kernel cmdline? (/proc/cmdline I assume?)

Last edited by Vectorlocity (2019-10-01 15:44:46)

V1del · 2019-10-01 15:42:53

https://wiki.archlinux.org/index.php/Kernel_parameters

Swiggles · 2019-10-01 15:43:12

https://wiki.archlinux.org/index.php/Kernel_parameters

V1del was faster

Last edited by Swiggles (2019-10-01 15:43:37)

Vectorlocity · 2019-10-01 16:08:14

I've done the pci=nommconf thing. Just rebooted, so waiting to see any effect on the PCI-e errors yet.
But still a ton of this:

Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
Oct 01 16:59:26 Kevin-B350MA gnome-shell[742]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed

Here is a list of all the hits when I googled the error:
https://bbs.archlinux.org/viewtopic.php?id=249365
https://bbs.archlinux.org/viewtopic.php?id=249302
Those two were talking about adding XDG_SESSION_TYPE=x11 to ~/.xinitrc. I didn't have an .xinitrc, so I copied it from /etc/X11/xinit/xinitrc. Not sure if I'm supposed to edit that file after copying it though - could someone provide me a template that I could just add XDG_SESSION_TYPE to?
https://www.reddit.com/r/gnome/comments … yone_else/
https://bugs.archlinux.org/task/63916
https://bugs.launchpad.net/ubuntu/+sour … ug/1844509
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1678
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1681
https://github.com/micheleg/dash-to-dock/issues/987

Swiggles · 2019-10-01 17:05:03

It looks like I was wrong with my first assumption. Did you have any further PCIe errors though?

Regarding the gnome problems I think you already found some relevant topics, but the ones reported upstream are already closed as fixed. So maybe the next (arch) version fixes it. The version in testing might already contain these fixed, maybe try that?

Vectorlocity · 2019-10-01 17:30:28

Swiggles wrote:

It looks like I was wrong with my first assumption. Did you have any further PCIe errors though?
Regarding the gnome problems I think you already found some relevant topics, but the ones reported upstream are already closed as fixed. So maybe the next (arch) version fixes it. The version in testing might already contain these fixed, maybe try that?

I'll try the testing thing.
Do you have an ~/.xinitrc template I could copy from though? Just asking .
I've noticed that if I run Insurgency without just waiting for the window to pop up and instead filling my screen but then tab out of Insurgency and go to Chrome or something and wait for it to load, then it works fine. I'll try searching about Insurgency issues with freezing on the New World Interactive splash screen.

Swiggles · 2019-10-01 18:02:08

If you are using xinit it should come with a default. Copy it to home and edit away. Do you use it though and not gdm or some other display manager?

https://wiki.archlinux.org/index.php/Xinit
https://wiki.archlinux.org/index.php/GNOME#Manually

Last edited by Swiggles (2019-10-01 18:03:39)

Vectorlocity · 2019-10-01 18:34:51

Swiggles wrote:

If you are using xinit it should come with a default. Copy it to home and edit away. Do you use it though and not gdm or some other display manager?
https://wiki.archlinux.org/index.php/Xinit
https://wiki.archlinux.org/index.php/GNOME#Manually

I do use gdm.
Wait, does that mean a ~/.xinitrc is unnecessary/useless in my use case?

Swiggles · 2019-10-01 18:45:42

https://wiki.archlinux.org/index.php/Xprofile

But did you actually check if is not set?

Vectorlocity · 2019-10-01 18:52:30

Swiggles wrote:

https://wiki.archlinux.org/index.php/Xprofile
But did you actually check if is not set?

No, it is already set.

fedev · 2019-10-19 14:27:19

Were you able to figure this out? I'm getting the same issue. gnome-shell seems to be having a problem because if I kill the process, I'm able to see part of the game before steam shuts down. For me Borderlands 2 was affected. The moment the game is launched I see the windowed screen and then, instead of getting maximized, it stays black. However, the game is still running because I can hear it.

What I did to get the game to work was to try a few times. Basically I'm running the game and at the same time a timer set to 60 seconds that will kill gnome-shell unless I cancel it. After a few tries, the game starts as usual. But I do get the same error message:

gnome-shell[3507]: ../mutter/clutter/clutter/clutter-offscreen-effect.c:225: Unable to create an Offscreen buffer

Vectorlocity · 2019-10-20 21:08:41

fedev wrote:

Were you able to figure this out? I'm getting the same issue. gnome-shell seems to be having a problem because if I kill the process, I'm able to see part of the game before steam shuts down. For me Borderlands 2 was affected. The moment the game is launched I see the windowed screen and then, instead of getting maximized, it stays black. However, the game is still running because I can hear it.
What I did to get the game to work was to try a few times. Basically I'm running the game and at the same time a timer set to 60 seconds that will kill gnome-shell unless I cancel it. After a few tries, the game starts as usual. But I do get the same error message:
gnome-shell[3507]: ../mutter/clutter/clutter/clutter-offscreen-effect.c:225: Unable to create an Offscreen buffer

Tabbing out and waiting for Insurgency to load works.
I've googled the error and it seems to have been fixed in older versions but it still does appear.

Link to one of my possibly related recent threads: https://bbs.archlinux.org/viewtopic.php?id=250094

Last edited by Vectorlocity (2019-10-20 21:10:20)

Arch Linux

#1 2019-09-30 20:07:01

Gnome 3.34 bugs (?)

#2 2019-09-30 20:56:34

Re: Gnome 3.34 bugs (?)

#3 2019-10-01 15:42:11

Re: Gnome 3.34 bugs (?)

#4 2019-10-01 15:42:53

Re: Gnome 3.34 bugs (?)

#5 2019-10-01 15:43:12

Re: Gnome 3.34 bugs (?)

#6 2019-10-01 16:08:14

Re: Gnome 3.34 bugs (?)

#7 2019-10-01 17:05:03

Re: Gnome 3.34 bugs (?)

#8 2019-10-01 17:30:28

Re: Gnome 3.34 bugs (?)

#9 2019-10-01 18:02:08

Re: Gnome 3.34 bugs (?)

#10 2019-10-01 18:34:51

Re: Gnome 3.34 bugs (?)

#11 2019-10-01 18:45:42

Re: Gnome 3.34 bugs (?)

#12 2019-10-01 18:52:30

Re: Gnome 3.34 bugs (?)

#13 2019-10-19 14:27:19

Re: Gnome 3.34 bugs (?)

#14 2019-10-20 21:08:41

Re: Gnome 3.34 bugs (?)

Board footer