Bug 223402 - Multiple individual window icons remain in taskbar despite grouping
Summary: Multiple individual window icons remain in taskbar despite grouping
Status: RESOLVED DUPLICATE of bug 201761
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-taskbar (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-19 13:45 UTC by mps
Modified: 2010-01-25 04:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot showing taskbar grouping problem (37.44 KB, image/png)
2010-01-19 13:46 UTC, mps
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mps 2010-01-19 13:45:53 UTC
Version:           4.3.90 (4.4 RC1) (using Devel)
OS:                Linux
Installed from:    Compiled sources


See attached screenshot of the panel. 

Okular, Firefox and Kmail have 2, 2 and 3 windows respectively open. They appear grouped (righthand side of taskbar), however there are individual icons for each one as well (see left end of taskbar). Clicking on the individual and grouped ones confirm that they are the same windows.

Happens only when task bar is very full. Also, sometimes there ends up being a gap in the taskbar when an application is closed.
Comment 1 mps 2010-01-19 13:46:46 UTC
Created attachment 40036 [details]
Screenshot showing taskbar grouping problem
Comment 2 mps 2010-01-19 13:47:32 UTC
Sorry, these are kde-redhat rpms, not compiled sources.
Comment 3 Dario Andres 2010-01-19 13:48:30 UTC
- Is that the normal taskbar or FancyTasks/SmoothTasks/STasks ?
Regards
Comment 4 mps 2010-01-19 14:26:15 UTC
Its the default taskbar, not stasks.
thankss
Comment 5 Christoph Feck 2010-01-20 14:43:54 UTC
I can confirm this on todays trunk. For example, clicking on links inside Akregator, external Konqueror windows opened this way usually are not grouped.
Comment 6 Christoph Feck 2010-01-25 04:21:21 UTC

*** This bug has been marked as a duplicate of bug 201761 ***