1.Upgrade from Fedora 37 to Fedora 38 2.The really bad stuff started when I went from initramfs-6.3.8-200.fc38.x86_64 to initramfs-6.3.11-200.fc38.x886_64 3.I started using Fedora Core 2 and have been using it consistently to the present. Debian is looking really appealing to me right now. Reproducible: Steps to Reproduce: 1.Upgrade from Fedora 37 to Fedora 38 2.The really bad stuff started when I went from kernel 6.3.8-200.fc38.x86_64 to 6.3.11-200.fc38.x86_64 3.I started using Fedora Core 2 and have been using it consistently to the present. Debian is looking really appealing to me right now. Kernel 6.3.11-200 has introduced instabilities to otherwise stable computers that have been running Fedora for years. The problem is the lack of information about kernel changes. Better documentation about kernel changes will help. The mandatory 15 minute suspend that was introduced with the change from Fedora 37 to Fedora 38 has me keeping some computers at Fedora 37 until I can find a workable solution to avoid a mandatory suspend.
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/. This issue should only be kept open if it: 1. Relates to Fedora packaging or integration with other Fedora components 2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions If this issue isn't needed for either of these two reasons, please: * create an issue with GNOME * add a link to the GNOME issue here * close this issue as CLOSED/UPSTREAM Thank you!
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.