On Sun, Jan 04, 2026 at 02:51:07PM +0100, Landry Breuil wrote:
> Le Sun, Jan 04, 2026 at 01:54:10PM +0100, Matthieu Herrb a écrit :
> > On Tue, Dec 09, 2025 at 10:31:55AM +0100, Landry Breuil wrote:
> > > Le Mon, Dec 08, 2025 at 08:03:58PM +0000, yaydn@protonmail.com a écrit :
> > > > > > >
> > > > > > > resending after the wcm update of august, now that mesa has been fixed,
> > > > > > > wdisplays displays its own window. It doesn't render 'visually' the list
> > > > > > > of actually plugged screens (says 'No GL implementation available') but
> > > > > > > it allows to play with DPI scaling, change resolution/position,
> > > > > > > flip/rotate/etc..
> > > > > > >
> > > > > > > ----
> > > > > > > wdisplays is a graphical application for configuring displays in Wayland
> > > > > > > compositors. It should work in any compositor that implements the
> > > > > > > wlr-output-management-unstable-v1 protocol. Compositors that are known
> > > > > > > to support the protocol are Sway and Wayfire. The goal of this project
> > > > > > > is to allow precise adjustment of display settings in kiosks, digital
> > > > > > > signage, and other elaborate multi-monitor setups.
> > > > > > > ----
> > > > > > >
> > > > > > > oks welcome to import.
> > > > > >
> > > > > > ping, still looking for okays to import this one - reattached for
> > > > > > convenience.
> > > > >
> > > > >
> > > > > and ping again, now that i've tested it w/ wayland and an external hdmi
> > > > > monitor, it properly allows to configure relative position of screens
> > > > > (like xfce4-display-settings, which also works fine with wayland afaict)
> > > > >
> > > > > Landry
> > > 
> > > oks from developers still welcome :)
> > 
> > ok matthieu@. It will be easier to debug the remaining issues in the
> > tree.
> 
> the only remaining issue is the missing graphical rendering of the
> screens in the left pane, but that works fine once mesa is built with
> wayland support :)

At least under sway, the pointer motion becomes sluggish while wdisplays is
running, on my 2 testing machines. I couldn't find the reason so far,
but it may be linked to the attempts at rendering a miniature of the
screen.

> 
> will import it later, thanks !

-- 
Matthieu Herrb