Bug 27477 - Default Plasma Workspace Panel as duplicate icons
Summary: Default Plasma Workspace Panel as duplicate icons
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker normal
Target Milestone: Mageia 8
Assignee: KDE maintainers
QA Contact:
Keywords: Triaged
Depends on:
Blocks: 17523
  Show dependency treegraph
Reported: 2020-10-28 18:33 CET by Aurelien Oudelet
Modified: 2020-12-05 14:56 CET (History)
4 users (show)

See Also:
Source RPM: plasma-workspace-5.20.1-1.mga8.src.rpm
Status comment:

Default Layout on Plasma 5.20.1 Panel (44.25 KB, application/pdf)
2020-10-28 18:33 CET, Aurelien Oudelet

Description Aurelien Oudelet 2020-10-28 18:33:14 CET
Created attachment 11961 [details]
Default Layout on Plasma 5.20.1 Panel

Since Plasma 5.20 release, default user as weird bottom Panel layout.

See attached screenshot in PDF.

Duplicate icons:
- Dolphin
- Systemsettings5
- Firefox
- Display desktop

These duplicates are related to new default upstream layout with a Task Manager by icon only.

Missing link:
- Discover in Task Manager by icon as it is not installed by default.
Comment 1 Aurelien Oudelet 2020-10-28 18:33:43 CET
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged

Aurelien Oudelet 2020-10-29 16:13:22 CET

Blocks: (none) => 17523

Comment 2 David Walser 2020-10-29 18:11:04 CET
I'm guessing some of the duplicate application icons are from a "icons-only taskbar" which became the upstream default in 5.20.  We already reverted this nonsense during the KDE4 days, so we need to do that again (and default to a normal taskbar).
David Walser 2020-10-29 18:11:12 CET

Priority: High => release_blocker

Comment 3 David Walser 2020-11-13 21:08:42 CET
We really should fix this ASAP, as it affects new Plasma profiles that are created.  I think we can release new ISOs as soon as this is fixed.

The upstream commit that needs to be reverted is this one:

CC: (none) => luigiwalser

Morgan Leijström 2020-11-14 19:05:21 CET

CC: (none) => fri

Comment 4 David Walser 2020-11-15 14:54:52 CET
This has been partially addressed here:

but the change to the default icontasks hasn't been reverted yet, and should be.
Comment 5 David GEIGER 2020-11-15 18:37:35 CET
Yes, and why revert the upstream icontasks default choice? for me it is good as this.
Comment 6 David Walser 2020-11-15 18:44:08 CET
Because it's a bad choice.  They're trying too much to be like Microsoft Windows, for no good reason.  It's not a good UI choice.  We've always made our own choices with our KDE UI.  The traditional taskbar is what most of our users expect and provides better usability.  As I've said before, we already did the same thing during the Plasma 4 lifecycle.
Comment 7 Dave Hodgins 2020-12-04 22:01:18 CET
Ping. Status?

CC: (none) => davidwhodgins

Comment 8 David Walser 2020-12-04 22:05:12 CET
Indeed, I'd like to see this fixed now so that we can start building ISOs.

Just to follow on to previous comments, in light of the fact that *we've* had a regular taskbar in the past and upstream Plasma *just* made this change, the better question to ask is why would *we* make a change to the icononly taskbar now, and the answer is, there is no good justification for that.  It causes user confusion.  I am quite certain that if we have the default as a regular taskbar, there will be a lot less users wanting to switch to the icononly taskbar, then there would be users wanting to switch to a regular one if we left the default as icononly, and I imagine it wouldn't even be close.
Comment 9 Dave Hodgins 2020-12-04 22:21:43 CET
Just to be clear, I agree with comment 8. ISO images built with this bug
in place will not pass qa testing.
Comment 10 David Walser 2020-12-04 22:37:15 CET
Thanks Dave.  Should be fixed in plasma-desktop-5.20.3-3.mga8 when it builds.
Comment 11 David Walser 2020-12-05 14:56:06 CET
Marking as FIXED.

Resolution: (none) => FIXED

Note You need to log in before you can comment on or make changes to this bug.