-
Notifications
You must be signed in to change notification settings - Fork 54
Plasmoid configuration not written #339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I haven't noticed this problem so far. If it is a recent regression then it is probably caused by a change in Plasma as I haven't changed anything concerning the Plasmoid directly. Writing this config file is also done by the Plasma shell and not the Plasmoid themselves so the problem is most likely there anyway. For another issue I've already tried to figure out what is possibly wrong with my Plasmoid and unfortunately I'm not sure what needs to be improved. (I'm not a Plasma dev and only created this Plasmoid by checking the source code of official Plasmoids for how things are done.) |
It did happen before the latest update, but I wasn't on that version long and can't say for certain if it's the exact same issue (since version changes may introduce different variables). I'll see if I can find where the problems are happening but it may not be for a while since I'm extremely busy with a project. If I find anything I'll let you know, but for now if anyone runs into this exact problem and needs a fix, the file I mentioned
where |
I have the same issue and I found this error in my journalctl, not sure if its related:
syncthingtray-qt6 v1.7.7-1 from AUR |
Even if it is unrelated there might be something I could do to avoid this warning/message. Or it is literally about a missing translation/localization? In this case I can't help much as I could only add English and German. |
I've just tested this on my system and can reproduce it. This definitely worked before so I assume there's a breaking change or regression in Plasma (considering I haven't changed anything). I guess the relevant log line below the translation one could be relevant as well:
The icon of the Plasmoid is also no longer displayed correctly in the selection which would also indicate "invalid" meta-data. I'm quoting "invalid" here because I don't think I have changed anything about the meta-data on the Syncthing Tray side. |
* Use correct prefix/suffix in icon name so it is also displayed when the regular variant (without prefix/suffix) is not installed as well * Change the category within `KPlugin` to `Utilities` which seems to be the most fitting category among the list of categories outputed on my system via `cat /usr/share/plasma/plasmoids/*/metadata.json | jq .KPlugin.Category` * Note that the currrent category `SystemServices` is not on that list. * It looks like the category needs to be translatable so this change might help preventing warnings like `"SystemServices" from "martchus.syncthingplasmoid-qt6" is not a known category that can be translated`. * Expose the version correctly so it isn't empty * Simplify specifying version in Plasma 5 version of the metadata file * See #339
I pushed a change that will avoid the With this I'm still getting
Enabling/disabling the Plasmoid as entry within the system tray Plasmoid works (is is configured persistently). I also see tons of errors like:
Those errors are probably unrelated as well. I haven't seen them before so they are probably caused by a change in either Qt or Plasma. (Strangely all those icons are still shown correctly. I also used the debugger adding a breakpoint when the relevant icon provider for these icons is registered. The registration happens before those errors are logged so it is not like the registration happens to late. When removing the registration there are also other errors logged in addition and then the icons aren't shown for real. Maybe this is an additional check on the image sources by Plasma which is wrongly performed on the |
I asked on the Plasma Matrix channel for help yesterday but haven't gotten any reply so far. I could try filing a Plasma bug but probably I'll have to figure this out on my own anyway. So I probably have to make a development build of Plasma and all KDE Frameworks dependencies to improve logging and debug the Plasma parts together why my own code. This will be a bigger task again so I'm not sure when I can dedicate time to do it. |
Thank you for the effort. Luckily the the syncthing started is still working but I guess the main use of the tray app is currently not really usable for us. |
Not sure what you mean by "the the syncthing started is still working" and "I guess the main use of the tray app is currently not really usable for us". Note that you can still use the Plasmoid. Either use the workaround mentioned on #339 (comment) or enable it as entry in the system tray plasmoid. The latter still seems to work despite #239. I've also updated the relevant README section accordingly. |
Sorry for the confusion, I was just saying that the build in systemd unit configuration is of course still working, so the syncing is also still working. |
Relevant components
syncthingctl
)libsyncthing
)Environment and versions
syncthingtray
,qtutilities
andc++utilities
: syncthingtray-qt6 (Syncthing Plasmoid 1.7.7), Plasma 6.3.5Bug description
Adding the plasmoid works as intended, and all usage thereafter is normal, including moving its position elsewhere, but its entry isn't added to
plasma-org.kde.plasma.desktop-appletsrc
meaning it's lost on plasmashell restart/reboot/etc. All other plasmoids work correctly, and once the default entry is added to file, it also seems to write other data (such as position) correctly too.Noting use of Wayland, though I don't think it matters since this is a config issue? Also not sure if this bug report belongs here or KDE, but felt likely here. Please advise if that isn't the case!
Steps to reproduce
Expected behavior
The plasmoid is persistent.
Screenshots
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: