Getting QT apps running.

Dietmar Winkler dietmar.winkler at
Fri Aug 5 15:07:02 UTC 2016


so I finally spend some time again on this. Since I could not get the
menus to work under standard Ubuntu Unity 16.04 I thought maybe it's
not the snap but something that does not agree within the desktop

So I simply installed ubuntu-mate-desktop and logged into standard mate.

Then I rebuild the IPE application with three variants of plugs. I.e., in

1.   plugs: [x11, home]
2.   plugs: [unity7, home]
3.   plugs: [x11, unity7, home]

The result? ALL of those build worked flawlessly under Ubuntu Mate
whilst under standard Ubuntu Unity (on the very same machine I get:

1.   plugs: [x11, home]    > ipe doesn't launch but also no errors in
the terminal
2.   plugs: [unity7, home] > ipe launches without menu
3.   plugs: [x11, unity7, home]  > ipe launches without menu

Since ipe doesn't use any unity speciific stuff the right plug should
actually be simply x11 (and as the FAQ pointed out
even when run natively one needs to remove the appmenu-qt5 package to
get the menu).

Question that still stands is why although appmenu-qt5 is NOT present,
IPE would run when natively compiled (also under Unity) but only under
non-unity desktop when build as a snap.

Any idea how to explain this behaviour?


On 29 July 2016 at 16:01, Dietmar Winkler <dietmar.winkler at> wrote:
> Thanks for the pointer. Reading through the documentation of
> desktop-helper again I noticed that I might actually try the x11 plug
> instead of unity7 since it is the appmenu that causes problems in the
> first place.
> But now ipe would not launch at all. Also I don't get any error
> messages (apart from the Gtk warnings).
> Are there any debug logs I could search for to see what is getting stuck?
> On 29 July 2016 at 15:34, Joe Talbott <joe.talbott at> wrote:
>> Note the remote parts are now at
>> Cheers,
>> Joe
>> On Fri, Jul 29, 2016 at 8:53 AM, Dietmar Winkler <dietmar.winkler at> wrote:
>>> Seting the rests of the paths helped. I now have icons. The menu is
>>> still missing which reminded me that there currently is an issue with
>>> appmenu-qt5 which when naively compiled causes some keyboard shortcuts
>>> not to work.
>>> I was wondering if it is possible to generate a variant of desktop/qt5
>>> without appmenu-qt5 staged.
>>> I've found the definition here:
>>> but would still need the source to point to.
>>> --
>>> /Dietmar/
>>> Secure email communication:
>>> Public OpenPGP key: 0x235E6689
>>> --
>>> Snapcraft mailing list
>>> Snapcraft at
>>> Modify settings or unsubscribe at:
> --
> /Dietmar/
> Secure email communication:
> Public OpenPGP key: 0x235E6689


Secure email communication:
Public OpenPGP key: 0x235E6689

More information about the Snapcraft mailing list