Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no access to gnome-keyring? #9

Closed
mainmachine opened this issue Jun 10, 2019 · 5 comments · Fixed by #10

Comments

@mainmachine
Copy link
Contributor

commented Jun 10, 2019

Version 1.7.0 on Ubuntu 18.04 running in the Cinnamon desktop. Looks like the snap is being denied access to the gnome-keyring:

Uncaught (in promise) Error: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.446" (uid=1000 pid=19795 comm="/snap/ghost-desktop/71/usr/lib/Ghost/Ghost --type=" label="snap.ghost-desktop.ghost-desktop (enforce)") interface="org.freedesktop.Secret.Service" member="OpenSession" error name="(unset)" requested_reply="0" destination=":1.11" (uid=1000 pid=4698 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined")
Another fellow is using "--devmode" as a workaround:

http://smac.io/ghost-desktop-issue/

...and I suspect running with classic confinement might work too.

@mainmachine

This comment has been minimized.

Copy link
Contributor Author

commented Jun 10, 2019

Maybe just a guess, but does this snap need to be able to connect to the password-manager-service interface?

@igorljubuncic

This comment has been minimized.

Copy link

commented Jun 10, 2019

Can you rebuild with the password-manager-service interface and see if that makes a difference?
https://forum.snapcraft.io/t/the-password-manager-service-interface/7899

@mainmachine

This comment has been minimized.

Copy link
Contributor Author

commented Jun 12, 2019

I will try. Never built a snap before so wish me luck :)

@mainmachine

This comment has been minimized.

Copy link
Contributor Author

commented Jun 13, 2019

So adding password-manager-service does indeed fix this!

I also learned that you need to build snaps on 16.04 presently, and that "snap try prime" does not necessarily work even if the build was successful...

I did need to manually run 'sudo snap connect ghost-desktop:password-manager-service' manually, so I suspect there is some nuance to the snapcraft.yaml that I am missing.

Shall I fork and submit a PR?

@mainmachine

This comment has been minimized.

Copy link
Contributor Author

commented Jun 14, 2019

submitted PR #10

@popey popey closed this in #10 Jun 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.