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-keyring still checks for DBus secrets interface #112

Open
Freso opened this issue May 2, 2016 · 2 comments
Open

--no-keyring still checks for DBus secrets interface #112

Freso opened this issue May 2, 2016 · 2 comments

Comments

@Freso
Copy link
Collaborator

Freso commented May 2, 2016

din% isrcsubmit.py --debug --no-keyring
/usr/lib/python3.5/site-packages/keyrings/alt/Gnome.py:28: DeprecationWarning: GnomeKeyring.get_default_keyring_sync is deprecated
  result = GnomeKeyring.get_default_keyring_sync()[0]
Gkr-Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
isrcsubmit 2.0.1 by JonnyJD for MusicBrainz
INFO: Writing debug log to isrcsubmit.log
INFO: using discid version 1.1.0
using Cdrdao 1.2.3

DiscID:         reTyXYVFkqmFHLU1qzR3s8cXeYQ-
Tracks on disc: 11
INFO: in <ws2:disc>, uncaught <offset-list>
INFO: in <ws2:disc>, uncaught <offset-list>

Artist:         The Axel Boys Quartet
Release:        Everybody Else (Official)
Release Event:  1996            DK
Barcode:        0724385444227
Catalog No.:
MusicBrainz ID: e85185a3-ffd7-4b2a-b9f8-1725ce5185fb

Is this information different for your release?
Would you like to open the browser to submit the disc? [y/N] 

INFO: Saving toc in /tmp/cdrdao-2016-05-03 00-10-20.712139.toc..
ERROR: cdrdao returned with 1
@JonnyJD
Copy link
Owner

JonnyJD commented May 2, 2016

Well the problem "checking for the interface" is probably that the "check" is done on import. Note that the import itself doesn't fail.
Also note that we only import "keyring" here and don't have anything to do with the backend directly.

So I'd say this should be reported to (one of) upstream.
However, I don't think I have to troubleshoot this.
At least until it is clear that this is the actual problem for #113

@Freso
Copy link
Collaborator Author

Freso commented May 3, 2016

Oh, I'm fairly sure that this is entirely unrelated to #113 and I also know that it doesn't interfere with normal operations at all. I've gotten the error for some time, but have been able to both submit ISRCs and use keyring just fine. It is only a cosmetic error AFAICT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants