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
In the Creating appmenus stage of the provisioning, multiple warnings about the send-to-usb.desktop file are printed, meaning I think our file is somehow malformed vs what Qubes expects:
Warning: ignoring key 'Name' of send-to-usb
[...]
Warning: not creating/updating '/home/<redacted $USER>/.local/share/qubes-appmenus/sd-large-bookworm-template/apps.templates/send-to-usb.desktop' because of missing 'Name' key`
The first warning line is us hitting this, second is this, because we ignored the Name key. This code is executed during the qubes.GetAppMenus rpc service call.
The plot thickens: yes we should figure out why qubes-desktop-linux-common thinks our desktop file is malformed (I think maybe the quotation marks?) and throwing warnings, but we may not actually want an appemnu created in the template anyway for this because it's not meant to be invoked any other way than via our rpc calls.
(/usr/share/applications/send-to-usb.desktop is created)
Steps to Reproduce
Please specify your environment if that is necessary to reproduce the bug (if in doubt, include it).
Expected Behavior
No warnings during provisioning
Actual Behavior
Warning, as above
Comments
Suggestions to fix, any other relevant information.
The text was updated successfully, but these errors were encountered:
Description
Noticed testing #1112 :
In the
Creating appmenus
stage of the provisioning, multiple warnings about thesend-to-usb.desktop
file are printed, meaning I think our file is somehow malformed vs what Qubes expects:The first warning line is us hitting this, second is this, because we ignored the Name key. This code is executed during the
qubes.GetAppMenus
rpc service call.The plot thickens: yes we should figure out why qubes-desktop-linux-common thinks our desktop file is malformed (I think maybe the quotation marks?) and throwing warnings, but we may not actually want an appemnu created in the template anyway for this because it's not meant to be invoked any other way than via our rpc calls.
(/usr/share/applications/send-to-usb.desktop is created)
Steps to Reproduce
Please specify your environment if that is necessary to reproduce the bug (if in doubt, include it).
Expected Behavior
No warnings during provisioning
Actual Behavior
Warning, as above
Comments
Suggestions to fix, any other relevant information.
The text was updated successfully, but these errors were encountered: