I have been using QMMP with and winamp skin for years now.
But since last zypper dup, there is a problem.
What I should see:
So I google and found this :
https://sourceforge.net/p/qmmp-dev/tickets/1139/
That worked for some part, at least QMMP shows the winamp skin again, but
It should be three parts, which you can move around.
Instead I get the 3 winamp windows totally stuck and over lapping.
Not sure were to ask for help, kde ? openSUSE ? So lets start here.
Who broke my qmmp ? 
So, you’re hoping it looks like the screenshot below?
(with the Player, Equalizer, and Playlist components stacked)
Yes and normally you can move those three parts, together or separately.
And if you move them and bring them close, they kinda snap together.
1min 37 in the vid.
How it normally looks out of the box.
Yea, I realize that … that screenshot I showed is my TW system, running my install of QMMP
I am able to un-stack the 3 components, or overlay them, or place anywhere on screen. And of course, when I drag one component close to the base of another, they “snap” together (as intended).
Probably, with the most recent updates, which mainly consists of the big KDE Plasma 6 upgrade, there might be something missing, or misconfigured, affecting you QMMP
My QMMP install is as a Flatpak.
What happens when you drag one component to the bottom of another?
I cant, every QMMP window is stuck in place.
I don’t use this app but just installed and compared to flatpak and I have same issue with flatpak version. I am able to in plamsa alt-mouseclick and drag them around but just as separate windows. -Default in plasma rather than alt for modifier key in “Window Behavior” settings is the windows key for click-drag
Obviously not prettiest solution until they update it.
Well, if it were me, I see two choices:
a - uninstall, then install the standard version again
b - uninstall the standard version, then install the Flatpak version. (what I prefer, not that that means anything )
Hmmm. I don’t have to use any modifier key. I simply left-click and hold the top bar, then drag the individual window(s) around.
Then I simply left click and hold on top bar of a component window and drag back to another Q window and they snap together.
Thats how it should work.
Found something, it seems to be a wayland problem.
I don’t use Wayland, because there’s always one issue or another.
If doubtful, spend some time out here and read all the, “it’s a Wayland prob” comments
I think we need to open a can of whoopass on the wayland devs.
Nobody should touch my winamp clone. 
(and yes I have tried other programs)
I just switched to plasma X11, and all is fine again. QMMP working as it should.
So now, I at least narrowed the problem down to wayland.
Now need to find out were to complain, so they can fix it.
But for now, bye bye wayland.
Off topic, and I realize I wont have to code stuff, so it might be easy for me to say, but.
They dont fix / adapt alsa but come up with pipewire.
Now they don’t fix X but make wayland.
To end positive pipewire is working fine. Maybe wayland will get there too.
In most cases not Wayland is the culprit, but the application devs like from QMMP which ignored the last decade of development. They slept and didn’t care, knowing that X will disappear…
That why I tried wayland.
I read enough on phoronix, to know, like it or not, X is on its way out.
Valve is putting effort into wayland…
Then I am also on a bleeding edge distro, still I like to quote Linux on this.
You should never break user space. 
I opened a ticket at qmmp.
Lets see what happens. I only seems to be a problem on wayland, when you use a winamp skin.
I got an reply, and I am not happy. Were can I talk to the wayland devs?
For now wont be using wayland. Reading about this issue, I am starting to worry about ardour too.
Unfortunately Wayland protocol does not allow application to control their windows positions. Some people trying to bypass this limitation by complicating the protocol: staging: Add ext-placement protocol for window positioning in "zones" (v2) (!264) · Merge requests · wayland / wayland-protocols · GitLab But without any luck.
If you find any solution or workaround, please, let me know.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
