If you have some windows grouped in the task bar. In earlier KDE versions you were able to cyclic switch through the grouped windows by hovering the mouse cursor on the group menu item and turn the mouse wheel. This does not work anymore in KDE4.11(.2) Reproducible: Always Steps to Reproduce: 1. open an application multiple times (e.g. konsole or kate) 2. configure the taskbar to group windows of the same application 3. mouse the mouse cursor on the group taskbar entry. 4. turn the mouse wheel up or down Actual Results: The behaviour is not the same every time. Sometimes you only bring one window of the application to the front. If you continue to turn the mouse wheel nothing more happens. This one window is kept in the foreground. Sometimes instead the one window is brought to front and to back again. The to the front again and so on. Expected Results: Like using the window switcher (Alt+Tab) you should be able to switch through all the windows of the task bar group.
I cannot reproduce this; it works just fine here. Can you please attach a screenshot of your settings and perhaps the panel in the relevant state, for clues?
Oh you are right. On other desktops the switching still works. I am able to reproduce it the following way: On an empty desktop: 1. open 3 konsole windows => cycling does work fine. 2. open the editor "medit" (a GTK app) with one window => cycling through the konsole windows does work fine. 3. open a second medit window (e.g. from the file-menu of medit) => cycling through the konsole windows does not work anymore But it behaves always the same way: only one konsole window is brought to the front and back again. (The other behaviour was a mistake by me in analysing the issue.)
Bug confirmed.
Git commit d21f3948efe782b20e118f80a3cf3c2705664bcd by Eike Hein. Committed on 07/11/2013 at 14:44. Pushed by hein into branch 'KDE/4.11'. Fix switch-by-wheel on group parents only working correctly for the rightmost one. M +4 -0 libs/taskmanager/tasksmodel.cpp http://commits.kde.org/kde-workspace/d21f3948efe782b20e118f80a3cf3c2705664bcd
Thanks for your report, it turned out to be a small but nasty logic error. It's fixed now; the fix will appear in 4.11.4 and subsequent releases.
Wow, this was quick. :) Thank you very much, Gert PS: Could you do me a favor and do this following little fix and commit it for me? https://bugs.kde.org/show_bug.cgi?id=313734 ;)
https://bugs.kde.org/show_bug.cgi?id=429525