edquota crashes when used with libnss-db
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
quota (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: libnss-db
Hello,
This is from Ubuntu Lucid, libnss-db 2.2.3pre1-
I am using nss-updatedb to get user information from LDAP and I am using nsswitch.conf with the 'db' backend. Everything was fine until I tried to setup quota on one of the machines. edquota segfaults. I changed the backend to 'ldap', and this worked so this showed that the problem is in libnss-db.
LD_PRELOAD=
GNU gdb (GDB) 7.1-ubuntu
[...]
(gdb) run
Starting program: /usr/sbin/edquota -f /home -u bt
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff81ff8f0 in dirname ()
(gdb) bt
#0 0x00007ffff81ff8f0 in dirname ()
#1 0x00007ffff741b893 in ?? () from /usr/lib/
#2 0x00007ffff741a21a in ?? () from /usr/lib/
#3 0x00007ffff741a59b in _nss_db_getpwnam_r () from /usr/lib/
#4 0x00007ffff78d449d in getpwnam_r () from /lib/libc.so.6
#5 0x00007ffff78d3e80 in getpwnam () from /lib/libc.so.6
#6 0x00007ffff7ff4fec in ?? ()
#7 0x00007ffff7ff0a4c in main ()
This was not very communicative, so I recompiled the package without dh_strip, and tried the same:
LD_PRELOAD=
[...]
(gdb) run
Starting program: /usr/sbin/edquota -f /home -u bt
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff81ff8f0 in dirname ()
(gdb) bt
#0 0x00007ffff81ff8f0 in dirname ()
#1 0x00007ffff741b893 in internal_setent (
file=
dbenvp=
#2 0x00007ffff741a21a in lookup (key=0x7fffffff
buffer=
#3 0x00007ffff741a59b in _nss_db_getpwnam_r (name=0x7ffffff
result=
errnop=
#4 0x00007ffff78d449d in getpwnam_r () from /lib/libc.so.6
#5 0x00007ffff78d3e80 in getpwnam () from /lib/libc.so.6
#6 0x00007ffff7ff4fec in ?? ()
#7 0x00007ffff7ff0a4c in main ()
Well, I am no developer, so I don't give a clue about why this fails.
Could somebody please fix it?
Best regards,
Boleslaw Tokarski
Status changed to 'Confirmed' because the bug affects multiple users.