2009/9/20 Milan Bouchet-Valat <email address hidden>
> Good, we know have the original error. I don't know what can trigger
> this, but the problem is not specific to the gnome-system-tools.
>
> Please run 'sudo apt-get install lslk' and
> lslk /etc/passwd
> It seems that another process/user is locking the file, preventing us from
> editing it. Sure, we should report errors instead of failing silently, but
> that's another story.
There seems to be no locks...
tta@dv5:~$ lslk /etc/passwd
tta@dv5:~$ sudo lslk /etc/passwd
lslk: WARNING: can't stat() fuse.gvfs-fuse-daemon file system
/home/tta/.gvfs
Output information may be incomplete.
> I don't think encrypted home changes anything to the problem, since the
> file is on the root partition.
>
>
Was just wondering could ecryptfs somehow block the writing of user specific
info.
2009/9/20 Milan Bouchet-Valat <email address hidden>
> Good, we know have the original error. I don't know what can trigger
> this, but the problem is not specific to the gnome-system-tools.
>
> Please run 'sudo apt-get install lslk' and
> lslk /etc/passwd
> It seems that another process/user is locking the file, preventing us from
> editing it. Sure, we should report errors instead of failing silently, but
> that's another story.
There seems to be no locks...
tta@dv5:~$ lslk /etc/passwd fuse-daemon file system
tta@dv5:~$ sudo lslk /etc/passwd
lslk: WARNING: can't stat() fuse.gvfs-
/home/tta/.gvfs
Output information may be incomplete.
> I don't think encrypted home changes anything to the problem, since the
> file is on the root partition.
>
>
Was just wondering could ecryptfs somehow block the writing of user specific
info.