On 2025-03-04 21:36, Tobias Heider wrote:
On Tue, Mar 04, 2025 at 09:27:02PM GMT, Volker Schlecht wrote:
On 2025-03-04 17:13, Tobias Heider wrote:
> here is a new port for niri [1], a scrollable-tiling Wayland compositor
> heavily inspired by the PaperWM extension for Gnome.

Very cool, unfortunately it doesn't start here. My first guess would be a
permission issue, but sway starts without a problem.

Here's what I get, and then it hangs:

2025-03-04T20:03:38.428046Z  INFO niri: 
starting version 25.02 (unknown commit)
2025-03-04T20:03:38.486812Z DEBUG niri_config: loaded config 
from "<VALID PATH TO VALID CONFIG>"
2025-03-04T20:03:38.549308Z  WARN 
niri::backend::tty: error getting the render node for the 
primary GPU; proceeding anyway
2025-03-04T20:03:38.549328Z  INFO niri::backend::tty: 
using as the render node: "/dev/dri/card0"
2025-03-04T20:03:38.691720Z DEBUG niri::backend::tty: 
device added: 22272 "/dev/dri/card0"
2025-03-04T20:03:38.691779Z  WARN 
niri::backend::tty: error adding device: Failed to open device: 
Operation not permitted (os error 1)
2025-03-04T20:03:38.691859Z  INFO niri: 
listening on Wayland socket: wayland-1
2025-03-04T20:03:38.691862Z  INFO niri: IPC 
listening on: <MY HOME DIR>/.local/run/niri.wayland-1.36264.sock

Can you try adding:

debug {
   render-drm-device "/dev/dri/renderD128"
}

to your config.kdl and see if that works?

Unfortunately it doesn't. It picks up the device from the configuration
(visible in the first two lines logged by niri::backend::tty), but still adds
/dev/dri/card0 and the error remains the same.

Reply via email to