Yes, if you run the store-client manually from command line, it lacks permission to access the keys. You can look up the complete line to invoke it in its .desktop file, though. This will provide it with the required privileges.
Martin 2013/12/27, Mike Sheldon <m...@mikeasoft.com>: > On Fri, 2013-12-27 at 16:01 +0000, Mike Sheldon wrote: >> On Fri, 2013-12-27 at 15:58 +0000, Mike Sheldon wrote: >> > On Fri, 2013-12-27 at 16:44 +0100, Martin Grimme wrote: >> > > You're right. Those apps should not be updatable before updating the >> > > OS. >> > > >> > > I think you can revive your store-client by updating the store-client >> > > package and then doing a "pkill store-client". >> > >> > Well, manually updating the store-client has got the store opening >> > again, but only to the page saying that no accounts are currently set >> > up, attempting to sign in from there just results in it complaining >> > that >> > an account already exists. >> >> Deleting the account and attempting to sign in again gets me the generic >> error "Oops, problem with account creation". I'll leave this for now in >> case it's just down to the Jolla servers being hammered, if it still >> continues not to work I guess I'll have to reset the phone. > > Aha, managed to add my account again now. Looks like the store-client > maybe gets some extra privileges when launched by the system, when > running it from the command line for debugging it was producing these > errors: > > SailfishKeyProvider_ini_read: unable to open file > SailfishKeyProvider_storedKey(): error: no scheme or key found for > provider/service > SailfishKeyProvider_ini_write: unable to create writable ini directory > > But killing that and relaunching the store normally solved it :) > > Thanks, > Mike. > > _______________________________________________ > SailfishOS.org Devel mailing list > _______________________________________________ SailfishOS.org Devel mailing list
