(Some) Flatpaks kill the machine on F31SB Beta/Testing

Project Discussion
1

For now, I found 2 that are making the system unresponsive (Discord(flathub), MellowPlayer).
System crashes before the app window is shown.

rpm-ostree status
State: idle
AutomaticUpdates: disabled
Deployments:
● ostree://fedora:fedora/31/x86_64/testing/silverblue
                   Version: 31.20190929.0 (2019-09-29T00:42:12Z)
                BaseCommit: 69782add567c70cafba33a17287a6a8351ede05625e57f2687b13e5ea383dced
              GPGSignature: Valid signature by 7D22D5867F2A4236474BF7B850CB390B3C3359C4
           LayeredPackages: fedora-workstation-repositories file-roller gnome-tweaks htop inxi jq kernel-tools
                            lm_sensors tuned-utils vim

journal:

Oct 01 07:02:01 traken systemd[1220]: Started Portal service (GTK+/GNOME implementation).
Oct 01 07:02:02 traken systemd[1220]: Started Multimedia Service.
Oct 01 07:02:02 traken rtkit-daemon[1105]: Successfully made thread 12771 of process 12770 (/usr/bin/pipewire) owned by '1000' RT at priority 20.
Oct 01 07:02:02 traken rtkit-daemon[1105]: Supervising 8 threads of 2 processes of 1 users.
Oct 01 07:02:02 traken pipewire[12770]: [E][v4l2-utils.c:91 spa_v4l2_open()] v4l2: /dev/video5 is no video capture device
Oct 01 07:02:02 traken pipewire[12770]: [E][v4l2-utils.c:91 spa_v4l2_open()] v4l2: /dev/video1 is no video capture device
Oct 01 07:02:02 traken pipewire[12770]: [E][v4l2-utils.c:91 spa_v4l2_open()] v4l2: /dev/video3 is no video capture device
Oct 01 07:02:02 traken xdg-desktop-por[12756]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed
Oct 01 07:02:02 traken systemd[1220]: Started Portal service.
Oct 01 07:02:03 traken gnome-shell[1862]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.130/StatusNotifierItem
Oct 01 07:02:03 traken systemd[1]: Starting Hostname Service...
Oct 01 07:02:04 traken gnome-shell[1862]: [AppIndicatorSupport-FATAL] unable to update overlay icon
Oct 01 07:02:04 traken gnome-shell[1862]: [AppIndicatorSupport-FATAL] unable to update overlay icon
Oct 01 07:02:04 traken gnome-shell[1862]: [AppIndicatorSupport-FATAL] unable to update overlay icon
Oct 01 07:02:04 traken kernel: gmc_v9_0_process_interrupt: 59 callbacks suppressed
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:3 pasid:32769, for process gnome-shell pid 1862 thread gnome-shel:cs0 pid 1900)
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0:   in page starting at address 0x0000000102c20000 from 27
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:3 pasid:32769, for process gnome-shell pid 1862 thread gnome-shel:cs0 pid 1900)
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0:   in page starting at address 0x0000000102c20000 from 27
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:3 pasid:32769, for process gnome-shell pid 1862 thread gnome-shel:cs0 pid 1900)
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0:   in page starting at address 0x0000000102c20000 from 27
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:3 pasid:32769, for process gnome-shell pid 1862 thread gnome-shel:cs0 pid 1900)
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0:   in page starting at address 0x0000000102c20000 from 27
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:3 pasid:32769, for process gnome-shell pid 1862 thread gnome-shel:cs0 pid 1900)
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0:   in page starting at address 0x0000000102c20000 from 27
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:3 pasid:32769, for process gnome-shell pid 1862 thread gnome-shel:cs0 pid 1900)
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0:   in page starting at address 0x0000000102c20000 from 27
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:3 pasid:32769, for process gnome-shell pid 1862 thread gnome-shel:cs0 pid 1900)
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0:   in page starting at address 0x0000000102c20000 from 27
Oct 01 07:02:04 traken kernel: amdgpu 0000:06:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
.
.
.
and spam of those amdgpu error lines

Now the bigboys question:
Where can I file/search for bug? Is this flatpak or kernel (gpu) bug?

2

This definitely seems like a kernel bug… A quick google shows some people saying a bios update helps. Could you try that instead?

3

Just tried with september bios update, no luck.

4

Found the solution with help of cool people on IRC. Mesa 19.2 doesn’t like Mesa inside 18.08 sandbox, building the app against 19.08 fixes the problem

1 Like