I seem to have an issue with Firefox pinned icons in the taskbar. Specifically, I’ve noticed usually after a reboot, clicking on the Firefox icon in taskbar to launch it, on opening it shows up as a seperate icon rather than with against the pinned one.
The description that I gave may not be clear, thus adding a picture. The “change” I made to the taskbar is edited the tasks.svg file from default breeze theme to have an underline and I’ve verified that the issue exists with default theme as well.
Appreciate help in trying to figure out what’s going on here.
Operating System: Manjaro Linux
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.6.44-1-MANJARO (64-bit)
Graphics Platform: Wayland
i’ve recently been battling this one too on kubuntu 24.04 and had a similar experience with kubutnu 22.04, but i didn’t document how i resolved it, so when it came back after the new install i had to figure it out all over again.
it would also add the new windows (and even group them) under a separate icon that i could only manually sort among my open apps… not the pinned icons, so it might have something to do with that.
still can’t say i know for sure what i did to solve it, but i kept unpinning firefox from the icons only task manager and then adding it back from the applications menu until finally it stuck and is working at the moment.
there were several snap updates to firefox in the mean time that may or may not have played into that and i’m on plasma 5 and x11.
i suggest this:
- unpin from the task manager
- update firefox (however you do that for your installed version).
- reboot
- configure task manager so grouping is ON
- also set sort to manual
- then right click on firefox from the application launcher to pin it again
- reboot again (just for fun)
see if it behaves itself.
1 Like
Thanks I did the following.
- Unpin from task manager
- Reinstall Firefox (I was already on the latest version)
- Reboot
- Task manager grouping was already set to On and sort was manual.
- Launch firefox and ping it to the desired position.
- Reboot
Firefox seems to be behaving itself (for now). The only variable other than reboot is them change (Breeze Light to dark and vice-versa). I’ll give it a couple days with me rebooting and switching theme and see if it sticks.
What a strange issue, only firefox seems to be affected. If this is indeed the solution, I wonder if it’ll reoccur when firefox is updated.
i have a FF snap update pending as we speak… brb.
ok, seems like it held this time and behavior is unchanged.
you know they are always working on bug fixes behind the scenes and sometimes i feel like i’m going crazy when things just start working as they should and i didn’t really do anything.
i’m just glad it’s not doing it any more.
update: after a reboot it started acting up again showing a new icon (with the plus sign) down at the bottom of my task manager.
to resolve it, i unpinned my old pin at the top, then pinned the new icon and moved it back up to the top.
i guess you have to do this after each firefox update.
1 Like
Glad I posted the question here and you found time to answer. I’ve had to do the unpin/re-pin at least half a dozen times so far before I posted the question. I was about to give up on firefox and switch to brave (I just like ff suggestions better).
I wonder if this is a bug with Firefox or plasma. It’s the only application that seems to have a problem. Considering I’m using the native package and you snap, packaging is different as well.
Thanks for responding, I’ll mark your post as the answer as it helped.
i filed a bug report
https://bugs.kde.org/show_bug.cgi?id=491643
feel free to comment with any additional info about your experience.
Thanks. I see that the issue is marked as “Resolved Upstream” and a reference stating that due to packaging changes on firefox there is no way other than to repin. I’ll collect more data and try to figure out what’s actually happening here because my experience has been that ff needs to be unpinned/repinned after every shutdown/reboot.
i submitted a new tag because i too can reproduce it by simply doing a REBOOT.
https://bugs.kde.org/show_bug.cgi?id=491754
we’ll see what the answer is this time.
1 Like