Suspend Function Causes Automatic Restart on Fedora Xfce 43 Spin

Ask Fedora
1

Dear Technical Support Team,

I am writing to report an issue I am currently experiencing with the suspend functionality on Fedora Xfce 43 Spin.

Whenever I click the “Suspend” option, the system initially appears to enter suspend mode as expected. However, instead of remaining in suspend, the computer automatically restarts on its own. This behavior occurs consistently and prevents normal use of the suspend feature.

I would like to understand why this issue is occurring and whether there is a recommended fix or workaround available. Additionally, I would like to know if this is a known issue with Fedora Xfce 43 Spin or if it may be related to specific system configurations or hardware compatibility.

For reference, I was previously using Fedora 40 on the same system, and the suspend functionality worked without any issues.

Please let me know if you require any additional system logs, hardware specifications, or diagnostic details to help investigate this issue. I would be happy to provide further information if needed.

Thank you for your time and assistance. I look forward to your guidance on resolving this matter.

Best regards,
Nagarjun

2

Suspend has been the biggest problem I’ve had with Fedora (though not likely Fedora specific) and you’ll find lots of others also having issues with it if you search this forum. It works for a while then breaks again, then works for a while, etc. There are a few things you can try that might help and will give people here more info. Suspend issues tend to be very hardware specific, so:

  1. Please update your system BIOS to the latest to see if anything has been fixed.
  2. Please post the output of “inxi -Fzxx” here using the pre-formatted text </> button above. If it tells you command not found, then you may install it first with “sudo dnf install inxi”. This will tell us what hardware you have.
  3. If you haven’t already, make sure you’ve updated Fedora recently “sudo dnf update”.
  4. After your system reboots, you can type “journalctl -b -1” to look at logs from the previous boot. Look for any errors.