Snappy

snapd-interface application problem with systry icon

Bug #1592714 reported by Josué on 2016-06-15

This bug report is a duplicate of: Bug #1600136: App indicator does not show icon for Qt apps or with custom icons. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Snappy	Confirmed	Undecided	Unassigned

Bug Description

I installed telegram-sergiusens snap package.

The original telegram-app uses a systry icon that works as follow:
If you close the window of telegram app the app will still be runing untill you close the app through the systry icon.
If you close the window but without close through systry icon and then, you open again the app throug the icon on the dash a window of the same instance that is previously open will emerge.

In the telegram-sergiusens:
No icon on systry appears. If you close the window app the app will be still running in the background, you will recieve destktop notifications if someone write you, so I assume that the app tries to put a icon on the systry but if fails.
If you click again in the launcher icon of telegram a new instance will be created.

I removed the snap package and reinstall it ussing --devmode, the ressult is still strange but better than before:
If you run the app an "icon" will appear in systry, it's hard to explain, it's not the native icon for the app, i think that it's the icon that appears when the icon file is missing or something. The systry icon works as espected. But, if you close the window app, without closing systry icon and you open again through the launcher icon a new instance will be created for the app.

Attached syslog grep for Telegram when installed with --devmode

Tags:

Revision history for this message

Josué (j2g2rp) wrote on 2016-06-15:

telegram.txt Edit (68.1 KiB, text/plain)

Revision history for this message

Josué (j2g2rp) wrote on 2016-06-15:

I was trying in other computer the first problem that was that the systry icon doesn't appear, but i cant reproduce it, maybe firstly I was doing something weird...
The ressult is the same for the instalation as using --devmode

Revision history for this message

Josué (j2g2rp) wrote on 2016-06-15:

I installed this in a virtualbox with ubuntu 16.04 and the result is the same as i posted in the first message, no systray icon appear.

Revision history for this message

Jamie Strandboge (jdstrand) wrote on 2016-06-16:

Thank you for the bug report. Can you attach the output of 'grep audit /var/log/syslog' after the application is installed in strict mode and you exercise the application?

Changed in snappy:
status:	New → Incomplete

Revision history for this message

Josué (j2g2rp) wrote on 2016-06-19:

Telegram.txt Edit (287 bytes, text/plain)

Hi!
Attached you will find the log after opening the app installed in virtualbox guest.

Revision history for this message

Jamie Strandboge (jdstrand) wrote on 2016-06-22:

Hi Josué, the specified denial is this:
kernel: [ 598.952301] audit: type=1400 audit(1466339978.463:31): apparmor="DENIED" operation="open" profile="snap.telegram-sergiusens.telegram" name="/etc/openal/alsoft.conf" pid=2342 comm="Telegram" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

This indicates a problem not with the systray but with openal, an audio library. I'm curious if you are seeing a cascading failure. Can you modify /var/lib/snapd/apparmor/profiles/snap.telegram-sergiusens.telegram to have before the last '}':

/etc/openal/* r,

then do:
$ sudo apparmor_parser -r /var/lib/snapd/apparmor/profiles/snap.telegram-sergiusens.telegram

and try again? Please report back any new denials in /var/log/syslog and if this worked around the issue or not.

Thanks!

Revision history for this message

Josué (j2g2rp) wrote on 2016-06-25:

TT Edit (31.5 KiB, text/plain)

seems logic, the package also have problems accesssing to the sound it can't play any sound from notifications or from audio messages.
Respect this bug:
I did what you suggested, but the systray icon is missing yet.
Doing a grep "Telegram" to syslog and sending it to a file the file this time is empty, in any case i attach the syslog for that sesion.

Revision history for this message

Jamie Strandboge (jdstrand) wrote on 2016-07-08:

I think this is a duplicate of bug #1600138. Since that bug is in the process of being fixed, I'm going to mark this a duplicate of that. If this is in error, please re-open. Thanks!