| Summary: | Icons-Only Task Manager will stop respecting the window class after a while | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Danilo Luvizotto <danilo.luvizotto> |
| Component: | Task Manager and Icons-Only Task Manager widgets | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jsodpad, kdedev, nate, nicolas.fella, nikolakocicbz, qydwhotmail |
| Priority: | NOR | Keywords: | qt6 |
| Version First Reported In: | 6.0.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=475736 https://bugs.kde.org/show_bug.cgi?id=358277 |
||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Danilo Luvizotto
2024-03-01 14:07:28 UTC
I suspect this is related to Bug 475736 or Bug 358277. It's been days since it last happened. When I observed it, I was editing color schemes and Plasma themes, and I restarted plasmashell several times. If I can't reproduce it in the next fews days, I'll just close this. ok, I figured out how to reproduce it: 1. Close plasmashell with `kquitapp6 plasmashell` 2. Run plasmashell again Both Firefox and Whatsapp will be grouped together as Firefox in the Icons-only task manager. Not sure if I should create new issue, but I feel it is related to this one. I have similar setup with two "applications" of firefox with different profile args and names. When I launch app 1 and pin it, then after closing it and running again it will launch app 2. It will also show app 2 name on hover. This happens to any app I have in multiple instances. (In reply to Danilo Luvizotto from comment #3) > ok, I figured out how to reproduce it: > > 1. Close plasmashell with `kquitapp6 plasmashell` > 2. Run plasmashell again > > Both Firefox and Whatsapp will be grouped together as Firefox in the > Icons-only task manager. I can't reproduce this on git master, which will become Plasma 6.4 in a little under two months. Can you still reproduce this issue in Plasma 6.3? If you can, you you also try quitting Plasma using `systemctl restart --user plasma-plasmashell.service` and see if the same thing happens? Thanks a lot! No, it's been a long while since a last saw this happen, it's fixed! |