XS/jabber gabble: password is not available after reboot

[greenfeld]

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: 13.1.0 os22
This is a regression to 12.1.0.

[erikos]

Ok, after setting up my environment I was able to debug this. I have found the following. In the mission control log there was the statement "missing mandatory account parameter password". We do ​set the password when using gabble when we create the account. However, when the account exists already, the password seem to not be known to the server, either not stored/restored correctly or not transferred well.

I verified that this is the case and deleted the telepathy settings (~/.local/share/telepathy/mission-control/) on two machines and restarted them, the next run the account got created again. I could see both buddies in the neighborhood view and shared Chat fine between those two machines. Looks like we are back to the previous behaviour when we sort out the password issue.

[erikos]

One can use 'mc-tool show <account name>' (the account name can be retrieved with mc-tool list) to show the account details. When I did create the gabble account from new the password was listed there. Then after a restart it is not listed there anymore, and I can not connect to gabble.

[JerryV]

Think the password gets saved in ~/.gnome2/keyrings/default-keyring, not sure how to retrieve it but the password is just a call to: key_hash = get_profile().privkey_hash so it might be easy to recreate it.

[JerryV]

in terminal I can bring up gabble by hand with:
'mc-tool update <Account> string:password=<secret from default-keyring>'

the connection is instantaneously switched over to gabble and Neighbourhood View becomes populated.

[erikos]

Replying to JerryV:

in terminal I can bring up gabble by hand with:
'mc-tool update <Account> string:password=<secret from default-keyring>'

the connection is instantaneously switched over to gabble and Neighbourhood View becomes populated.

Thanks Jerry for that update. Yes the password is there, we need to find out now why the communication between mission-control and the gnome-keyring is not working. I am trying to build gnome-keyring with debug output, but failed until now.

[erikos]

For debugging I run the gnome-keyring-daemon and ​mission-control-5:

killall gnome-keyring-daemon mission-control-5

G_MESSAGES_DEBUG=all /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets

G_MESSAGES_DEBUG=all MCMC_PERSIST=1 MC_DEBUG=all /usr/libexec/mission-control-5 2>&1 | tee mc.log

[erikos]

gnome-keyring-daemon log

[erikos]

mission-control log

[JerryV]

Attached patch allow gabble to connect, think there still is an issue with two gabble dbus instances running.

[JerryV]

patch to neighborhood.py

[erikos]

Thanks Jerry for the patch. I did the same to test some days ago. But if mission-control does talk with the keyring we should fix that and not interfere with passing the password to mc ourself.