** Project changed: snappy => snapd
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bamf in Ubuntu.
https://bugs.launchpad.net/bugs/1643910
Title:
BAMF_DESKTOP_FILE_HINT not set in correct place for unity7
Status in snapd:
Triaged
Actually, there is https://bugs.launchpad.net/bamf/+bug/1747802 which is
fixed. I checked the code and this should be resolved. Marking as fixed.
** Changed in: bamf (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Is there any more progress on this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bamf in Ubuntu.
https://bugs.launchpad.net/bugs/1643910
Title:
BAMF_DESKTOP_FILE_HINT not set in correct place for unity7
Status in Snappy:
Triaged
As discussed on telegram we agreed that `snap run` should do basic
matching when not run from a desktop file. However we should be aware
that this matching will not 100% accurate because desktop files may use
the same binary but different commandline arguments.
--
You received this bug
The way we're currently doing it is by setting the environment from the
desktop file, and that works OK for things launched from that desktop
file (right?).
So if when running a snap we find that env key not set, I think we need
to set BAMF_DESKTOP_FILE_HINT to *something*. Otherwise things (bamf
Right now the way desktop files work is that you put them in
meta/gui/*.desktop and they will get installed into
/var/lib/snapd/desktop/applications.
When running a snap I could introspect that dir and look if snap.command
is part of the /var/lib/snapd/desktop/application/*.desktop and if so,
set
claswsmail results in even different behavior:
sudo snap install claws-mail-moon127 --devmode --edge
launch from dash, launched via snap-confine (see aa-status)
pin non-pulsating to launcher, launches outside of snap run (see aa-
status) with no desktop file in ~/.local/share/applications
--
I'm marking this as High for now since it appears that a malicious snap
should be able to craft a desktop file such that it will launch outside
of confinement.
** Changed in: snappy
Importance: Undecided => High
** Changed in: bamf (Ubuntu)
Importance: Undecided => High
--
You received
At this point it is hard to pin point what the problem is as there is
different behavior depending on the snap where:
- sometimes things show up in the dash, other times not
- sometimes we can pin the launcher and have it launch under snap-confine and
sometimes not
- sometimes we can launch from
$ sudo snap install trusthtables
It doesn't show up in the dash even though
/var/lib/snapd/desktop/applications/trusthtables_truthtables.desktop
exists
launching from command line:
$ truthtables
/snap/truthtables/3/bin/qt5-launch: 74: exec: truthtables: not found
(something obviously wrong
Interestingly, installing 'snap install gnome-easytag --devmode --edge'
and pinning it to the launcher results in nothing created for it in
~/.local/share/applications but it launches under confinement (as seen
with aa-status).
--
You received this bug notification because you are a member of
But if I launch easytag from the command line and pin the resulting
icon, then ~/.local/share/applications/easytag.desktop is created with
Exec=easytag (ie, both the desktop file name and Exec is wrong).
--
You received this bug notification because you are a member of Desktop
Packages, which is
(glade is also not found in the dash)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bamf in Ubuntu.
https://bugs.launchpad.net/bugs/1643910
Title:
BAMF_DESKTOP_FILE_HINT not set in correct place for unity7
Status in Snappy:
Here is one that results in launching outside of confinement:
$ sudo snap install chrome-test --edge
Launch from the dash
Pin the non-pulsating icon to the dash
The resulting desktop entry in ~/.local/share/applications/google-
chrome.desktop is
Here is one that results in a broken launcher:
$ snap install glade-attente
$ glade-attente.glade
pin to launcher
close glade
try to launch glade-attente.glade
The resulting desktop entry in ~/.local/share/applications/glade.desktop
is 'Exec=glade'
Notice that the desktop file name
We also should protect BAMF from creating .desktop files for such SNAPs
pointing to the actual binary instead that to the wrapper script.
** Also affects: bamf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bamf (Ubuntu)
Status: New => Triaged
--
You received this
** Description changed:
Occasionally when I pin items to the Unity7 launcher, the BAMF code (as
I'm told) incorrectly matches to /snap/app/revision/ This is a
security issue because the Exec= line points to /snap/app/revision/...
which bypasses snap run (/snap/bin/...) and therefore
** Changed in: bamf (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bamf in Ubuntu.
https://bugs.launchpad.net/bugs/1643910
Title:
BAMF_DESKTOP_FILE_HINT not set
** Changed in: snappy
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bamf in Ubuntu.
https://bugs.launchpad.net/bugs/1643910
Title:
BAMF_DESKTOP_FILE_HINT not set in correct place for unity7
Status in
19 matches
Mail list logo
