Severe Freeze Upon Re-Entry

[KoshulaDora]

Niri causes a freeze upon re-entry from display manager. The degree of freeze is so severe that none of tty can be called up on with alt+ctrl+f1-6. Nothing moves. Nothing shows. Nothing functions. You will have to force reboot the pc if you want to keep using it.

System Information

• niri version: niri 0.1.9 (unknown commit)
• Distro: ArchLinux
• GPU: AMD rx 590
• CPU: Amd Ryzen 5800x

Additional Info

• Display manager: Lightdm

This issue doesn't happen with hyprland, sway, i3, or any other wm.

[YaLTeR]

Does it unfreeze after 20 or so seconds? Does it happen at initial niri startup?

I will need niri output during the freeze: journalctl --user-unit=niri

[KoshulaDora]

Does it unfreeze after 20 or so seconds? Does it happen at initial niri startup?

Sometimes? Typically when I make a clean move from logging into my default x11 wm and try to move to niri it works, but after trying to get back to niri it tends to freeze. It never unfreezes after a while.

I will need niri output during the freeze: journalctl --user-unit=niri

I am sorry, the text is far too big so I created a gist and linked it. Will that be fine?

[YaLTeR]

That's quite weird. Seems that niri doesn't get the permission to the DRM device after the session is restored.

Could you check if the same issue happens in COSMIC with cosmic-comp?

[KoshulaDora]

Could you check if the same issue happens in COSMIC with cosmic-comp?

Kind of? I can still use the tty in Cosmic, so it isn't the same kind of freeze, and the cursor actually shows and blinks. Here is the relevant but unsolved issue.

Here are the outputs of journalctl --user _EXE=/usr/bin/cosmic-comp and journalctl --user _EXE=/usr/bin/cosmic-session, respectively:

Sep 28 20:36:27 archlinux cosmic-comp[5559]: Failed to read config 'workspaces'
Sep 28 20:36:27 archlinux cosmic-comp[5559]: failed to read local shortcuts config 'system_actions': NoConfigDirectory
Sep 28 20:36:27 archlinux cosmic-comp[5559]: Key-Binding 'Period' only matched case insensitive for "period"
Sep 28 20:36:27 archlinux cosmic-comp[5559]: Key-Binding 'Comma' only matched case insensitive for "comma"
Sep 28 20:36:27 archlinux cosmic-comp[5559]: Key-Binding 'Period' only matched case insensitive for "period"
Sep 28 20:36:27 archlinux cosmic-comp[5559]: Key-Binding 'Comma' only matched case insensitive for "comma"
Sep 28 20:36:27 archlinux cosmic-comp[5559]: shortcuts custom config error: GetKey("custom", Os { code: 2, kind: NotFound, message: "No such file or directory" })
Sep 28 20:36:27 archlinux cosmic-comp[5559]: tiling exceptions custom config error: GetKey("tiling_exception_custom", Os { code: 2, kind: NotFound, message: "No such file or directory" })

sep 28 20:36:27 archlinux cosmic-session[5553]: starting cosmic-session
sep 28 20:36:27 archlinux cosmic-session[5553]: starting process ' cosmic_session_sock=12 cosmic-comp '
sep 28 20:36:27 archlinux cosmic-session[5553]: process ' cosmic_session_sock=12 cosmic-comp ' failed with code 1
sep 28 20:36:27 archlinux cosmic-session[5553]: cosmic-comp exited with error code 1
sep 28 20:36:27 archlinux cosmic-session[5553]: draining stdin receiver before restarting process
sep 28 20:36:27 archlinux cosmic-session[5553]: sleeping for 6ms before restarting process cosmic-comp (restart 0)
sep 28 20:36:27 archlinux cosmic-session[5553]: restarted process ' cosmic_session_sock=12 cosmic-comp ', now at 1 restarts
sep 28 20:36:27 archlinux cosmic-session[5553]: process 'processkey(1v1)' cancelled

Overall this issue seems to be very unrelated however, and I don't have anywhere near enough time or interest in trying to get cosmic run properly.

[YaLTeR]

I'd need help from someone more experienced with DRM for this one. Don't know what can cause this issue to happen. It's as if Lightdm doesn't release the DRM device for niri. It also for some reason leaves DISPLAY set, does it know that niri is a Wayland compositor?

[KoshulaDora]

I'd need help from someone more experienced with DRM for this one. Don't know what can cause this issue to happen. It's as if Lightdm doesn't release the DRM device for niri. It also for some reason leaves DISPLAY set, does it know that niri is a Wayland compositor?

Oh you don't need to worry about that, the display is my config issue, I forgot to disable it after removing xwayland satelite from startup.

The bug is still reproduced with that config removed.