When I try to run any browser game, Solus crashes my computer. (Logs below)

Tom-CSTech

The title says it all. The game in this example is Gartic Phone, but any browser game I tried had the same issue. My entire computer resets. Since the apparent start of the issue involves UPower, I wonder if it's related to a separate problem, where my login screen is completely black if my graphics card is plugged in, which among other little quirks looks like a power issue. Ignore that for the instant though. Please look through the JournalCTL log provided and help me if you can. Also, I noticed I can't add a text file attachment to my post? So I guess I'll just include the full thing in the body of my post.

Dec 25 16:54:18 ███████████ one.ablaze.floorp.desktop[15747]: console.log: "NRWebScraperChild created for:" "https://garticphone.com/"
Dec 25 16:54:18 ███████████ one.ablaze.floorp.desktop[15747]: JavaScript error: , line 0: TypeError: Property 'handleEvent' is not callable.
Dec 25 16:54:18 ███████████ one.ablaze.floorp.desktop[15747]: JavaScript warning: https://garticphone.com/_next/static/chunks/main-5a52b49d694c2291.js, line 1: unreachable code after return statement -- [START OF ISSUES - JS unreachable]
Dec 25 16:54:18 ███████████ one.ablaze.floorp.desktop[15153]: console.warn: "No icon found for" "startpage"
Dec 25 16:54:18 ███████████ one.ablaze.floorp.desktop[15747]: JavaScript error: , line 0: TypeError: Property 'handleEvent' is not callable.
Dec 25 16:54:20 ███████████ one.ablaze.floorp.desktop[15153]: [Parent 2, Main Thread] WARNING: Failed to enumerate devices of org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown -- [FIRST FAILURE OUTSIDE BROWSER - Failed to enumerate upower/dbus service unknown]
Dec 25 16:54:20 ███████████ one.ablaze.floorp.desktop[15153]: : 'glib warning', file /home/runner/work/Floorp-Runtime/Floorp-Runtime/toolkit/xre/nsSigHandlers.cpp:201
Dec 25 16:54:20 ███████████ floorp[15153]: Failed to enumerate devices of org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown
Dec 25 16:54:20 ███████████ xdg-desktop-portal-gtk[4627]: Backend call failed: GDBus.Error:org.gnome.SessionManager.GeneralError: Reason not specified
Dec 25 16:54:20 ███████████ kernel: budgie-session-[3544]: segfault at 562f5f189f84 ip 00007f752dbf704d sp 00007ffe08c9dd58 error 4 in libgobject-2.0.so.0.8600.3[4804d,7f752dbbb000+48000] likely on CPU 11 (cor -- [SEGFAULT]e 5, socket 0)
Dec 25 16:54:20 ███████████ kernel: Code: 80 00 00 00 00 48 83 e0 fc eb e0 66 90 31 d2 89 d0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 48 85 ff 74 4b 48 8b 07 48 85 c0 74 43 <48> 8b 00 48 3d fc 03 00 00 77 30 48 8d15 c1 70 02 00 48 c1 e8 02
Dec 25 16:54:20 ███████████ systemd-coredump[20481]: Process 3544 (budgie-session-) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Dec 25 16:54:20 ███████████ systemd[1]: Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump.
Dec 25 16:54:20 ███████████ systemd[1]: Started systemd-coredump@0-20481-0.service - Process Core Dump (PID 20481/UID 0).
Dec 25 16:54:20 ███████████ one.ablaze.floorp.desktop[15153]: console.warn: "No icon found for" "startpage"
Dec 25 16:54:20 ███████████ systemd-coredump[20482]: Process 3544 (budgie-session-) of user 1000 dumped core.

                                                     Stack trace of thread 3544:
                                                     #0  0x00007f752dbf704d n/a (libgobject-2.0.so.0 + 0x4804d)
                                                     #1  0x00007f752dbd2b26 g_object_unref (libgobject-2.0.so.0 + 0x23b26)
                                                     #2  0x00007f752d6d61a4 n/a (libglib-2.0.so.0 + 0x771a4)
                                                     #3  0x00007f752d6da5c1 n/a (libglib-2.0.so.0 + 0x7b5c1)
                                                     #4  0x00007f752d6dfc41 n/a (libglib-2.0.so.0 + 0x80c41)
                                                     #5  0x00007f752d6e0c08 n/a (libglib-2.0.so.0 + 0x81c08)
                                                     #6  0x00007f752d6e0e77 g_main_loop_run (libglib-2.0.so.0 + 0x81e77)
                                                     #7  0x0000562872e7b47e n/a (/usr/lib64/budgie-session/budgie-session-binary + 0x947e)
                                                     #8  0x00007f752d22b529 n/a (libc.so.6 + 0x2b529)
                                                     #9  0x00007f752d22b5da __libc_start_main (libc.so.6 + 0x2b5da)
                                                     #10 0x0000562872e7bb75 n/a (/usr/lib64/budgie-session/budgie-session-binary + 0x9b75)

                                                     Stack trace of thread 3603:
                                                     #0  0x00007f752d336dad syscall (libc.so.6 + 0x136dad)
                                                     #1  0x00007f752d72582d n/a (libglib-2.0.so.0 + 0xc682d)
                                                     #2  0x00007f752d723977 n/a (libglib-2.0.so.0 + 0xc4977)
                                                     #3  0x00007f752d2a783e n/a (libc.so.6 + 0xa783e)
                                                     #4  0x00007f752d3396dc n/a (libc.so.6 + 0x1396dc)

                                                     Stack trace of thread 3605:
                                                     #0  0x00007f752d2afd22 n/a (libc.so.6 + 0xafd22)
                                                     #1  0x00007f752d2a3ab8 n/a (libc.so.6 + 0xa3ab8)
                                                     #2  0x00007f752d32ac03 ppoll (libc.so.6 + 0x12ac03)
                                                     #3  0x00007f752d6e0bdf n/a (libglib-2.0.so.0 + 0x81bdf)
                                                     #4  0x00007f752d6e0e77 g_main_loop_run (libglib-2.0.so.0 + 0x81e77)
                                                     #5  0x00007f752d980160 n/a (libgio-2.0.so.0 + 0x180160)
                                                     #6  0x00007f752d723977 n/a (libglib-2.0.so.0 + 0xc4977)
                                                     #7  0x00007f752d2a783e n/a (libc.so.6 + 0xa783e)
                                                     #8  0x00007f752d3396dc n/a (libc.so.6 + 0x1396dc)

                                                     Stack trace of thread 3604:
                                                     #0  0x00007f752d2afd22 n/a (libc.so.6 + 0xafd22)
                                                     #1  0x00007f752d2a3ab8 n/a (libc.so.6 + 0xa3ab8)
                                                     #2  0x00007f752d32ac03 ppoll (libc.so.6 + 0x12ac03)
                                                     #3  0x00007f752d6e0bdf n/a (libglib-2.0.so.0 + 0x81bdf)
                                                     #4  0x00007f752d6e1025 n/a (libglib-2.0.so.0 + 0x82025)
                                                     #5  0x00007f752d723977 n/a (libglib-2.0.so.0 + 0xc4977)
                                                     #6  0x00007f752d2a783e n/a (libc.so.6 + 0xa783e)
                                                     #7  0x00007f752d3396dc n/a (libc.so.6 + 0x1396dc)

                                                     Stack trace of thread 3607:
                                                     #0  0x00007f752d2afd22 n/a (libc.so.6 + 0xafd22)
                                                     #1  0x00007f752d2a3ab8 n/a (libc.so.6 + 0xa3ab8)
                                                     #2  0x00007f752d32ac03 ppoll (libc.so.6 + 0x12ac03)
                                                     #3  0x00007f752d6e0bdf n/a (libglib-2.0.so.0 + 0x81bdf)
                                                     #4  0x00007f752d6e0cf8 g_main_context_iteration (libglib-2.0.so.0 + 0x81cf8)
                                                     #5  0x00007f752b4c78de n/a (libdconfsettings.so + 0xb8de)
                                                     #6  0x00007f752d723977 n/a (libglib-2.0.so.0 + 0xc4977)
                                                     #7  0x00007f752d2a783e n/a (libc.so.6 + 0xa783e)
                                                     #8  0x00007f752d3396dc n/a (libc.so.6 + 0x1396dc)
                                                     ELF object binary architecture: AMD x86-64
Dec 25 16:54:20 ███████████ org.kde.discover.notifier.desktop[4389]: ICE default IO error handler doing an exit(), pid = 4389, errno = 11
Dec 25 16:54:20 ███████████ kernel: rfkill: input handler enabled
Dec 25 16:54:20 ███████████ pia-client.desktop[4399]: ICE default IO error handler doing an exit(), pid = 4399, errno = 0
Dec 25 16:54:20 ███████████ systemd[1]: systemd-coredump@0-20481-0.service: Deactivated successfully.
Dec 25 16:54:20 ███████████ lightdm[2939]: pam_unix(lightdm:session): session closed for user ████
Dec 25 16:54:20 ███████████ org.buddiesofbudgie.BudgieWm.desktop[3802]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Dec 25 16:54:20 ███████████ systemd[1]: systemd-coredump@0-20481-0.service: Consumed 71ms CPU time, 76.6M memory peak.
Dec 25 16:54:20 ███████████ budgie-daemon[4160]: statusnotifier.vala:127: Received unregister request for item with service=:1.87, path=/StatusNotifierItem, name=:1.87, sender=:1.87
Dec 25 16:54:20 ███████████ budgie-daemon[4160]: statusnotifier.vala:130: Unregistering item with service=:1.87, path=/StatusNotifierItem, name=:1.87, sender=:1.87
Dec 25 16:54:20 ███████████ DiscoverNotifier[4389]: QThreadStorage: entry 6 destroyed before end of thread 0x55aa2bf40330
Dec 25 16:54:20 ███████████ DiscoverNotifier[4389]: QThreadStorage: entry 2 destroyed before end of thread 0x55aa2bf40330
Dec 25 16:54:20 ███████████ DiscoverNotifier[4389]: QThreadStorage: entry 1 destroyed before end of thread 0x55aa2bf40330
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3608 (gsd-usb-protect) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3611 (gsd-rfkill) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3614 (gsd-xsettings) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3619 (gsd-color) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3624 (gsd-screensaver) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3632 (gsd-datetime) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3638 (gsd-sharing) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3641 (gsd-a11y-settin) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3647 (gsd-housekeepin) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3650 (gsd-smartcard) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3653 (gsd-wwan) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3666 (gsd-keyboard) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3675 (bsd-media-keys) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3683 (gsd-sound) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3690 (gsd-print-notif) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3703 (bsd-power) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3802 (budgie-wm) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3834 (ibus-daemon) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3835 (budgie-panel) with signal SIGTERM.
Dec 25 16:54:20 ███████████ org.buddiesofbudgie.SettingsDaemon.XSettings.desktop[3614]: XIO:  fatal IO error 4 (Interrupted system call) on X server ":0"
Dec 25 16:54:20 ███████████ org.buddiesofbudgie.SettingsDaemon.XSettings.desktop[3614]:       after 26 requests (26 known processed) with 1 events remaining.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3854 (ibus-dconf) with signal SIGTERM.
Dec 25 16:54:20 ███████████ at-spi2-registryd[3773]: X connection to :0 broken (explicit kill or server shutdown).
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3855 (ibus-extension-) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3857 (ibus-x11) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3887 (gsd-printer) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 3899 (ibus-engine-sim) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4160 (budgie-daemon) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4161 (budgie-polkit-d) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4388 (org.buddiesofbu) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4392 (budgie-screensa) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4395 (applet.py) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4399 (pia-client) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4402 (org.buddiesofbu) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4404 (budgie-power-di) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4408 (agent) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4411 (evolution-alarm) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4413 (nm-applet) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[3524]: dbus-:1.8-org.a11y.atspi.Registry@0.service: Main process exited, code=exited, status=1/FAILURE
Dec 25 16:54:20 ███████████ systemd[3524]: dbus-:1.8-org.a11y.atspi.Registry@0.service: Failed with result 'exit-code'.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4566 (bwrap) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4567 (bwrap) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 4569 (glycin-image-rs) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 13438 (bwrap) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 13441 (bwrap) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 13443 (glycin-image-rs) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 14011 (bwrap) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 14012 (bwrap) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 14013 (glycin-image-rs) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 20501 (bwrap) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 20502 (bwrap) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Killing process 20506 (bwrap) with signal SIGTERM.
Dec 25 16:54:20 ███████████ systemd[1]: Stopping session-2.scope - Session 2 of User ████... -- [SHUTTING DOWN USER SESSION]
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) event1  - Power Button: device removed
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) event2  - Video Bus: device removed -- [SCREEN GOES BLACK]
Dec 25 16:54:20 ███████████ polkitd[844]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.73, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_CA.utf8) (disconnected from bus)
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/ldac
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSink/aptx_hd
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/aptx_hd
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSink/aptx
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/aptx
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSink/aac
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/aac
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSink/opus_g
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/opus_g
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSink/sbc
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/sbc
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/faststream
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/faststream_duplex
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSink/opus_05
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/opus_05
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Dec 25 16:54:20 ███████████ bluetoothd[842]: Endpoint unregistered: sender=:1.69 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Dec 25 16:54:20 ███████████ systemd[3524]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Dec 25 16:54:20 ███████████ systemd[3524]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Dec 25 16:54:20 ███████████ systemd[3524]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
Dec 25 16:54:20 ███████████ systemd[3524]: gnome-terminal-server.service: Failed with result 'exit-code'.
Dec 25 16:54:20 ███████████ systemd[3524]: gnome-terminal-server.service: Consumed 1.290s CPU time, 25.1M memory peak.
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) event0  - Power Button: device removed
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) event3  - TKC Portico75: device removed
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) event5  - TKC Portico75 System Control: device removed
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) event7  - TKC Portico75 Keyboard: device removed
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) event4  - TKC Portico75 Mouse: device removed
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Deactivated successfully.
Dec 25 16:54:20 ███████████ systemd[1]: Stopped session-2.scope - Session 2 of User ████.
Dec 25 16:54:20 ███████████ systemd[1]: session-2.scope: Consumed 12.326s CPU time, 723.7M memory peak.
Dec 25 16:54:20 ███████████ systemd-logind[848]: Removed session 2.
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) event8  - Logitech M720 Triathlon: device removed
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) event6  - TKC Portico75 Consumer Control: device removed -- [LAST DEVICE REMOVED]
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) UnloadModule: "libinput"
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) UnloadModule: "libinput"
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) UnloadModule: "libinput"
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) UnloadModule: "libinput"
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) UnloadModule: "libinput"
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) UnloadModule: "libinput"
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) UnloadModule: "libinput"
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) UnloadModule: "libinput"
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) UnloadModule: "libinput"
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) UnloadModule: "libinput"
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) UnloadModule: "libinput"
Dec 25 16:54:20 ███████████ one.ablaze.floorp.desktop[15818]: Exiting due to channel error.
Dec 25 16:54:20 ███████████ one.ablaze.floorp.desktop[15747]: Exiting due to channel error.
Dec 25 16:54:20 ███████████ one.ablaze.floorp.desktop[15911]: Exiting due to channel error.
Dec 25 16:54:20 ███████████ one.ablaze.floorp.desktop[15705]: Exiting due to channel error.
Dec 25 16:54:20 ███████████ one.ablaze.floorp.desktop[15483]: Exiting due to channel error.
Dec 25 16:54:20 ███████████ one.ablaze.floorp.desktop[15442]: Exiting due to channel error.
Dec 25 16:54:20 ███████████ one.ablaze.floorp.desktop[15672]: Exiting due to channel error.
Dec 25 16:54:20 ███████████ one.ablaze.floorp.desktop[20431]: Exiting due to channel error.
Dec 25 16:54:20 ███████████ one.ablaze.floorp.desktop[15368]: Exiting due to channel error.
Dec 25 16:54:20 ███████████ one.ablaze.floorp.desktop[15290]: Exiting due to channel error.
Dec 25 16:54:20 ███████████ systemd[3524]: Starting xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)...
Dec 25 16:54:20 ███████████ systemd[3524]: app-flatpak-io.github.milkshiift.GoofCord-8977.scope: Consumed 55.036s CPU time, 1.1G memory peak.
Dec 25 16:54:20 ███████████ systemd[3524]: app-flatpak-one.ablaze.floorp-15110.scope: Consumed 31.002s CPU time, 1.4G memory peak.
Dec 25 16:54:20 ███████████ xdg-desktop-portal-gtk[20571]: cannot open display: :0
Dec 25 16:54:20 ███████████ systemd[3524]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE -- [MAIN PROCESS EXIT COMPLETE]
Dec 25 16:54:20 ███████████ systemd[3524]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Dec 25 16:54:20 ███████████ systemd[3524]: Failed to start xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
Dec 25 16:54:20 ███████████ xserver-wrapper[1052]: (II) Server terminated successfully (0). Closing log file. -- [LOGGING END]

Staudey

Seems like there are a number of issues with firefox crashing on Budgie after the most recent rounds of updates.

e.g.
https://github.com/BuddiesOfBudgie/budgie-desktop/issues/783
https://github.com/getsolus/packages/issues/7440

When you say your "entire computer resets" though it sounds like it doesn't just kick you to the login screen but it actually restarts the PC or something?

Tom-CSTech

Staudey That's actually a fuzzy question, honestly. Because per the logs, all my hardware devices disconnect (keyboard, video bus, and even... my power button???) which feels like a full reset operation. And of course when I go back in, it starts with the characteristic lag (and lack of open windows) of starting up from shutdown, although I'm not sure if a simple logout does the same. Either way, that hardware stuff is weird. But on the other hand, it does seem not to be a full reset, because, well there's this bug I've got (that already filed with Discover's bug forum, not relevant here) where I can only open Discover a single time per login -- if I close it, I have to restart my computer to open it again. And in the case of this here issue, I am not actually able to open it again. That means there is some way in which it is not, actually, a full reset. So, I leave that to more professional minds to judge what it means.

penny-farthing

Tom-CSTech

well there's this bug I've got (that already filed with Discover's bug forum, not relevant here) where I can only open Discover a single time per login -- if I close it, I have to restart my computer to open it again.

While you are waiting for a solution about Discover, if you need to relaunch it in your session, try these terminal commands that were suggested to me by @MikeK61 :

pkill plasma-discover
plasma-discover --backends packagekit,snap,fwupd,flatpak

That should work.

Tom-CSTech

Yep, I've just checked, and a logout does very little of what's in that crash log, including not having any device disconnections. But obviously there's a way in which it's different from a full restart, so I'm not sure what that might be.

Tom-CSTech

I'm going to test a soft restart now.

Tom-CSTech

Okay, I tried both a soft and a hard reset. A hard reset apparently isn't detected by the system, makes sense if it's effectively just cut power, can't run journalctl daemon without power. Soft reset though also doesn't disconnect the devices, apparently. I'm going to try a soft shutdown, since a reset does come with an implication of the user using the same devices again (otherwise they would've disconnected them manually). A shutdown shouldn't carry that assumption.

Tom-CSTech

penny-farthing By the way, I've tried this out, and it works to temporarily use Discover. It doesn't fix the opening via icon, nor does it show the menu in the bottom left for viewing ongoing installs, but it does let Discover open and behave mostly normal again. You've helped me to add new info to my bug post in that forum, thank you. If you're interested, here is that link: https://bugs.kde.org/show_bug.cgi?id=513569

Tom-CSTech

Okay, so I've done a soft and hard restart, and none of them include device disconnections (a hard restart appears to be a power interruption -- journalctl can't even log anything and ends abruptly -- meanwhile, a soft reset keeps devices and hardware services alive).

