Snapped applications launched from command line aren't properly matched

This bug was fixed in the package bamf - 0.5.3+18.04.20180207.2-0ubuntu1

---------------
bamf (0.5.3+18.04.20180207.2-0ubuntu1) bionic; urgency=medium

  * bamf-window: read snap and flatpak IDs and use it to guess desktop-
    id (LP: #1747802)

 -- Marco Trevisan (Treviño) <mail@3v1n0.net> Wed, 07 Feb 2018 14:10:54 +0000

I'm wondering if it makes sense to also get this released for artful? Unity is not the default experience but the package is still available, so in theory someone upgrading from xenial to artful and insisting on staying with Unity as his shell might experience a regression.

What do you think? I'll accept it for now, but maybe it's worth considering?

Hello Marco, or anyone else affected,

Accepted bamf into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bamf/0.5.3~bzr0+16.04.20180207-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Artful backport coming also in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3137/+packages

Hello Marco, or anyone else affected,

Accepted bamf into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bamf/0.5.3+17.10.20180208-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Can confirm that test-case works in xenial after updating:

apt-cache policy bamfdaemon
bamfdaemon:
  Installato: 0.5.3~bzr0+16.04.20180207-0ubuntu1
  Candidato: 0.5.3~bzr0+16.04.20180207-0ubuntu1

Hello Marco, or anyone else affected,

Accepted bamf into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bamf/0.5.3~bzr0+16.04.20180209-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Why was the 20180209 version of the package created? Does it too need testing?

Brian, it was just rebuilt by bileto because I forgot to untick bamf from a rbuild, so nothing changes from previous testing.

So I just re-verified the check.

@3v1n0 can you also test the artful version?

The verification of the Stable Release Update for bamf has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package bamf - 0.5.3~bzr0+16.04.20180209-0ubuntu1

---------------
bamf (0.5.3~bzr0+16.04.20180209-0ubuntu1) xenial; urgency=medium

  * bamf-window: read snap and flatpak IDs and use it to guess desktop-
    id (LP: #1747802)

 -- Marco Trevisan (Treviño) <mail@3v1n0.net> Fri, 09 Feb 2018 15:49:14 +0000

As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of bamf from artful-proposed was performed and bug 1752153 was found. Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the "verification-failed-artful" tag from this bug report and add the tag "bot-stop-nagging" to bug 1752153 (not this bug). Thanks!

What testing has been has been performed on this package? On what versions?

That was in an artful VM running bamfdaemon 0.5.3+17.10.20180208-0ubuntu1

What testing was performed on this version? For example, did you test that an application with security profile gets a correct desktop file?

Please re-tag once you have detailed what verification was performed.