I have been facing this issue since yesterday, but basically at some point the system becomes insanely slow, and the restart and shutdown options disappear from the menu, tty3-7 dont work, it freezes at the shutdown -now command(at which point I just manually cut the power(bad Idea I know)),

but today I stuck around as my system got insanely borked, eventually freezing up and giving me the screen above. the problem shows up after I wake it up from suspend but not always: My system specs:

OS: Fedora Linux 41 (Workstation Edition) x86_64 
Host: TECRA R940 PT439V-03U02WAR 
Kernel: 6.11.10-300.fc41.x86_64 
Uptime: 23 mins 
Packages: 2282 (rpm), 43 (flatpak) 
Shell: bash 5.2.32 
Resolution: 1600x900 
DE: GNOME 47.1 
WM: Mutter 
WM Theme: Adwaita 
Theme: Adwaita [GTK2/3] 
Icons: Adwaita [GTK2/3] 
Terminal: gnome-terminal 
CPU: Intel i7-3540M (4) @ 3.700GHz 
GPU: AMD ATI Radeon HD 7550M/7570M/7650M 
Memory: 1845MiB / 7879MiB 

here are the journalctl entries that I think are relevant

entries for events 40 min before that.

and this is from when it happened earlier in the day

    • Artemis_Mystique@lemmy.mlOP
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      18 days ago

      LightDM last stable release was 2 years ago, are there any other options available?? going through journalctl entries these seem to popout to me Vulkan: ../src/amd/vulkan/radv_physical_device.c:1984: Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)

      JS ERROR: TypeError: this.actor is null
                                                _syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:144:25
                                                onStopped@resource:///org/gnome/shell/ui/windowManager.js:161:35
                                                _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                                _easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:247:60
                                                _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1611:21
                                                onStopped@resource:///org/gnome/shell/ui/windowManager.js:1579:39
                                                _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                                _easeActor/<@resource:///org/gnome/shell/ui/environment.js:160:64
                                                @resource:///org/gnome/shell/ui/init.js:21:20
      
      
      • Botzo@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        18 days ago

        Not sure if this the display manager is the issue, but SDDM is the other “big player”.