Open twang2218 opened 2 years ago
Current workaround of the problem, fix the AppArmor profiles by provided script:
sudo /snap/qqmusic-snap/current/fix-tray.sh
The script fix-tray.sh will patch and reload the AppArmor profile for qqmusic-snap. Relaunch the qqmusic-snap, the systray should work correctly.
I send the pull request: snapcore/snapd#10873 at 2nd Oct, and it's been merged at 18 Oct, it's marked to be part of snapd 2.53
. So, the fix-tray.sh
workaround will not be necessary after the release of 2.53
.
If the snap is installed in the
devmode
, everything works correctly, however, if it's installed instrict
/dangerouse
, the systray icon is not working correctly.Installed in
devmode
Verify the mode:
Launch the
qqmusic
via cliAt the same time, the
/var/log/kern.log
content is following:And the systray icon works correctly.
Installed in
strict
/dangerous
modeThe mode can be verified by CLI:
Launch the
qqmusic
from command line:The
/var/log/kern.log
output for the launch is:And nothing happened if click on the qqmusic systray icon.
Problem
The
bluez
error should not be the problem, I can overcome it by connecting it tobluez
interface, and the result is the same.The following error caught my eyes, and I'm not sure whether it's the cause of the problem: