Ok, I found out a bit more about this bug. It is most probably the same
bug as this:
http://bugs.kde.org/show_bug.cgi?id=148126
and ultimately the closed bug 103381
http://bugs.kde.org/show_bug.cgi?id=103381
I also discovered one more fact, that makes me rather sure that it is the
same bug: there are also some types of external windows that will push the
osd to the bottom, but that are not opened by amarok (one of them is the
"FvwmWinList")
To quote the last entry of this closed bug:
Mark Tiefenbruck 2007-07-08 06:43:53 wrote:
"This has been resolved in fluxbox. However, as the one who tracked this
one down, I can say for sure that amarok shares the blame. The OSD is an
override-redirect window. We therefore ignore it completely. When the user
opened the menu, we raised that, and it ended up higher than the OSD in
the stacking order. Then, when we needed to restack our windows, the OSD
would get pushed to the bottom (since we're not keeping track of it). If
amarok simply raised their OSD every time they mapped it, this would be a
non-issue."
So this might be regarded as an fvwm2 bug, but is an issue that will keep
creeping up from time to time with different windows managers (or on
wm-change, as seen in the other bug), unless amarok raises its osd each
time it opens a new one! (It would still become pushed to the back from
time to time, but that wouldn't normally have a major influence of the
usefulness of the osd as a whole).
Reassign to fvwm2 if you like... I think it would be more useful to
(also?) have a fix in amarok...
K.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
