[Bug 1764778] Re: Problems with SSSD + pam mount

Andreas Hasenack andreas at canonical.com
Tue Apr 24 18:17:41 UTC 2018

I setup a watch on the dconf directory, and can confirm the rename
happens just as in your error log message when I use dconf:

andreas at nsnx:~$ inotifywait -m /home/andreas/.config/dconf/
Setting up watches.
Watches established.

(run in another terminal: dconf write /org/gnome/rhythmbox/player/volume

/home/andreas/.config/dconf/ OPEN user
/home/andreas/.config/dconf/ CREATE user.3S6GHZ
/home/andreas/.config/dconf/ OPEN user.3S6GHZ
/home/andreas/.config/dconf/ MODIFY user.3S6GHZ
/home/andreas/.config/dconf/ CLOSE_WRITE,CLOSE user.3S6GHZ
/home/andreas/.config/dconf/ MOVED_FROM user.3S6GHZ
/home/andreas/.config/dconf/ MOVED_TO user
/home/andreas/.config/dconf/ CLOSE_NOWRITE,CLOSE user

I'm about to try that on a cifs mount. I also checked the documentation
for rename(2) (the system call that g_rename() is a wrapper for, see
Utilities.html#g-rename), and there is a scenario where it would fail
due to the filesystem not allowing it:

       EPERM or EACCES
(...) ; or the filesystem containing pathname does not support renaming of the type requested.

I cooked up a quick C rename.c program but it worked just fine in my cifs mount, so the investigation continues.

You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to libpam-mount in Ubuntu.

  Problems with SSSD + pam mount

To manage notifications about this bug go to:

More information about the Ubuntu-server-bugs mailing list