The icons-only taskbar should allow grouping by ClassName, or any other means to seperate programs that share a common process name. One example for this is wine. If you launch a wine application, notepad.exe for example, ClassName will be notepad.exe, ClassClass will be wine. If you then launch TeamViewer.exe (ClassName), it will also be wine (ClassClass). Reproducible: Always Steps to Reproduce: Affected is (at the time of this feature request) KDE 4.10.1 and prior releases including icontasks (i.e. icons-only taskbar). Actual Results: Effects: 1) The wine icon is shown instead of the actual application icon. 2) Any two or more wine applications are grouped. Expected Results: This is opposite to what would be the expected effect: 1) the .exe applications icon (from the .desktop link, if not available by other means) 2) not grouped with wine, but only with the wine application (e.g. all Notepad windows should be grouped, but not all wine application windows). A related bug seems to be bug #315488. Other possible cases include Java (.jar) and Mono (.exe) and propably any other interpreter-level application. A discussion about the wine issue is at http://forum.kde.org/viewtopic.php?f=17&t=106637.
Bump. Adding exceptions doesn't work either. For example, this settings: http://i.imgur.com/HyaPCZU.png Still make both apps grouped.
Created attachment 80462 [details] disable grouping This is a rough patch which disabled grouping altogether. (there is no ui config, just the code :) ) I know this won't be accepted by the dev, but may work for everyone who is asking for this. Group gets disabled but still gets the indicators of detected programs.
A real shame that this isn't well regarded upstream. While grouping per se is a great feature it is quite annoying with certain applications. For me it's really counter productive for realvnc windows, virtualbox machines. Besides that, I find it odd to have the taskbar icons occupying 10% of the space on the left, with lots of grouped items, while the rest of the taskbar is unused.
Disable grouping would make me like this widget even more. Great job anyway. Thanks.
*** This bug has been confirmed by popular vote. ***
Grouping is good and should be kept around for native KDE, Gnome, X, whatever Linux applications. The problem is that there needs to be special treatment for interpreter applications that share the same invocing program name, like wine. For example, disabling grouping completely also ungroups all of my Konqueror windows. That is not what I want. As it is now, only wine.exe applications are grouped unintendidly. I just tested this once more on KDE 3.12.3 with TeamViewer (has its own version of Wine: 1.2.1) and notepad.exe (which on my system is from Wine 1.7.15): grouped but shouldn't be. TeamViewer actually has two windows, so grouping them is intended. But all notepad windows should be separate from TeamViewer windows, as should be any other invoked wine session (i.e. wine application).
To whom it may concern, I beg you to fix this.
I can confirm this weird behaviour on the latest Kubuntu 14.10 alpha.
Note that in *buntu 14.10, this has been worked around by a change in wine: From 14.10: lengau@hyperion:~$ xprop WM_CLASS WM_NAME WM_CLASS(STRING) = "control.exe", "control.exe" WM_NAME(STRING) = "Wine Control Panel" lengau@hyperion:~$ xprop WM_CLASS WM_NAME WM_CLASS(STRING) = "notepad.exe", "notepad.exe" WM_NAME(STRING) = "Untitled - Notepad" lengau@hyperion:~$ From 14.04: amlowe@amlowe-VirtualBox:~$ xprop WM_CLASS WM_NAME WM_CLASS(STRING) = "control.exe", "Wine" WM_NAME(STRING) = "Wine Control Panel" amlowe@amlowe-VirtualBox:~$ xprop WM_CLASS WM_NAME WM_CLASS(STRING) = "notepad.exe", "Wine" WM_NAME(STRING) = "Untitled - Notepad" amlowe@amlowe-VirtualBox:~$ It looks like this is due to a patch in the Ubuntu version (http://archive.ubuntu.com/ubuntu/pool/universe/w/wine1.6/wine1.6_1.6.2-0ubuntu6.debian.tar.gz > debian/patches/winex11-Prevent-window-managers-from-grouping-all-wi.patch, also at https://github.com/wine-compholio/wine-staging/blob/master/patches/winex11-Window_Groups/0001-winex11-Prevent-window-managers-from-grouping-all-wi.patch) which sets ClassClass to be the process name. More info about this particularly is available at https://bugs.winehq.org/show_bug.cgi?id=32699 it looks like both bug #315488 and possibly bug #340498 address this same issue (#340398 is only a potential duplicate since it seems to be addressing the regular taskbar, and I don't know whether the same grouping logic applies to both).
Does not work with Wine 1.7.30 on PlayOnLinux, does work with the built-in Wine 1.6.2 from Ubuntu 14.10. Tested on Lubuntu 14.10 and Kubuntu 14.10 (i.e. LXDE & KDE) in a virtual machine environment. This patch needs merged into the mainline. (In reply to Alex Lowe from comment #9) > Note that in *buntu 14.10, this has been worked around by a change in wine: > > From 14.10: > lengau@hyperion:~$ xprop WM_CLASS WM_NAME > WM_CLASS(STRING) = "control.exe", "control.exe" > WM_NAME(STRING) = "Wine Control Panel" > lengau@hyperion:~$ xprop WM_CLASS WM_NAME > WM_CLASS(STRING) = "notepad.exe", "notepad.exe" > WM_NAME(STRING) = "Untitled - Notepad" > lengau@hyperion:~$ > > From 14.04: > amlowe@amlowe-VirtualBox:~$ xprop WM_CLASS WM_NAME > WM_CLASS(STRING) = "control.exe", "Wine" > WM_NAME(STRING) = "Wine Control Panel" > amlowe@amlowe-VirtualBox:~$ xprop WM_CLASS WM_NAME > WM_CLASS(STRING) = "notepad.exe", "Wine" > WM_NAME(STRING) = "Untitled - Notepad" > amlowe@amlowe-VirtualBox:~$ > > It looks like this is due to a patch in the Ubuntu version > (http://archive.ubuntu.com/ubuntu/pool/universe/w/wine1.6/wine1.6_1.6.2- > 0ubuntu6.debian.tar.gz > > debian/patches/winex11-Prevent-window-managers-from-grouping-all-wi.patch, > also at > https://github.com/wine-compholio/wine-staging/blob/master/patches/winex11- > Window_Groups/0001-winex11-Prevent-window-managers-from-grouping-all-wi. > patch) which sets ClassClass to be the process name. More info about this > particularly is available at https://bugs.winehq.org/show_bug.cgi?id=32699 > > it looks like both bug #315488 and possibly bug #340498 address this same > issue (#340398 is only a potential duplicate since it seems to be addressing > the regular taskbar, and I don't know whether the same grouping logic > applies to both).
Plasma 5.7 ships a fully-rewritten Task Manager backend which should resolve these issues. Please re-test with the Plasma 5.7 final release and feel free to reopen if problems do persist after all.