[Bug 1307778] Re: getent group on trusty returns only local groups
** Tags added: utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
** Tags added: utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
Per Michael Wodniok's post, Samba 4.1.13 appears to have fixed the bug with groups that don't have a GID in AD. Samba/Winbind 4.1.13 is available in Ubuntu 15.04 (Vivid). The issue with trying to map a group to SID S-1-18-1 still occurs, and I still see a groups: cannot find name for group ID 10. This appears to interfere with getent groups still. On the other hand, setting a domain group as privileged with visudo and then running sudo commands as a user in that group appears to work, resolving the problem that prompted this bug report. ** Changed in: samba (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
Per Michael Wodniok's post, Samba 4.1.13 appears to have fixed the bug with groups that don't have a GID in AD. Samba/Winbind 4.1.13 is available in Ubuntu 15.04 (Vivid). The issue with trying to map a group to SID S-1-18-1 still occurs, and I still see a groups: cannot find name for group ID 10. This appears to interfere with getent groups still. On the other hand, setting a domain group as privileged with visudo and then running sudo commands as a user in that group appears to work, resolving the problem that prompted this bug report. ** Changed in: samba (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
@Sector That may be a good workaround for some, but for us it won't help as changing to an RID backend would redo all of the UID numbers for users. That would break a number of configured services, and require a significant amount of time to fix. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
@Sector That may be a good workaround for some, but for us it won't help as changing to an RID backend would redo all of the UID numbers for users. That would break a number of configured services, and require a significant amount of time to fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399975] Re: caldendarserver requires postgres binaries in path
Ironically, I just realized that calendarserver does not depend on the postgreSQL, though it should be, or at least, postgresql should be a recommended package. ** Tags added: calendarserver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399975 Title: caldendarserver requires postgres binaries in path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calendarserver/+bug/1399975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399975] [NEW] caldendarserver requires postgres binaries in path
Public bug reported: In calendarserver 5.3 on Ubuntu 14.10, the launch script does not properly launch the server using the default configuration files and the init.d script. This is because calendarserver spawns a child postgreSQL server by default. However, the server expects the binaries located in /usr/lib/postgressql/x.y/bin to be in the path when launching, and exits with an error if they are not. See https://www.calendarserver.org/ticket/397 for an error log under that condition. An easy solution is to edit the calendarserver init script and add the appropriate directory to the path. (See attached init script for the modification). However, my attachment should not be considered a patch as the path is postgreSQL version specific. A more clever programmer could add a few lines to the init script to determine the path, then add it. Per the linked ticket on www.calendarserver.org, this bug appears to have existed since at least 10.04 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: calendarserver 5.2+dfsg-1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sat Dec 6 11:36:44 2014 InstallationDate: Installed on 2014-12-05 (0 days ago) InstallationMedia: Ubuntu-Server 14.10 Utopic Unicorn - Release amd64 (20141022.2) ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: calendarserver UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.caldavd.caldavd.plist: [modified] modified.conffile..etc.default.calendarserver: [modified] mtime.conffile..etc.caldavd.caldavd.plist: 2014-12-06T11:01:09.819860 mtime.conffile..etc.default.calendarserver: 2014-12-06T08:22:46.171443 mtime.conffile..etc.init.d.calendarserver: 2014-12-06T09:33:52.195770 ** Affects: calendarserver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug calendarserver utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399975 Title: caldendarserver requires postgres binaries in path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calendarserver/+bug/1399975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
I believe I have tracked down the source of this bug, which will hopefully lead to an easy fix. The problem appears to be the inability of SID S-1-18-1 to be mapped (See https://support.microsoft.com/kb/2830145 for an explanation why). Winbind gets a list of all groups, and that SID is returned, then attempts to map them to GIDs but fails because that SID cannot be mapped. If one runs: wbinfo -U [uid] then takes the SID that results and does wbinfo --user-sids=[users SID] a list of groups will be returned, along with the users SID. I am able to map all of them back to objects/groups in the domain, except for the S-1-18-1 SID. This nicely matches the output of groups [user] which on my machine returns all of the groups I belong to, except for one, for which the command returns groups: cannot find name for group ID 10, where 10 is the beginning of the idmap * range in smb.conf. I am almost certain the GID 10 corresponds to the unmappable S-1-18-1 SID and is the reason getent group only returns local groups. A patch may be as simple as winbind just ignoring S-1-18-1 and S-1-18-2 when returned as an SID for a group. This appears to have been the behavior for earlier versions of winbind, as running wbinfo -s [user SID] on a centos 6 machine using Samba 3.6 returns all of the SIDs for the user's groups, except the bad S-1-18-1 SID. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
I believe I have tracked down the source of this bug, which will hopefully lead to an easy fix. The problem appears to be the inability of SID S-1-18-1 to be mapped (See https://support.microsoft.com/kb/2830145 for an explanation why). Winbind gets a list of all groups, and that SID is returned, then attempts to map them to GIDs but fails because that SID cannot be mapped. If one runs: wbinfo -U [uid] then takes the SID that results and does wbinfo --user-sids=[users SID] a list of groups will be returned, along with the users SID. I am able to map all of them back to objects/groups in the domain, except for the S-1-18-1 SID. This nicely matches the output of groups [user] which on my machine returns all of the groups I belong to, except for one, for which the command returns groups: cannot find name for group ID 10, where 10 is the beginning of the idmap * range in smb.conf. I am almost certain the GID 10 corresponds to the unmappable S-1-18-1 SID and is the reason getent group only returns local groups. A patch may be as simple as winbind just ignoring S-1-18-1 and S-1-18-2 when returned as an SID for a group. This appears to have been the behavior for earlier versions of winbind, as running wbinfo -s [user SID] on a centos 6 machine using Samba 3.6 returns all of the SIDs for the user's groups, except the bad S-1-18-1 SID. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
I added a gid to two different groups within the AD/OU. This does fix the -1 GIDs, as evidenced by the replacement of one of the -1's with GIDs 2002 and 2003 for the two different groups, one for each user: For the same user as shown above (see the appearance of the 2003): user@Host:~$ wbinfo -r user 2001 -1 2003 1 -1 -1 12 11 For an alternate user who had 2003 appear in place of the -1: user@Host:~$ wbinfo -r user2 2001 -1 2002 12 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
I added a gid to two different groups within the AD/OU. This does fix the -1 GIDs, as evidenced by the replacement of one of the -1's with GIDs 2002 and 2003 for the two different groups, one for each user: For the same user as shown above (see the appearance of the 2003): user@Host:~$ wbinfo -r user 2001 -1 2003 1 -1 -1 12 11 For an alternate user who had 2003 appear in place of the -1: user@Host:~$ wbinfo -r user2 2001 -1 2002 12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
** Description changed: On Trusty, winbind version: 2:4.1.6+dfsg-1ubuntu2 returns groups with GID = -1 when using wbinfo -r: - user@host:~$ wbinfo -r [user] + user@host:~$ wbinfo -r user 2001 -1 -1 1 -1 -1 12 11 On Saucy, winbind 2:3.6.18-1ubuntu3.2 returned only groups with valid GIDs as defined in the active directory using the same command: user@otherhost:~$ wbinfo -r user 2001 1 - With this configuration, getent group returns only local groups. The - same thing happens on a groups command run by the user at a prompt. - However, if groups [user] is run, it returns the defined active - directory groups, as well as a number of errors: + With this configuration on a Trusty host, getent group returns only + local groups (it does not even enumerate the active directory groups + with GIDs 2001 1): The same thing happens on a groups command + run by the user at a prompt. However, if groups [user] is run, it + returns the defined active directory groups, as well as a number of + errors (line breaks added to output for readability): + + user@host:~$ groups + localgroup1 sudo user@host:~$ groups user - user : localgroup1 sudo - groups: cannot find name for group ID 4294967295 4294967295 - groups: cannot find name for group ID 4294967295 4294967295 - domain admins - groups: cannot find name for group ID 4294967295 4294967295 - groups: cannot find name for group ID 4294967295 4294967295 - BUILTIN\users + user : localgroup1 sudo + groups: cannot find name for group ID 4294967295 4294967295 + groups: cannot find name for group ID 4294967295 4294967295 + domain admins + groups: cannot find name for group ID 4294967295 4294967295 + groups: cannot find name for group ID 4294967295 4294967295 + BUILTIN\users BUILTIN\administrators The groups on the Trusty host with GIDs 11 and 12 as returned by - wbinfo -r belong to BUILTIN\administrator and BUILTIN\users respectively - (per wbinfo --gid-info=11), neither of which have defined GIDs in - the active directory. There are several others groups within the user's - OU that also do not have GIDs, and I suspect the -1 values belong to - those groups. + wbinfo -r belong to BUILTIN\administrator and BUILTIN\users + respectively (per wbinfo --gid-info=11), neither of which have + defined GIDs in the active directory. There are several others groups + within the user's OU that also do not have GIDs, and I suspect the -1 + values belong to those groups. I am not sure why the BUILTIN groups get assigned a dynamic GID (as set - by the idmap config * : range = 10-20 line in smb.conf) when + by the idmap config * : range = 10-30 line in smb.conf) when they have no LDAP gidNumber assigned to them, while the other groups inside our OU get assigned gid -1 when they also have no gidNumber assigned to them. The smb.conf file is identical between the two hosts except for the server name string. The non-working host was upgraded from Saucy to Trusty today. Two other hosts were also upgraded, and they show exactly the same behavior. This issue breaks domain-wide administrative powers, as we use visudo to give members of the domain admins group local administrative permissions - on all machines. + on all machines. sudo commands run on the Trusty host by a domain + admin member not also in the local sudo group fail, declaring the user + is not one of the sudoers - Notably, getent passwd returns local and domain users, and users are - able to login with correct UIDs using domain accounts. + Notably, getent passwd returns all local and domain users, and domain + users remain able to login with correct UIDs using domain accounts. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libnss-winbind 2:4.1.6+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Mon Apr 14 18:50:45 2014 InstallationDate: Installed on 2014-02-13 (60 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash SambaClientRegression: Yes SourcePackage: samba UpgradeStatus: Upgraded to trusty on 2014-04-15 (0 days ago) ** Description changed: On Trusty, winbind version: 2:4.1.6+dfsg-1ubuntu2 returns groups with GID = -1 when using wbinfo -r: user@host:~$ wbinfo -r user 2001 -1 -1 1 -1 -1 12 11 On Saucy, winbind 2:3.6.18-1ubuntu3.2 returned only groups with valid GIDs as defined in the active directory using the same command: user@otherhost:~$ wbinfo -r user 2001 1 With this configuration on a Trusty host, getent group
[Bug 1307778] Re: getent group on trusty returns only local groups
description was updated to clean up grammar and add clarity. Nothing substantive was changed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
** Description changed: On Trusty, winbind version: 2:4.1.6+dfsg-1ubuntu2 returns groups with GID = -1 when using wbinfo -r: - user@host:~$ wbinfo -r [user] + user@host:~$ wbinfo -r user 2001 -1 -1 1 -1 -1 12 11 On Saucy, winbind 2:3.6.18-1ubuntu3.2 returned only groups with valid GIDs as defined in the active directory using the same command: user@otherhost:~$ wbinfo -r user 2001 1 - With this configuration, getent group returns only local groups. The - same thing happens on a groups command run by the user at a prompt. - However, if groups [user] is run, it returns the defined active - directory groups, as well as a number of errors: + With this configuration on a Trusty host, getent group returns only + local groups (it does not even enumerate the active directory groups + with GIDs 2001 1): The same thing happens on a groups command + run by the user at a prompt. However, if groups [user] is run, it + returns the defined active directory groups, as well as a number of + errors (line breaks added to output for readability): + + user@host:~$ groups + localgroup1 sudo user@host:~$ groups user - user : localgroup1 sudo - groups: cannot find name for group ID 4294967295 4294967295 - groups: cannot find name for group ID 4294967295 4294967295 - domain admins - groups: cannot find name for group ID 4294967295 4294967295 - groups: cannot find name for group ID 4294967295 4294967295 - BUILTIN\users + user : localgroup1 sudo + groups: cannot find name for group ID 4294967295 4294967295 + groups: cannot find name for group ID 4294967295 4294967295 + domain admins + groups: cannot find name for group ID 4294967295 4294967295 + groups: cannot find name for group ID 4294967295 4294967295 + BUILTIN\users BUILTIN\administrators The groups on the Trusty host with GIDs 11 and 12 as returned by - wbinfo -r belong to BUILTIN\administrator and BUILTIN\users respectively - (per wbinfo --gid-info=11), neither of which have defined GIDs in - the active directory. There are several others groups within the user's - OU that also do not have GIDs, and I suspect the -1 values belong to - those groups. + wbinfo -r belong to BUILTIN\administrator and BUILTIN\users + respectively (per wbinfo --gid-info=11), neither of which have + defined GIDs in the active directory. There are several others groups + within the user's OU that also do not have GIDs, and I suspect the -1 + values belong to those groups. I am not sure why the BUILTIN groups get assigned a dynamic GID (as set - by the idmap config * : range = 10-20 line in smb.conf) when + by the idmap config * : range = 10-30 line in smb.conf) when they have no LDAP gidNumber assigned to them, while the other groups inside our OU get assigned gid -1 when they also have no gidNumber assigned to them. The smb.conf file is identical between the two hosts except for the server name string. The non-working host was upgraded from Saucy to Trusty today. Two other hosts were also upgraded, and they show exactly the same behavior. This issue breaks domain-wide administrative powers, as we use visudo to give members of the domain admins group local administrative permissions - on all machines. + on all machines. sudo commands run on the Trusty host by a domain + admin member not also in the local sudo group fail, declaring the user + is not one of the sudoers - Notably, getent passwd returns local and domain users, and users are - able to login with correct UIDs using domain accounts. + Notably, getent passwd returns all local and domain users, and domain + users remain able to login with correct UIDs using domain accounts. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libnss-winbind 2:4.1.6+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Mon Apr 14 18:50:45 2014 InstallationDate: Installed on 2014-02-13 (60 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash SambaClientRegression: Yes SourcePackage: samba UpgradeStatus: Upgraded to trusty on 2014-04-15 (0 days ago) ** Description changed: On Trusty, winbind version: 2:4.1.6+dfsg-1ubuntu2 returns groups with GID = -1 when using wbinfo -r: user@host:~$ wbinfo -r user 2001 -1 -1 1 -1 -1 12 11 On Saucy, winbind 2:3.6.18-1ubuntu3.2 returned only groups with valid GIDs as defined in the active directory using the same command: user@otherhost:~$ wbinfo -r user 2001 1 With this configuration on a Trusty host, getent group
[Bug 1307778] Re: getent group on trusty returns only local groups
description was updated to clean up grammar and add clarity. Nothing substantive was changed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307778] [NEW] getent group on trusty returns only local groups
Public bug reported: On Trusty, winbind version: 2:4.1.6+dfsg-1ubuntu2 returns groups with GID = -1 when using wbinfo -r: user@host:~$ wbinfo -r [user] 2001 -1 -1 1 -1 -1 12 11 On Saucy, winbind 2:3.6.18-1ubuntu3.2 returned only groups with valid GIDs as defined in the active directory using the same command: user@otherhost:~$ wbinfo -r user 2001 1 With this configuration, getent group returns only local groups. The same thing happens on a groups command run by the user at a prompt. However, if groups [user] is run, it returns the defined active directory groups, as well as a number of errors: user@host:~$ groups user user : localgroup1 sudo groups: cannot find name for group ID 4294967295 4294967295 groups: cannot find name for group ID 4294967295 4294967295 domain admins groups: cannot find name for group ID 4294967295 4294967295 groups: cannot find name for group ID 4294967295 4294967295 BUILTIN\users BUILTIN\administrators The groups on the Trusty host with GIDs 11 and 12 as returned by wbinfo -r belong to BUILTIN\administrator and BUILTIN\users respectively (per wbinfo --gid-info=11), neither of which have defined GIDs in the active directory. There are several others groups within the user's OU that also do not have GIDs, and I suspect the -1 values belong to those groups. I am not sure why the BUILTIN groups get assigned a dynamic GID (as set by the idmap config * : range = 10-20 line in smb.conf) when they have no LDAP gidNumber assigned to them, while the other groups inside our OU get assigned gid -1 when they also have no gidNumber assigned to them. The smb.conf file is identical between the two hosts except for the server name string. The non-working host was upgraded from Saucy to Trusty today. Two other hosts were also upgraded, and they show exactly the same behavior. This issue breaks domain-wide administrative powers, as we use visudo to give members of the domain admins group local administrative permissions on all machines. Notably, getent passwd returns local and domain users, and users are able to login with correct UIDs using domain accounts. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libnss-winbind 2:4.1.6+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Mon Apr 14 18:50:45 2014 InstallationDate: Installed on 2014-02-13 (60 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SambaClientRegression: Yes SourcePackage: samba UpgradeStatus: Upgraded to trusty on 2014-04-15 (0 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
Attached smb.conf with workgroup and hostnames changed to generics. ** Attachment added: smb.conf from Trusty host https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+attachment/4083984/+files/smb.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
I forgot to comment that I added extra line breaks to the output of groups user for readability of the bug report. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
I forgot to comment that I added extra line breaks to the output of groups user for readability of the bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307778] [NEW] getent group on trusty returns only local groups
Public bug reported: On Trusty, winbind version: 2:4.1.6+dfsg-1ubuntu2 returns groups with GID = -1 when using wbinfo -r: user@host:~$ wbinfo -r [user] 2001 -1 -1 1 -1 -1 12 11 On Saucy, winbind 2:3.6.18-1ubuntu3.2 returned only groups with valid GIDs as defined in the active directory using the same command: user@otherhost:~$ wbinfo -r user 2001 1 With this configuration, getent group returns only local groups. The same thing happens on a groups command run by the user at a prompt. However, if groups [user] is run, it returns the defined active directory groups, as well as a number of errors: user@host:~$ groups user user : localgroup1 sudo groups: cannot find name for group ID 4294967295 4294967295 groups: cannot find name for group ID 4294967295 4294967295 domain admins groups: cannot find name for group ID 4294967295 4294967295 groups: cannot find name for group ID 4294967295 4294967295 BUILTIN\users BUILTIN\administrators The groups on the Trusty host with GIDs 11 and 12 as returned by wbinfo -r belong to BUILTIN\administrator and BUILTIN\users respectively (per wbinfo --gid-info=11), neither of which have defined GIDs in the active directory. There are several others groups within the user's OU that also do not have GIDs, and I suspect the -1 values belong to those groups. I am not sure why the BUILTIN groups get assigned a dynamic GID (as set by the idmap config * : range = 10-20 line in smb.conf) when they have no LDAP gidNumber assigned to them, while the other groups inside our OU get assigned gid -1 when they also have no gidNumber assigned to them. The smb.conf file is identical between the two hosts except for the server name string. The non-working host was upgraded from Saucy to Trusty today. Two other hosts were also upgraded, and they show exactly the same behavior. This issue breaks domain-wide administrative powers, as we use visudo to give members of the domain admins group local administrative permissions on all machines. Notably, getent passwd returns local and domain users, and users are able to login with correct UIDs using domain accounts. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libnss-winbind 2:4.1.6+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Mon Apr 14 18:50:45 2014 InstallationDate: Installed on 2014-02-13 (60 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SambaClientRegression: Yes SourcePackage: samba UpgradeStatus: Upgraded to trusty on 2014-04-15 (0 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307778] Re: getent group on trusty returns only local groups
Attached smb.conf with workgroup and hostnames changed to generics. ** Attachment added: smb.conf from Trusty host https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+attachment/4083984/+files/smb.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307778 Title: getent group on trusty returns only local groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 709505] Re: [MASTER] fglrx failed to install/upgrade due to being incompatible with 2.6.38 kernel
With the current fglrx package version available in the repos, DKMS fails to build the module due to kernel changes removing the big kernel lock. So, as filed and as stands, the title is correct. I don't believe 11.2 is available pre-packaged in the natty repos yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709505 Title: [MASTER] fglrx failed to install/upgrade due to being incompatible with 2.6.38 kernel -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 729997] [NEW] package fglrx 2:8.801-0ubuntu3 failed to install/upgrade: fglrx kernel module failed to build
Public bug reported: attached is the make.log with the included errors: ProblemType: Package DistroRelease: Ubuntu 11.04 Package: fglrx 2:8.801-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic x86_64 Architecture: amd64 Date: Sat Mar 5 20:20:11 2011 DistUpgraded: Log time: 2011-02-24 19:29:12.563490 DistroCodename: natty DistroVariant: ubuntu ErrorMessage: fglrx kernel module failed to build PackageVersion: 2:8.801-0ubuntu3 SourcePackage: fglrx-installer Title: package fglrx 2:8.801-0ubuntu3 failed to install/upgrade: fglrx kernel module failed to build UpgradeStatus: Upgraded to natty on 2011-02-25 (9 days ago) version.compiz: compiz 1:0.9.4-0ubuntu3 version.libdrm2: libdrm2 2.4.23-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1~git20110215.cc1636b6-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu5 ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package natty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/729997 Title: package fglrx 2:8.801-0ubuntu3 failed to install/upgrade: fglrx kernel module failed to build -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 729997] Re: package fglrx 2:8.801-0ubuntu3 failed to install/upgrade: fglrx kernel module failed to build
** Attachment added: make.log https://bugs.launchpad.net/bugs/729997/+attachment/1889045/+files/make.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/729997 Title: package fglrx 2:8.801-0ubuntu3 failed to install/upgrade: fglrx kernel module failed to build -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 717999] Re: indicator-sound-service crashed with SIGSEGV in g_variant_builder_add_value()
I have been running daily updates to stay current with package versions. Last night, something got upgraded and sound started to work on my internal sound card but, although not on my video card based HDMI-out. Along with those changes this crash appeared to stop happening. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/717999 Title: indicator-sound-service crashed with SIGSEGV in g_variant_builder_add_value() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 717999] Re: indicator-sound-service crashed with SIGSEGV in g_variant_builder_add_value()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/717999 Title: indicator-sound-service crashed with SIGSEGV in g_variant_builder_add_value() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 717309] Re: software-center crashed with DatabaseModifiedError in get_pkgname(): The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/717309 Title: software-center crashed with DatabaseModifiedError in get_pkgname(): The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 717309] Re: software-center crashed with DatabaseModifiedError in get_pkgname(): The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation
I have been running alpha 2 since it's release date, so the bug is regressive to at least that point. Also, if I keep software-center open, the same bug is triggered repeatedly even without user action, causing a crash reporter window to pop every 2 minutes or so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/717309 Title: software-center crashed with DatabaseModifiedError in get_pkgname(): The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365772] Re: in Jaunty, mount.nfs fails with mount(2): Input/output error
I tried connecting to the same file server with the same command on another box with a fresh install of Jaunty x64 and the command works with no issues. I am going to attempt to reformat this box and see if that fixes the problem. -- in Jaunty, mount.nfs fails with mount(2): Input/output error https://bugs.launchpad.net/bugs/365772 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365772] Re: in Jaunty, mount.nfs fails with mount(2): Input/output error
In my case, the bug appears to be due to a firewall change on the server banning this specific client's IP from connecting that happened coincidentally while upgrading to Jaunty. I am marking the bug as invalid, as it's not really a bug. ** Changed in: nfs-utils (Ubuntu) Status: Confirmed = Invalid -- in Jaunty, mount.nfs fails with mount(2): Input/output error https://bugs.launchpad.net/bugs/365772 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365772] Re: in Jaunty, mount.nfs fails with mount(2): Input/output error
If I run the command as Kaustubh Srikanth runs, replacing the relevant entries with my server and share, I get identical output. Results of the uname are: Linux 2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:31:32 UTC 2009 -- in Jaunty, mount.nfs fails with mount(2): Input/output error https://bugs.launchpad.net/bugs/365772 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365772] Re: in Jaunty, mount.nfs fails with mount(2): Input/output error
Multiple persons comment having identical problems, so changing from new to confirmed. ** Changed in: nfs-utils (Ubuntu) Status: New = Confirmed -- in Jaunty, mount.nfs fails with mount(2): Input/output error https://bugs.launchpad.net/bugs/365772 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365772] [NEW] in Jaunty, mount.nfs fails with mount(2): Input/output error
Public bug reported: Binary package hint: nfs-common For some time I was affected by bug #213444, preventing me from mounting an NFS share since Ubuntu 8.04 (Heron). That bug appears to have been fixed (for a short time i was able to mount successfully), but now I get an additional series of errors in Jaunty when trying to mount an NFS share: call: sudo mount -t nfs -o nolock - fileserver:/remoteMount localmount which returns: mount.nfs: mount(2): Input/output error and mount.nfs: mount system call failed. We have a number of other linux systems around, running different distributions, mostly CentOS, which have no problem mounting the server. Of interest may be a link dumped into the system logs: muscat kernel: [ 979.924016] rpcbind: server fileserver not responding, timed out However, I think that's probably a red herring, as mount typically responds with a different error message on time out, and other computers are able to reach the NFS server without difficulty. iptables has no rules set up, and portmapper is running. I have also tried -o nolock (as you can see), but it appears I am affected by a different problem than bug #306016. Package is version 1:1.1.4-1ubuntu1 ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: nfs-common For some time I was affected by bug #213444, preventing me from mounting - an NFS share since Ubuntu 8.04 (Gutsy). That bug appears to have been + an NFS share since Ubuntu 8.04 (Heron). That bug appears to have been fixed (for a short time i was able to mount successfully), but now I get an additional series of errors in Jaunty when trying to mount an NFS share: call: sudo mount -t nfs -o nolock - fileserver:/remoteMount localmount which returns: mount.nfs: mount(2): Input/output error and mount.nfs: mount system call failed. We have a number of other linux systems around, running different distributions, mostly CentOS, which have no problem mounting the server. Of interest may be a link dumped into the system logs: muscat kernel: [ 979.924016] rpcbind: server fileserver not responding, timed out However, I think that's probably a red herring, as mount typically responds with a different error message on time out, and other computers are able to reach the NFS server without difficulty. iptables has no rules set up, and portmapper is running. I have also tried -o nolock (as you can see), but it appears I am affected by a different problem than bug #306016. Package is version 1:1.1.4-1ubuntu1 -- in Jaunty, mount.nfs fails with mount(2): Input/output error https://bugs.launchpad.net/bugs/365772 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279262] Re: network-manager After reboot network is totally broken
my interfaces file was similar to Kadafi's, though I do not have a wireless interface. A workaround to the problem is to simply removed the static section and leave only the 'auto eth0' line, then reboot (some command may refresh the interface without the reboot, but ifconfig eth0 down/up does not). Of course, this is not a suitable workaround for those requiring a static configuration, but does suffice for those who can make-do with DHCP temporarily. -- network-manager After reboot network is totally broken https://bugs.launchpad.net/bugs/279262 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
