Re: gnome-keyring gnome keyring does not store passwords

[Marcus Moeller <marcus moeller gmx ch>]

On 08/24/2011 04:33 PM, Stef Walter wrote:
> On 08/24/2011 04:17 PM, Marcus Moeller wrote:
> > Hi all.
> >
> > First of all, I got to explain our setup in order to describe the
> > behaviour we experienced lately.
> >
> > At our university the users /home folders are mounted via CIFS. The
> > permissions are automatically set to 700 to every newly created file
> > within ~
> >
> > This works in general, but gnome-keyring seems to have some trouble with
> > it. The keyring file is created but with a size of 0. It is not shown in
> > seahores afterwards, too.
> >
> > Does perhaps gnome-keyring expects permissions of 600 instead?
>
> Hmmm, it's very likely there's something in you logs (syslog, auth
> facility) from gnome-keyring-daemon, which should help us see what's
> going on.

These are the only relevant messages I've found:

couldn't create temporary file for: 
/home/user/.gnome2/keyrings/login_25.keyring: Operation not supported
messages:Aug 24 12:29:01 host gnome-keyring-daemon[5586]: couldn't 
create login keyring: An error occurred on the device
messages:Aug 24 12:29:01 host gnome-keyring-daemon[5586]: failed to 
unlock login keyring on startup
messages:Aug 24 12:29:33 host gnome-keyring-daemon[5586]: keyring was in 
an invalid or unrecognized format: 
/home/user/.gnome2/keyrings/login_25.keyring
messages:Aug 24 12:29:36 host gnome-keyring-daemon[5586]: couldn't 
create temporary file for: /home/user/.gnome2/keyrings/default.keyring: 
Operation not supported
messages:Aug 24 12:29:36 host gnome-keyring-daemon[5586]: couldn't 
create collection: An error occurred on the device

Could it perhaps be, that the keyring files are hardlinks? Because 
hardlinks are not supported on the CIFS shares.

Greets
Marcus