Ivan Molodetskikh
Ivan Molodetskikh
This won't help with your problem. You're moving something like a proportion 25% window to the vertical monitor where it remains proportion 25%.
That error shouldn't affect it. Try cosmic-comp or anvil please if the outputs are visible there? If not then open a Smithay issue
Can you post the full niri log?
Strange, it doesn't recognize any other connector at all. What's printed in the log if you unplug and replug the monitor?
Weird, it's like it's not seeing it at all
Interesting. @cmeissl hey, do you know if this could happen if the smithay-drm-extras CRTC mapper fails to map a connector to a CRTC in some unfortunate way where another mapping...
We don't try to reuse existing configurations (though it's something that would be good to do) I believe we only add connectors from drm_scanner.connectors() which only gives out those with...
Is there an existing compositor where disabled-on-external-mouse works properly for your setup? If so we can copy the logic from there
So since recently, Smithay allows the compositor to skip cursor updates in such cases, but I intentionally don't do that because I expect the cursor to always do full FPS...
Can you try this patch? Put ```rust let output_state = niri.output_state.get_mut(output).unwrap(); if output_state.frame_clock.vrr() { flags.insert(FrameFlags::SKIP_CURSOR_ONLY_UPDATES); } ``` into here https://github.com/YaLTeR/niri/blob/ec88aae77d0032cc6500d2af09818c0003add608/src/backend/tty.rs#L1425 Before this can become a normal option, it needs some...