Version: (using KDE KDE 3.3.2) Installed from: Gentoo Packages Compiler: gcc 3.3.5 OS: Linux I listen to the first few songs and the OSD stuff works great, but after a while the OSD is not always on top anymore; which basically renders it useless. I tried to figure out exactly how long it was for it to stop working, but I couldn't figure it out.
On Thu, 7 Apr 2005 06:48 am, Arthur Axel fREW Schmidt wrote: > I listen to the first few songs and the OSD stuff works great, but after a > while the OSD is not always on top anymore; which basically renders it > useless. I tried to figure out exactly how long it was for it to stop > working, but I couldn't figure it out. Are you running a window manager like fluxbox?
Yes, that's what I am running.
This seems to be a fluxbox bug. see: http://amarok.kde.org/component/option,com_simpleboard/Itemid,/func,view/catid,8/id,1360/#1360 http://amarok.kde.org/component/option,com_simpleboard/Itemid,/func,view/catid,8/id,4302/#4302
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.