You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 3, 2022. It is now read-only.
What steps will reproduce the problem?
1. Set up password protection on your MPD server.
2. Add the password to Cantata's connection settings.
What is the expected output? What do you see instead?
I expect Cantata to connect to the MPD server with the password provided.
Instead, Cantata discards the password the moment you press OK or try to save
the configuration. It WILL successfully connect if you reconnect to the server
from the configuration dialog, but it reconnects again without a password as
soon as you exit the dialog no matter what happens.
What version of the product are you using? On what operating system?
Cantata r1296 on Kubuntu Precise. The problem exists at least as far back as
v1.7.1.
Please provide any additional information below.
My MPD configuration is known to be working because I've used MPD with
Client175, ncmpc, and Sonata without any problems, password and all.
Original issue reported on code.google.com by sunsetse...@gmail.com on 25 Jun 2012 at 4:20
The text was updated successfully, but these errors were encountered:
This maybe a duplicate of r39 - where settings wer not being saved. I always
use password with my MPDs. I've just had a quick check, and they are being
saved.
Please can you check if this is still present in the latest revision?
Original comment by craig.p....@gmail.com on 25 Jun 2012 at 6:20
I just figured out what the problem is.
Cantata uses the KDE Wallet to save passwords, apparently, and mine is
disabled. If I enable it, Cantata saves the password, but I don't want to
enable it.
Original comment by sunsetse...@gmail.com on 25 Jun 2012 at 10:53
Original issue reported on code.google.com by
sunsetse...@gmail.com
on 25 Jun 2012 at 4:20The text was updated successfully, but these errors were encountered: