[Bug 59468] New: gnome keyring secrets can not be accessed after reboot
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Jan 16 15:25:27 CET 2013
https://bugs.freedesktop.org/show_bug.cgi?id=59468
Priority: medium
Bug ID: 59468
Assignee: telepathy-bugs at lists.freedesktop.org
Summary: gnome keyring secrets can not be accessed after reboot
QA Contact: telepathy-bugs at lists.freedesktop.org
Severity: major
Classification: Unclassified
OS: All
Reporter: simon at schampijer.de
Hardware: All
Status: NEW
Version: git master
Component: mission-control
Product: Telepathy
When establishing the connection with the jabber server the first time
everything works fine, the connection can be made and using the mc-tool the
password for that account is shown correctly.
After reboot, the connection can not be established again. Using 'mc-tool show
<account name>' does not show the password anymore. One can connect to the
jabber server by using 'mc-tool update <Account> string:password=<secret from
default-keyring>' and passing the password by hand.
Version:
telepathy-mission-control: 5.14
telepathy-glib: 0.20
telepathy-gabble: 0.16.4
gnome-keyring: 3.6
libgnome-keyring: 3.6
I did downgrade to telepathy-gabble-0.16, telepathy-mission-control-5.12,
telepathy-glib-0.18 and the issue was gone.
Adding debug logs we point at
http://cgit.freedesktop.org/telepathy/telepathy-mission-control/commit/?h=telepathy-mission-control-5.14&id=eaefb264316f206186b2ac7f1f36e6a4692deb3d
at second boot, ending up in '/* behave as if it had already been deleted, i.e.
we never * actually found it... */'.
Full history and more info at: http://bugs.sugarlabs.org/ticket/4369
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
More information about the telepathy-bugs
mailing list