Bug 491754 - firefox icon behavior not as expected for grouping and sorting after REBOOT
Summary: firefox icon behavior not as expected for grouping and sorting after REBOOT
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager widgets (other bugs)
Version First Reported In: 5.27.11
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-15 15:40 UTC by goo
Modified: 2024-10-16 03:47 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
attachment-868140-0.html (2.17 KB, text/html)
2024-08-30 14:28 UTC, goo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description goo 2024-08-15 15:40:02 UTC
SUMMARY

the pinned icon behavior of the firefox icon in the icon only task manager is not as expected after a REBOOT... the previously pinned icon no longer groups new windows and it can no longer be shorted manually by dragging... and if unpinned, leaves behind a generic icon image rather than going away.

instead, after a REBOOT and a new window is opened,  a new icon appears that collects and groups all the new windows,  leaving the previously pinned icon abandoned.

to resolve, unpin all the icons, close firefox, navigate to the firefox app in the apps menu and pin to taskmanager... from there the icon can sorted, used to launch firefox and collect new windows 

until the next REBOOT.


STEPS TO REPRODUCE
1.  pin firefox icon to the taskmanager
2. REBOOT


OBSERVED RESULT
previously pinned icon no longer behaves normally and a new (duplicate icon) appears in the task manager.

EXPECTED RESULT
previous icon would remain associated with the CURRENT version of firefox and behave normally for sorting and grouping functions.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-40-generic (64-bit)
Graphics Platform: X11
Processors: 28 × Intel® Core™ i7-14700K
Memory: 62.6 GiB of RAM
Graphics Processor: AMD Radeon RX 6800
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D27
System Version: 1.0

ADDITIONAL INFORMATION

previous bug report https://bugs.kde.org/show_bug.cgi?id=491643 was in reference to firefox updates and the issue was closed based on the application meta data changing between updates (presumably confusing the task manager)... but this new observed and reproducible behavior occurs with the exact same version of firefox every time you reboot.

this also happened in kubuntu 22.04 but fixed itself at some point, perhaps when backports was enabled and don't exactly recall.
Comment 1 Nate Graham 2024-08-16 15:31:56 UTC
Cannot reproduce in current git master in a Wayland session.
Comment 2 Akseli Lahtinen 2024-08-30 12:35:03 UTC
Do you have firefox installed as snap or flatpak? I have seen similar issues with flatpaks before, however they seem to be resolved on my end now.

Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.80
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.10.6-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600
Comment 3 goo 2024-08-30 14:28:56 UTC
Created attachment 173127 [details]
attachment-868140-0.html

I'm using the snap version with

Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 28 × Intel® Core™ i7-14700K
Memory: 62.6 GiB of RAM
Graphics Processor: AMD Radeon RX 6800

but others have also experienced it with a native install

my version of FF is currently 129.0.2


On Fri, Aug 30, 2024 at 5:35 AM Akseli Lahtinen <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=491754
>
> Akseli Lahtinen <akselmo@akselmo.dev> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |akselmo@akselmo.dev
>
> --- Comment #2 from Akseli Lahtinen <akselmo@akselmo.dev> ---
> Do you have firefox installed as snap or flatpak? I have seen similar
> issues
> with flatpaks before, however they seem to be resolved on my end now.
>
> Operating System: Fedora Linux 40
> KDE Plasma Version: 6.1.80
> KDE Frameworks Version: 6.6.0
> Qt Version: 6.7.2
> Kernel Version: 6.10.6-200.fc40.x86_64 (64-bit)
> Graphics Platform: Wayland
> Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
> Memory: 15.5 GiB of RAM
> Graphics Processor: AMD Radeon RX 6600
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 4 Justin Zobel 2024-09-02 12:30:14 UTC
I've never seen it with a native install. Can you install the native Firefox package or the Flatpak version and test please? That would rule out the snap interface as the issue.
Comment 5 goo 2024-09-02 13:03:19 UTC
here is a discussion about it

https://discuss.kde.org/t/icon-grouping-does-not-work-in-taskbar-for-firefox/19913

i've messaged the author to share more details here.

unfortunately, i'm on kubuntu and only have access to the snap version.
Comment 6 goo 2024-09-02 17:41:33 UTC
I can also add a bit more about the behavior: when the new icon is created it's not movable within the other pinned icons in the task manager, (it can only be moved among the open items).

but after going to applications and re-pinning the firefox program to the task manager i now have a new icon that can be moved among the other pinned icons and it is not associated with my current open windows.

if i then close the window the old icon goes away and i can re-open firefox using the newly pinned icon... then all is well, until the next reboot
Comment 7 lwpkg 2024-09-10 17:03:00 UTC
Hello, I'm the other party in the message thread that @goo indicated. Here are my machine details:

Operating System: Manjaro Linux 
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.6-10-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700H
Memory: 15.2 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ASUS TUF Gaming F15 FX507ZE_FX577ZE
System Version: 1.0

I'm currently on firefox 130.0 native install from Manjaro repositories. I'm on the testing branch of Manjaro if it matters. If there is more information I can provide, let me know. I've had to unpin and repin firefox after every update and sometimes after reboot. What I can say is that the move from 129 to 130 is the first time in the last 3-4 months that I've *not* had to do unpin/re-pin. 

Let me know if I can share any other information.

(BTW I'm not familiar with the bug statuses in the bug tracker, so I've left it alone.)
Comment 8 Nate Graham 2024-09-16 15:13:20 UTC
Based on the description, this issue is actually a packaging bug.

For a long time Firefox didn't ship its own .desktop file, so distros made one for it. This means they were all inconsistent and unstandardized boo!

Eventually Firefox started shipping its own .desktop file, so distros removed theirs.

This resulted in previously pinned instances of Firefox no longer working, so you'd have to un-pin it and re-pin it. In some distos, this happened multiple times, based on distro packaging policies and actions.

Unfortunately there's nothing we can do about it in Plasma, sorry.
Comment 9 Bug Janitor Service 2024-10-01 03:47:05 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2024-10-16 03:47:49 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.