touch-packages team mailing list archive

[Bugfinder <1364316@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Use Ubuntu 14.04.1 LTS (with latest updates)

Configure your system to mount user home directories on login via cifs
mount (you can also switch to console and mount some user's home via
cifs).

You can try this via a samba mount on the same computer to show that
there are no network related issues, but make sure to not mount your
users home in his home (smbd will loop), but an empty share where your
user has all rights, which is stored on a completely other directory
path (not in your home).

Make sure that the home directory is empty (ls -alh shows no files).

Login via lightdm (Gnome Shell Fallback (Metacity) or Ubuntu (Unity)).

Login will be very slow and might hang.

On the server you will find in the samba logs:
Oplock break failed for file .config/dconf/user -- replying anyway

in your .cache/upstart/ logfiles you will find errors about dconf not
being able to store it's configuration.

When you restart the computer, clean up the mounted directory and either
use the bind option of mount to redirect .config/dconf elsewhere or use
pam_mount to mount a tmpfs there, the login will be very fast as it
should be (but you loose your dconf data).

Disabling locking in smb.conf also helps, but unfortunately it can be
only set on whole shares (ok it could be set on file extensions, but
user has no file extension).

** Affects: d-conf (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to d-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1364316

Title:
  Very slow/failed logon on cifs mounted home caused by locking issues
  of .config/dconf

Status in “d-conf” package in Ubuntu:
  New

Bug description:
  Use Ubuntu 14.04.1 LTS (with latest updates)

  Configure your system to mount user home directories on login via cifs
  mount (you can also switch to console and mount some user's home via
  cifs).

  You can try this via a samba mount on the same computer to show that
  there are no network related issues, but make sure to not mount your
  users home in his home (smbd will loop), but an empty share where your
  user has all rights, which is stored on a completely other directory
  path (not in your home).

  Make sure that the home directory is empty (ls -alh shows no files).

  Login via lightdm (Gnome Shell Fallback (Metacity) or Ubuntu (Unity)).

  Login will be very slow and might hang.

  On the server you will find in the samba logs:
  Oplock break failed for file .config/dconf/user -- replying anyway

  in your .cache/upstart/ logfiles you will find errors about dconf not
  being able to store it's configuration.

  When you restart the computer, clean up the mounted directory and
  either use the bind option of mount to redirect .config/dconf
  elsewhere or use pam_mount to mount a tmpfs there, the login will be
  very fast as it should be (but you loose your dconf data).

  Disabling locking in smb.conf also helps, but unfortunately it can be
  only set on whole shares (ok it could be set on file extensions, but
  user has no file extension).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1364316/+subscriptions