*** This bug is a duplicate of bug 1572132 ***
https://bugs.launchpad.net/bugs/1572132
Not sure if this is actually a duplicate. Is it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764778
*** This bug is a duplicate of bug 1572132 ***
https://bugs.launchpad.net/bugs/1572132
** This bug has been marked a duplicate of bug 1572132
SMBv2+ does not show all files when mounting a windows share
** No longer affects: libpam-mount (Ubuntu)
** No longer affects: sssd (Ubuntu)
--
Same problem happened to Ubuntu 16.04.5. I have to specify "vers=1.0" to
mount a old NAS drive successfully. The help said the default version is
1.0, so I spent a lot of time to check other options. Anyone please
update the help text.
--
You received this bug notification because you are a
Adding a cifs-utils task. It's closer to the problem. But the bug might
be in the kernel bit.
** Also affects: cifs-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libpam-mount (Ubuntu)
Status: Incomplete => Invalid
** Changed in: sssd (Ubuntu)
Status:
Adding a cifs-utils task. It's closer to the problem. But the bug might
be in the kernel bit.
** Also affects: cifs-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libpam-mount (Ubuntu)
Status: Incomplete => Invalid
** Changed in: sssd (Ubuntu)
Status:
I did. It resolves the error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764778
Title:
Problems with SSSD + pam mount
To manage notifications about this bug go to:
Can you try setting vers=1.0 in the mount options?
On Wed, Apr 25, 2018, 04:41 Paul-Georg Majev <1764...@bugs.launchpad.net>
wrote:
> First of all: Thank you very much for investing so much time into
> getting to the bottom of this problem! We are very grateful for it and
> relieved, that the
Can you try setting vers=1.0 in the mount options?
On Wed, Apr 25, 2018, 04:41 Paul-Georg Majev <1764...@bugs.launchpad.net>
wrote:
> First of all: Thank you very much for investing so much time into
> getting to the bottom of this problem! We are very grateful for it and
> relieved, that the
First of all: Thank you very much for investing so much time into
getting to the bottom of this problem! We are very grateful for it and
relieved, that the error could be reproduced. Is there anything else I
can do to help solve this?
--
You received this bug notification because you are a
I'm wondering if this is not related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572132
I see less files when I mount the share with smb3. In particular,
~/.config/dconf/user is missing when using smb3:
--- home-list-smb3.txt 2018-04-24 21:43:54.727520865 +
+++
I'm wondering if this is not related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572132
I see less files when I mount the share with smb3. In particular,
~/.config/dconf/user is missing when using smb3:
--- home-list-smb3.txt 2018-04-24 21:43:54.727520865 +
+++
Ok, the problem is caused by the change in minimum protocol version. In
xenial, smb 1.0 is the default, but in bionic it's 3.0.
In the working xenial case, when I force protocol version 3.0 via
"vers=3.0" in the pam_mount config, I get the same error as in bionic.
The troubleshooting continues!
Ok, the problem is caused by the change in minimum protocol version. In
xenial, smb 1.0 is the default, but in bionic it's 3.0.
In the working xenial case, when I force protocol version 3.0 via
"vers=3.0" in the pam_mount config, I get the same error as in bionic.
The troubleshooting continues!
I was able to reproduce this with a bionic desktop and a home-mounted
cifs share. Same setup but with xenial, and with the same user against
the same windows server, worked just fine.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to
I was able to reproduce this with a bionic desktop and a home-mounted
cifs share. Same setup but with xenial, and with the same user against
the same windows server, worked just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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@nsnx:~$ inotifywait -m /home/andreas/.config/dconf/
Setting up watches.
Watches established.
(run in another terminal: dconf write
Can you please paste me the output of "mount -t cifs" on a system where
this problem isn't happening?
Also, please paste the exact versions of cifs-utils in both cases and
the running kernel.
As for a minimal reproducing case I'm trying to find, does this fail for
you as one of these regular
Can you please paste me the output of "mount -t cifs" on a system where
this problem isn't happening?
Also, please paste the exact versions of cifs-utils in both cases and
the running kernel.
As for a minimal reproducing case I'm trying to find, does this fail for
you as one of these regular
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@nsnx:~$ inotifywait -m /home/andreas/.config/dconf/
Setting up watches.
Watches established.
(run in another terminal: dconf write
Not that I can see. At the time of trying to change an icon in the
sidebar, no errors are output to dmesg (tried with dmesg -Tw, dmesg -w
and just dmesg without arguments). The last error before that is:
[Mo Apr 23 18:12:56 2018] CIFS VFS: Send error in SessSetup = -2
[Mo Apr 23 18:12:56 2018]
Do you have apparmor DENIED errors in your dmesg output? Or other maybe
relevant messages there that match the timing of the "g_rename() failed"
error?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to libpam-mount in Ubuntu.
Do you have apparmor DENIED errors in your dmesg output? Or other maybe
relevant messages there that match the timing of the "g_rename() failed"
error?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Did you sanitize this log and replace the real user with "USER"? Yes I
did.
Can you verify if you can do simple file operations in that directory?
Create a file, mv it to another name in the same path, *as* the user
(not root or somebody else)? Indeed I am able to do all those things
without
This permission denied error looks relevant:
Apr 23 09:50:12 CLIENT gnome-shell[3975]: failed to commit changes to
dconf:
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2:
Failed to rename file “/home/USER/.config/dconf/user.ZHTTHZ” to
This permission denied error looks relevant:
Apr 23 09:50:12 CLIENT gnome-shell[3975]: failed to commit changes to
dconf:
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2:
Failed to rename file “/home/USER/.config/dconf/user.ZHTTHZ” to
Setting ad_gpo_access_control to disabled did not solve the problem.
I can confirm, that all files in the domain users mounted homefolder are
owned by the user with the rights set to 700.
In the timeframe i tried to trigger the error, the only entrances in
/var/log/syslog were:
Apr 23 09:50:10
Thanks for the feedback.
I haven't tried the sssd gpo controls myself yet, and I see you have
them set at "permissive", which tells me it would not be preventing
users from changing things. But let's say there is a bug in that area,
would the GPO controls be able to cause what you are seeing?
Thanks for the feedback.
I haven't tried the sssd gpo controls myself yet, and I see you have
them set at "permissive", which tells me it would not be preventing
users from changing things. But let's say there is a bug in that area,
would the GPO controls be able to cause what you are seeing?
Just to be clear: We are not 100% sure, the problem is not in our
configuration. We just dont see why the same configuration would yield
such different results between 16.04 and 18.04.
This is our sssd.conf
[sssd]
config_file_version = 2
services = nss,pam
domains = domain.domain
[nss]
[pam]
As we are not understanding the problem ourselves, we are not in the
position to pinpoint which package is responsible for the problem. SSSD
and pam mount are just the main two packages installed by us for our
domain setup. Thats why I included both of them in the bug report. There
are no problems
Why do you think it's related to pam_mount? Are the mount points mounted
read-only?
Can you show the output of "sudo mount -t cifs"?
** Changed in: sssd (Ubuntu)
Status: New => Incomplete
** Changed in: libpam-mount (Ubuntu)
Status: New => Incomplete
--
You received this bug
Why do you think it's related to pam_mount? Are the mount points mounted
read-only?
Can you show the output of "sudo mount -t cifs"?
** Changed in: sssd (Ubuntu)
Status: New => Incomplete
** Changed in: libpam-mount (Ubuntu)
Status: New => Incomplete
--
You received this bug
** Also affects: libpam-mount (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764778
Title:
Problems with SSSD + pam mount
To manage
** Tags added: regression-release
** Package changed: ubuntu => sssd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764778
Title:
Problems with SSSD + pam mount
To manage notifications
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
35 matches
Mail list logo
