| Summary: | After upgrade to KDE Plasma 5.20.5, unexpectedly new apps are pinned to Task Manager | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | i.Dark_Templar <idarktemplar> |
| Component: | Task Manager and Icons-Only Task Manager widgets | Assignee: | Eike Hein <hein> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.20.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | taskbar.png | ||
|
Description
i.Dark_Templar
2021-01-22 18:13:29 UTC
Hmm, it was definitely not intentional to add these to people's existing panels--just new ones. I'm not even sure how it could have happened, based on how the panel code works. Did you reset your panel to the default settings, or remove it and re-add it? Or had you never ever pinned any apps to your Task Manager in the first place? I didn't reset my settings before, during or after upgrade. I didn't remove or add/readd panels. But I had no pinned applications since I prefer traditional task panel icons which don't disappear when an instance of application is started. Ah yes, the old issue where changing the defaults only affects people who had not changed anything in the past. :/ Unfortunately we don't have a generic way to say "this change should affect everyone" or "this change should only affect new users". However in this case, it was intentional: we wanted people to get new pinned icons if they previously had not customized anything. I understand that you might disagree, but there's no way to change it back at this point since it's already happened. :) (In reply to Nate Graham from comment #3) > Ah yes, the old issue where changing the defaults only affects people who > had not changed anything in the past. :/ > > Unfortunately we don't have a generic way to say "this change should affect > everyone" or "this change should only affect new users". > My bug is exactly about this: next time something like this is implemented it'd be good to have some way to separate those two cases, and for existing users at least ask them. Like, "we have this new shiny feature. Want to try it out?". > However in this case, it was intentional: we wanted people to get new pinned > icons if they previously had not customized anything. I understand that you > might disagree, but there's no way to change it back at this point since > it's already happened. :) Of course, I didn't intend to wait for next KDE release to remove components unneeded for me, and do it for me specifically :) I did it on my own after reporting bug. Yes, I agree. It's something we need to improve in a central, deliberate way. Right now it's super ad-hoc: some things get automatically applied for people who haven't changed their own defaults, and some things don't, and we don't have a painless way of choosing what will happen--it's up to the underlying implementation. Resolving this with a sort of "here's what changed; do you want to use the new thing now?" dialog would be nice, I agree. |