So I have a new installation of fedora, which I reinstalled because gdm would freeze and prevent me from logging in and using my computer. I then noticed the same problem on the new installation. I noticed that using an older kernel worked, but system upgrades will break gdm again. I don’t want to have to never update my system. New distro? Suggestions to fix this? I ideally want an relatively bleeding edge distro.

  • Throwaway1234@sh.itjust.works
    5·
    9 months ago

    A quick search revealed that others have experienced issues that may be related. In order to disclose that this is different from the issue reported by others, please consider the following:

    After updating to the latest kernel, shut off instead of reboot. After which you turn your device back on. If strict adherence to ‘rebooting’ like this prevents the issue from coming up, then it’s likely the aforementioned known issue with the latest generation of AMD GPUs and recent kernel updates.

    Please consider to report back on your findings.

    • Lime66@lemmy.worldOP
      2·
      9 months ago

      I’ve tried rebooting it like that. I have a latest gen and GPU so that may be it

      • Throwaway1234@sh.itjust.works
        1·
        9 months ago

        Thank you for the reply!

        I’ve tried rebooting it like that.

        And…, what’s the result? Does the problem persist? Or is it resolved? (Under strict adherence to rebooting as described*)

          • Throwaway1234@sh.itjust.works
            2·
            8 months ago

            Alright. Thank you for reporting back!

            Uhmm…, so, the good thing is that it’s reproducible, a bug report has already been issued for it and should (therefore) eventually get a fix in upstream. The bad news, however, is that you may experience the same issue on every other relatively bleeding edge distro until then… But, there are two ways around it:

            1. Just reboot by shutting off 🤣.
            2. Or…, switch to Nobara. Some users reported the bug to its maintainer and they’ve fixed the issue on Nobara since. It’s conceivable that the fix may already be found on other distros as well, but it’s definitely fixed on Nobara. Thankfully, Nobara is based on Fedora. So you shouldn’t feel too far away from home ;).