SUMMARY It's my understanding that the path to the image used for the Firefox shortcut icon changes as part of a Snap refresh. KDE is having trouble with that. I've been told that there might be a Snap call needed to update some icon cache specifically for KDE. I've also been told that there may be a stale, outdated KDE cache that needs attention. As a result, it was recommended that I create a KDE and a Snap bug report. Here it is: I use Kubuntu 22.04 LTS and I put a shortcut to Firefox on my panel (taskbar) by right-clicking the Firefox entry in my K menu and choosing "Add to Panel (Widget)" from the context menu. When Snap pops up the reminder on screen every so often to tell me I need to update it, I close Firefox and run the sudo snap refresh firefox command. Afterwards, the Firefox widget shortcut on the panel sometimes continues to work without incident. Other times, however, it suffers a rather dramatic cosmetic change by vanishing from sight while still existing. When this happens, the invisible shortcut still takes up the same amount of space on the panel, is still clickable, and still works (it creates what appears to be a gap on the panel). This never happens immediately during or right after the update, but always occurs either later that day (during the same Kubuntu session) or when I boot up the next day. My work-around is to delete the invisible Firefox shortcut from the panel and recreate it from the K menu the same way I originally did. It then looks and works fine until the next time an update makes it vanish. Two final things I'd like to note are: * The icon in the Firefox entry in the K menu never disappears when this happens. * I'm only seeing the behavior in a Firefox widget shortcut on the panel. I haven't tested putting a Firefox shortcut onto the desktop or pinning a Firefox shortcut to the Task Manager. I'd be happy to test both of those if you'd like. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-76-generic (64-bit) ADDITIONAL INFORMATION These two issue reports seem to be related to this one: * https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1851490 * https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851490 This issue report by me was filed against snapd in reference to this same issue: * https://bugs.launchpad.net/ubuntu/+source/unity/+bug/2026314
Thank you for the bug report! However Plasma 5.24.7 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.24.7, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report.
Shouldn't you at least take the time to investigate the information I've provided to see whether the issue still exists in the current version and would benefit from your attention?
That was a bot. Indeed, this issue should have been fixed in Plasma 5.26. I'd recommend upgrading to Kubuntu 22.10, which will give you Plasma 5.27.
Then I take it that this won't be fixed. 22.10 is not an LTS, so it's not a solution for an LTS issue. Since WONTFIX isn't a status option, since the FIXED status that you chose isn't accurate (the issue that I reported above is broken in the current Kubuntu LTS), and since the bot and you both seem to want to close this report out without doing anything about it, INTENTIONAL status is more accurate. I am not allowed to choose that status, so please choose it on my behalf.
As the bot said, Plasma 5.24 is no longer supported by KDE. This is KDE's bug tracker, not Kubuntu's bug tracker. So it tracks when issues are fixed in KDE code, not when the fix is rolled out to users of the latest Kubuntu LTS version. Assuming I'm correct that this issue is fixed, then RESOLVED FIXED is appropriate since the issue is fixed in our code, it's just not fixed in the version of Plasma that you're using. It's your choice if you want to use a distro that ships software releases that are older than what KDE offers support for. That LTS designation came from Kubuntu, not us. It just means you need to ask for support from them. If tihs explanation is not satisfying, I'd recommend reading see https://community.kde.org/Get_Involved/Issue_Reporting#Understand_what_the_resolution_statuses_mean
Your use of "should have been fixed" and "Assuming I'm correct" suggests that you haven't checked and aren't certain whether the issue has been fixed in a more recent version of Plasma or not. Guesses and assumptions aren't strong structures upon which to hang a hat. If it turns out that a similar issue has been fixed in a more recent version of Plasma, that doesn't fix the behavior that occurs in KDE Plasma version 5.24.7 as described in this issue report. This issue report is not about the rest of your code. Also, your recommendation that I upgrade to a more recent version of Plasma is not a fix. It's a recommendation. As a result, surely it's as obvious to you as it is to me that marking this issue as FIXED is not only inaccurate, but is downright silly. No worries, though. I can help with that: Perhaps instead of repeatedly disagreeing with me and choosing an inaccurate status for an issue, you could check whether there's a fix for the behavior described above in a more recent version of Plasma, fixing it if there isn't, and, more importantly, add or work toward adding a DEPRECATED or WONTFIX or an INVALID or UNSUPPORTED status to this issue tracker so that you can choose an accurate status for this issue and for other such issues in the future, making for an informative and pleasant environment for your users and demonstrating that you value the time and effort they put into making these error reports.
Per https://community.kde.org/Get_Involved/Issue_Reporting#Understand_what_the_resolution_statuses_mean "RESOLVED FIXED" doesn't mean "fixed for you personally", it means "fixed in the code, even if you might not necessarily be using the version that contains the fix." We can't control what versions of our software that users use; if you choose to use 5.24 and the fix is in 5.27, for example, that's fine, but it means you won't have the fix yet.