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 100
** 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.launch
@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
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 locate
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 Ubu
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, t
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
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 g
** 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
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 trus
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 directo
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,
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 notif
** 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-0ubunt
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 2
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 b
** 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
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 notifi
** 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
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 =
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"
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 bec
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://
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 erro
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
25 matches
Mail list logo
