You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pinning Super Productivity to the Task Manager should have an icon when Super Productivity isn't running.
Current Behavior
If Super Productivity is pinned to the Task Manager and isn't running, a "blank" icon (white sheet) is shown.
Steps to Reproduce
Install Super Productivity using snap.
sudo snap install superproductivity
Run superproductivity.
superproductivity
Right click on the Task Manager Super Productivity icon and select "Pin to Task Manager". (You may need to select "On The Current Activity" if using activities.)
Exit Super Productivity
The launcher icon will now be a blank icon. (Also, you cannot start Super Productivity from the Task Manager and have to launch it from an Application Menu/Launcher/Dashboard.)
Note: This has been an issue for a while. I think it started around version 10.0.0. It's not easy to rollback snap versions so I wasn't able to figure out when it happened and what changed between versions.
Can you reproduce this reliably?
I was able to reproduce this with a live version of KDE Neon.
Potential Fix
It seems that the StartupWMClass is the superproductivity_superproductivity.desktop file doesn't match the class name of the window.
In the desktop launcher file /var/lib/snapd/desktop/applications/superproductivity_superproductivity.desktop:
StartupWMClass=Super Productivity
Class name from tools (xprop or qdbus):
StartupWMClass=superProductivity
Note: I wasn't able to figure out where in the build the desktop launcher file is built to make a pull request.
Getting StartupWMClass
Using xprop:
Run xprop:
xprop WM_CLASS
Click on the Super Productivity window.
Output is:
WM_CLASS(STRING) = "superproductivity", "superProductivity"
Using qdbus:
Install qtchooser.
sudo apt install qtchooser
Run qdbus:
qdbus org.kde.KWin /KWin queryWindowInfo
Click on the Super Productivity window.
Look for the resourceClass line in the output. Note the resourceName as well.
resourceClass: superProductivity
resourceName: superproductivity
Workaround (Temporary - Lasts until reboot or snap update)
Change the StartupWMClass from Super Productivity to superProductivity.
sudo sed -i 's/StartupWMClass=Super Productivity/StartupWMClass=superProductivity/' /var/lib/snapd/desktop/applications/superproductivity_superproductivity.desktop
Note: setting the StartupWMClass to superproductivity (lower case 'P' in productivity) seems to work as well.
Workaround (Permanent - override the desktop launcher file)
Change the StartupWMClass from Super Productivity to superProductivity.
sed -i 's/StartupWMClass=Super Productivity/StartupWMClass=superProductivity/' ~/.local/share/applications/superproductivity_superproductivity.desktop
Note: If you do this workaround, you will probably want to delete ~/.local/share/applications/superproductivity_superproductivity.desktop once this bug has been fixed.
The text was updated successfully, but these errors were encountered:
Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding!
Your Environment
Expected Behavior
Pinning Super Productivity to the Task Manager should have an icon when Super Productivity isn't running.
Current Behavior
If Super Productivity is pinned to the Task Manager and isn't running, a "blank" icon (white sheet) is shown.
Steps to Reproduce
sudo snap install superproductivity
superproductivity
Note: This has been an issue for a while. I think it started around version 10.0.0. It's not easy to rollback snap versions so I wasn't able to figure out when it happened and what changed between versions.
Can you reproduce this reliably?
I was able to reproduce this with a live version of KDE Neon.
Potential Fix
It seems that the StartupWMClass is the superproductivity_superproductivity.desktop file doesn't match the class name of the window.
In the desktop launcher file /var/lib/snapd/desktop/applications/superproductivity_superproductivity.desktop:
StartupWMClass=Super Productivity
Class name from tools (xprop or qdbus):
StartupWMClass=superProductivity
Note: I wasn't able to figure out where in the build the desktop launcher file is built to make a pull request.
Getting StartupWMClass
Using xprop:
xprop WM_CLASS
WM_CLASS(STRING) = "superproductivity", "superProductivity"
Using qdbus:
sudo apt install qtchooser
qdbus org.kde.KWin /KWin queryWindowInfo
resourceClass: superProductivity
resourceName: superproductivity
Workaround (Temporary - Lasts until reboot or snap update)
sudo sed -i 's/StartupWMClass=Super Productivity/StartupWMClass=superProductivity/' /var/lib/snapd/desktop/applications/superproductivity_superproductivity.desktop
Note: setting the StartupWMClass to superproductivity (lower case 'P' in productivity) seems to work as well.
Workaround (Permanent - override the desktop launcher file)
cp /var/lib/snapd/desktop/applications/superproductivity_superproductivity.desktop ~/.local/share/applications/
sed -i 's/StartupWMClass=Super Productivity/StartupWMClass=superProductivity/' ~/.local/share/applications/superproductivity_superproductivity.desktop
Note: If you do this workaround, you will probably want to delete ~/.local/share/applications/superproductivity_superproductivity.desktop once this bug has been fixed.
The text was updated successfully, but these errors were encountered: