Is Winamp interface support planned for Wayland?

[hellpe]

When trying to enable the Winamp Interface in Audacity (version 4.4.2 from Flathub on Fedora Silverblue 41), the window closes then reopens without any visible change. I get the same behavior from the Qt and the GTK interfaces. Here's the error message:

It seems that Wayland support is not planned and that I should not report an issue for it. Is that correct? Thanks in advance

[radioactiveman]

Applications running on Wayland are not able to get/set their window positions.
As a result, moving windows or restoring their position is not possible on application side.
Responsible for these tasks is now the window manager, not the application itself. This approach of Wayland is by design.

The Winamp interface for Audacious obviously relies on those functionalities.
And the consequence is that its windows cannot be moved at all on Wayland.
As explained above, this is not something we can solve on our side.

The answer therefore is:
No, supporting the Winamp interface on Wayland is not planned because it is simply not possible.
Audacious since version 4.4 uses X11/XWayland by default when available as workaround.
With Flathub this seems to be not the case (again not in our responsibility) and explains the warning you get.

See also:

• https://audacious-media-player.org/problems
• https://github.com/audacious-media-player/audacious/releases/tag/audacious-4.4
• https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/264 and the referenced previous proposals

@jlindgren90: Feel free to confirm and add more information if I missed something.

[jlindgren90]

That sums it up nicely 👍

[parkerlreed]

Positioning protocol has been merged https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/264

Would be great to have Audacious fully Wayland once support lands in the compositors.

[jlindgren90]

I have not read the entire protocol, but it sounds like in the final version, they intentionally do not support our use-case:

However, besides that, ext-zones makes implementing toplevel-drag impossible with a recent addition to the protocol:
[The compositor] must not send 'position' events while the item is dragged, only when it reaches its final position.
This makes it impossible to implement usable toplevel-dragging with this protocol.

... and propose yet another new protocol instead:

Implementing "magnetic windows" with this protocol looks annoying...
For this particular case, it is a lot better to tell the compositor about the two windows being docked together so it can perform the appropriate actions. Ideas for a new protocol specifically for this are being discussed here: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/198

[parkerlreed]

Ahh dang. Thanks. Here's to hoping.

[ffs-akl]

In my opinion, It is time to drop the winamp interface.

[radioactiveman]

If you don't like the Winamp interface, just don't use it. Other people use Audacious simply because it still supports Winamp skins.