Le Sat, Jan 24, 2026 at 05:18:09PM +0100, Landry Breuil a écrit :
> Le Tue, Jan 20, 2026 at 05:18:15PM +0100, Christoph Liebender a écrit :
> > On 1/18/26 19:55, Tobias Heider wrote:
> > > On Sun, Jan 18, 2026 at 04:14:50PM +0100, Christoph Liebender wrote:
> > > > On 1/17/26 23:04, Tobias Heider wrote:
> > > > > On Tue, Dec 30, 2025 at 07:33:05PM +0100, Landry Breuil wrote:
> > > > > > Le Tue, Dec 30, 2025 at 03:21:56PM +0100, Tobias Heider a écrit :
> > > > > > > On Tue, Mar 04, 2025 at 05:13:07PM +0100, Tobias Heider wrote:
> > > > > > > > Hi,
> > > > > > > >
> > >
> > > Interesting. In previous versions I had SMITHAY_USE_LEGACY=1 set in
> > > startniri.sh. Does adding that back fix it for you?
> > > It doesn't seem to be necessary on my (amdgpu) desktop.
> > >
> >
> > Unfortunately, that does not do the trick on my intel thinkpad.
> >
>
> same here, SMITHAY_USE_LEGACY=1 doesnt seem to help niri, be it started
> by greetd or from startniri.sh on a vt.
in the end i understood that there was no magic safe defaults, so i had
to configure an outputs section to enable my screen, which wasnt very
obvious.
SMITHAY_USE_LEGACY wasnt needed, and niri starts fine from greetd, shows
its help screen listing keybindings, i can open a term.. and then it
crashes hard, with a coredump
#0 thrkill () at /tmp/-:2
#1 0x2261c7d3ec172c39 in ?? ()
#2 0x0000037100da6f9b in _libc_abort () at /usr/src/lib/libc/stdlib/abort.c:51
#3 0x0000036e5d5b88fe in std::sys::pal::unix::abort_internal ()
#4 0x0000036e5d5d163d in std::process::abort ()
#5 0x0000036e5d5ec092 in std::panicking::panic_with_hook ()
#6 0x0000036e5d5d1747 in std::panicking::panic_handler::{{closure}} ()
#7 0x0000036e5d5d133d in std::sys::backtrace::__rust_end_short_backtrace ()
#8 0x0000036e5d5e8521 in __rustc::rust_begin_unwind ()
#9 0x0000036e5d60f881 in core::panicking::panic_nounwind_fmt ()
#10 0x0000036e5d60f7c6 in core::panicking::panic_nounwind ()
#11 0x0000036e5d60f9ed in core::panicking::panic_cannot_unwind ()
#12 0x0000036e5cba93e2 in
wayland_backend::sys::server_impl::resource_dispatcher ()
#13 0x00000370d4278bf3 in wl_closure_dispatch (closure=0x371565a81c0,
dispatcher=0x0, target=0x6, opcode=0) at ../wayland-1.24.0/src/connection.c:1250
#14 0x00000370d427186d in wl_client_connection_data (fd=<optimized out>,
mask=<optimized out>, data=0x3706b38eb00) at
../wayland-1.24.0/src/wayland-server.c:486
#15 0x00000370d4276340 in wl_event_loop_dispatch (loop=0x37096ac8b40,
timeout=<optimized out>) at ../wayland-1.24.0/src/event-loop.c:1059
#16 0x0000036e5cbaa550 in
wayland_backend::sys::server_impl::InnerBackend<D>::dispatch_all_clients ()
#17 0x0000036e5cdab814 in <calloop::sources::generic::Generic<F,E> as
calloop::sources::EventSource>::process_events ()
#18 0x0000036e5ce43562 in
<core::cell::RefCell<calloop::sources::DispatcherInner<S,F>> as
calloop::sources::EventDispatcher<Data>>::process_events ()
#19 0x0000036e5c931684 in calloop::loop_logic::EventLoop<Data>::run ()
#20 0x0000036e5c95b7e2 in niri::main ()
#21 0x0000036e5c927e7a in std::sys::backtrace::__rust_begin_short_backtrace ()
#22 0x0000036e5c95f110 in std::rt::lang_start::{{closure}} ()
#23 0x0000036e5d5e9338 in std::rt::lang_start_internal ()
#24 0x0000036e5c95f001 in main ()
drop this section from startniri.sh:
if [ ! -d "${XDG_RUNTIME_DIR}" ]; then
mkdir -m 700 -p "${XDG_RUNTIME_DIR}"
fi
and fix the readme to explain/stress what's the minimal requirements for the
config.. with that the port itself is definitely fine, ok to import, further
improvement can be done in-tree.
