Niri: Random reboots and after suspend my display goes red

Ask Fedora
, , , , ,
1

I am fairly new to Linux in general and opted for Fedora Workstation 43 and was using GNOME fine without issues but wanted to try out Niri. I have these random complete reboots which from reading around could be related to GPU? Also after a suspend I closed the laptop and opened it and was greeted with the login lock screen then when I turned on my second monitor the screens went red.

I had to boot into a tty to reboot.

I have looked around this forum and also other forums and am finding it quite difficult to troubleshoot. I suspected it could be related to the Nvidia drivers not being installed correctly. So followed the Howto/NVIDIA - RPM Fusion guide.

What would be the best way to pin point what is causing these reboots?

I have used LLM’s to further trouble shoot when not able to find any other people with the same issue online. Mainly for how to check logs etc.

Already Checked:

  • No kernel panics found with journalctl -b -1 | grep -i panic - only shows normal drm panic registration, no actual panics.
  • No OOM (Out of Memory) kills with journalctl -b -1 | grep -i "killed process" - nothing found
  • No hardware errors in dmesg - dmesg | grep -i error shows only minor issues (RAS correctable errors, UVC probe control failure)
  • Logs end abruptly with no errors, system just stops logging, suggesting hard lockup rather than kernel panic
  • System runs for variable periods anywhere from minutes to 3+ hours before crash
  • Crashes/reboots during normal use and on suspend/resume particularly when waking from suspend + connecting second monitor

Hardware Context:

  • Laptop with hybrid graphics (Intel Iris Xe integrated + Nvidia RTX A500 discrete)
  • Display physically connected to Intel GPU (Nvidia shows Disp.A Off in nvidia-smi)
  • Fedora Workstation 43, kernel 6.17.12
  • Using niri Wayland compositor
  • Nvidia driver version 580.119.02 (proprietary, from RPM Fusion)

If I need to provide any further information please let me know, as I said I am pretty new to this but have worked with the command line in my job so don’t have an issue navigating from there.

2

Just to clarify - none of these issues happen on GNOME, only on Niri?

3

Yes that is correct only on Niri. I’m booting into Niri through GDM also not sure if that makes any difference.

1 Like
4

Are you booting into Niri from within Gnome, from the command line, or from a login manager?

Searching, I find Red Screen after some idle time. Device is inactive. · Issue #1748 · YaLTeR/niri · GitHub which indicates a Niri issue with some screen lockers.

As Niri is still quite new, and as Journalctl is not showing you any errors, I would suggest also posting an issue on their GitHub.

5

Cool, thanks for clarifying. I took the liberty of editing the post title so that it might catch the eye of anyone that knows Niri.

1 Like
7

I am booting into Niri with GDM. I did read about this issue and the red screen is less of a worry than the random reboots, as I could be in the middle of doing some work and it just goes black.

Obviously would like to fix both of these. I am using Noctalia shell which is based on Quickshell opposed to Sway I am not sure if that would make a difference as this screen lock does not come default with Niri.

I’ll post an issue in their GitHub and see if I can get help there. Thanks

1 Like
8

For troubleshooting, I would remove the screen-locker. See how it goes for a day or two.

GDM should be fine, but with Sway WM I launch direct from a console TTY. However if GDM launches Niri, I could not explain why GDM would be a problem.