touch-packages team mailing list archive

[Ted Gould <ted@xxxxxxxx>]

I disagree, that file is a temporary file for legacy reasons. It doesn't
work that well and causes many problems, continuing to use it will see
the continuance of those issues that we could otherwise forgo.

I think it would be simple enough for the webapp to provide a relative
path to its installation directory for the desktop file. For instance
its Exec line could be as follows:

Exec=webapp-container --desktop-file=data/my-desktop-file.desktop
http://foo.com

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1437393

Title:
  Allow a confined app to read its own .desktop file

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  New

Bug description:
  The use-case is webapps: in the webapp container we are implementing a splash screen to be shown at certain times during the webapp execution, which contains among other things the application icon and name.
  While we could ask the webapp developer to explicitly specify the application name and icon in the webapp manifest, this seems like unnecessary work. On the other hand, reading the .desktop file from the installed package dir is not trivial: the file could be in a subdirectory, it could have any name, and we risk picking up the wrong file in case there are more apps in the same package.

  AFAICT, the only reliable way to get the desktop file is to check the
  APP_ID environment variable and read
  ~/.local/share/applications/$APP_ID.desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1437393/+subscriptions