Yeah, the indicators all ship upstart jobs, systemd units, and autostart .desktop files.
There are some cases where indicators need fixed in other ways to deal with similarly related issues (parsing other .desktop files), but generally the data/*.desktop.in files aren't a problem here, from what I can see. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1638708 Title: Hardcoded paths in desktop files need to be processed need $SNAP prefixing Status in indicator-application package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: New Status in indicator-datetime package in Ubuntu: New Status in indicator-location package in Ubuntu: New Status in indicator-messages package in Ubuntu: New Status in indicator-network package in Ubuntu: New Status in indicator-power package in Ubuntu: New Status in indicator-printers package in Ubuntu: New Status in indicator-session package in Ubuntu: New Status in indicator-sound package in Ubuntu: Triaged Status in indicator-transfer package in Ubuntu: New Bug description: Noticed and reported by mterry in several indicator patches, e.g. <https://code.launchpad.net/~mterry/indicator-sound/snap- root/+merge/308125>: > There are also two hardcoded paths in the data/*.desktop.in files. > But that's a static desktop file, so $SNAP isn't appropriate. > I think it makes more sense to update the code that reads those > files to do the prefixing. There is also an umbrella ticket for hardcoded paths in the u8 snap: <https://pad.lv/1629009> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1638708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
