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

  • river_chunk@lemmy.world
    1·
    6 days ago

    What about dmesg? if it’s a hardware problem (and it looks like, but I may wrong) dmesg will print some usefull data

    sudo dmesg -Tw

    -T form human redeable timestamp and -w to follow (like tail -f)

    Also, about that hard reset that you did, Linux magic keys are your friends if your are not facing a kernel panic, I have this key combo engraved in my head like a rune:

    Press and hold Alt + PrtSc (not Alt+Gr) and then press only one time each (and while holding Alt + PrtSc) E + I + S + U + B

    PrtSc maybe be SysRq in your keyboard depends on the manufacturer, architecture or how old it is. Also wait one or two seconds between keys when pressing EISUB.

    Edit: the rune in my head was wrong, fixed it

    • Artemis_MystiqueOP
      1·
      6 days ago

      What about dmesg? if it’s a hardware problem (and it looks like, but I may wrong) dmesg will print some usefull data

      I tried sysrq then, now i know why it didn’t work sysrq: This sysrq operation is disabled.

      nothing useful in dmesg, at least to me

      • river_chunk@lemmy.world
        1·
        6 days ago

        Looks like SysRq keys are not enable in your distro by default, don’t know the reason but Fedora kernel devs would known better than me.

        Just for curious, did you installed some gnome extension recently? try this

        grep -i gnome-shell /var/log/syslog* | grep -i exten
        • Artemis_MystiqueOP
          1·
          6 days ago

          there are gnome extensions but they were installed over a year ago and have been disabled for more than 6 months

          grep: /var/log/syslog*: No such file or directory

          I am getting this error but yes there were some JS errors that I attribute to extensions like

          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