But a soft SHUTDOWN does, as one would expect, disconnect devices. But there's a whole lot more that happens in a shutdown, per the logs I'm investigating now. So my crash is something like a logout, and something like a shutdown, but is neither of those two things.

I hope this information is helpful.

TraceyC

ℹ Moderator Note
We request that in Support, users stick to one topic per thread and create new threads for different issues.
This keeps questions and solutions clear, both for you and for other members of the forum.
If you want to discuss the Discover issue further, please create a new thread. Thanks.

P.S. The Discover issue is listed in our Known Issues. It has a link to the main upstream bug and the workaround.

TraceyC

The relevant part of the stack trace is this

Dec 25 16:54:20 ███████████ systemd-coredump[20482]: Process 3544 (budgie-session-) of user 1000 dumped core.

                                                     Stack trace of thread 3544:
                                                     #0  0x00007f752dbf704d n/a (libgobject-2.0.so.0 + 0x4804d)
                                                     #1  0x00007f752dbd2b26 g_object_unref (libgobject-2.0.so.0 + 0x23b26)
                                                     #2  0x00007f752d6d61a4 n/a (libglib-2.0.so.0 + 0x771a4)
                                                     #3  0x00007f752d6da5c1 n/a (libglib-2.0.so.0 + 0x7b5c1)
                                                     #4  0x00007f752d6dfc41 n/a (libglib-2.0.so.0 + 0x80c41)
                                                     #5  0x00007f752d6e0c08 n/a (libglib-2.0.so.0 + 0x81c08)
                                                     #6  0x00007f752d6e0e77 g_main_loop_run (libglib-2.0.so.0 + 0x81e77)
                                                     #7  0x0000562872e7b47e n/a (/usr/lib64/budgie-session/budgie-session-binary + 0x947e)
                                                     #8  0x00007f752d22b529 n/a (libc.so.6 + 0x2b529)
                                                     #9  0x00007f752d22b5da __libc_start_main (libc.so.6 + 0x2b5da)
                                                     #10 0x0000562872e7bb75 n/a (/usr/lib64/budgie-session/budgie-session-binary + 0x9b75)

This is Budgie crashing, which is what causes the session reset. This is indeed the crash caused by scrolling in Firefox. There is an issue open in the Budgie tracker for it, you'll need to wait for them to fix it.

Tom-CSTech

TraceyC It's strange, since I have no issues with Firefox (or forks) crashing due to scrolling, but I do have this one about the browser games crashing things. That said, if the stacktrace tells us it's actually the same issue, then I'll be glad that we're tackling too birds with one stone.