update failed in latest hardy alpha
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: apt
When I run apt-get update, here is what I get:
sudo apt-get update
Hit http://
Ign http://
Ign http://
Ign http://
Ign http://
Hit http://
Ign http://
Ign http://
Ign http://
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Reading package lists... Done
gary@Sheridan:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
gary@Sheridan:~$ sudo apt-get update
*** glibc detected *** sudo: free(): invalid pointer: 0xb7cebb28 ***
======= Backtrace: =========
/lib/libc.
/lib/libc.
/lib/libc.
/lib/libc.
/lib/libc.
/lib/libc.
/lib/libc.
sudo[0x804ef45]
sudo[0x8050000]
/lib/libc.
sudo[0x804a521]
======= Memory map: ========
08048000-08062000 r-xp 00000000 08:01 27000890 /usr/bin/sudo
08062000-08063000 rw-p 00019000 08:01 27000890 /usr/bin/sudo
08063000-08087000 rw-p 08063000 00:00 0 [heap]
b7cb4000-b7cbe000 r-xp 00000000 08:01 5443675 /lib/libgcc_s.so.1
b7cbe000-b7cbf000 rw-p 0000a000 08:01 5443675 /lib/libgcc_s.so.1
b7cbf000-b7cc8000 r-xp 00000000 08:01 5443120 /lib/libnss_
b7cc8000-b7cca000 rw-p 00008000 08:01 5443120 /lib/libnss_
b7cca000-b7cd2000 r-xp 00000000 08:01 5443122 /lib/libnss_
b7cd2000-b7cd4000 rw-p 00007000 08:01 5443122 /lib/libnss_
b7cd4000-b7ce7000 r-xp 00000000 08:01 5443117 /lib/libnsl-2.7.so
b7ce7000-b7ce9000 rw-p 00012000 08:01 5443117 /lib/libnsl-2.7.so
b7ce9000-b7cec000 rw-p b7ce9000 00:00 0
b7cec000-b7cf2000 r-xp 00000000 08:01 5443118 /lib/libnss_
b7cf2000-b7cf4000 rw-p 00005000 08:01 5443118 /lib/libnss_
b7d04000-b7d43000 r--p 00000000 08:01 27066422 /usr/lib/
b7d43000-b7d44000 r--p 00000000 08:01 27067559 /usr/lib/
b7d44000-b7e25000 r--p 00000000 08:01 27066436 /usr/lib/
b7e25000-b7e26000 rw-p b7e25000 00:00 0
b7e26000-b7f59000 r-xp 00000000 08:01 5443104 /lib/libc-2.7.so
b7f59000-b7f5a000 r--p 00133000 08:01 5443104 /lib/libc-2.7.so
b7f5a000-b7f5c000 rw-p 00134000 08:01 5443104 /lib/libc-2.7.so
b7f5c000-b7f60000 rw-p b7f5c000 00:00 0
b7f60000-b7f62000 r-xp 00000000 08:01 5443113 /lib/libdl-2.7.so
b7f62000-b7f64000 rw-p 00001000 08:01 5443113 /lib/libdl-2.7.so
b7f64000-b7f6d000 r-xp 00000000 08:01 5442848 /lib/libpam.
b7f6d000-b7f6e000 rw-p 00008000 08:01 5442848 /lib/libpam.
b7f6e000-b7f6f000 r--p 00000000 08:01 27066434 /usr/lib/
b7f6f000-b7f70000 r--p 00000000 08:01 27066438 /usr/lib/
b7f70000-b7f71000 r--p 00000000 08:01 27066440 /usr/lib/
b7f71000-b7f72000 r--p 00000000 08:01 27067846 /usr/lib/
b7f72000-b7f73000 r--p 00000000 08:01 27067558 /usr/lib/
b7f73000-b7f74000 r--p 00000000 08:01 27066442 /usr/lib/
b7f74000-b7f75000 r--p 00000000 08:01 27066444 /usr/lib/
b7f75000-b7f76000 r--p 00000000 08:01 27067556 /usr/lib/
b7f76000-b7f7d000 r--s 00000000 08:01 27005092 /usr/lib/
b7f7d000-b7f7e000 r--p 00000000 08:01 27066766 /usr/lib/
b7f7e000-b7f7f000 rw-p b7f7e000 00:00 0
b7f7f000-b7f80000 r-xp b7f7f000 00:00 0 [vdso]
b7f80000-b7f9a000 r-xp 00000000 08:01 5443100 /lib/ld-2.7.so
b7f9a000-b7f9b000 r--p 00019000 08:01 5443100 /lib/ld-2.7.so
b7f9b000-b7f9c000 rw-p 0001a000 08:01 5443100 /lib/ld-2.7.so
bfca0000-bfcb5000 rw-p bffeb000 00:00 0 [stack]
Aborted
gary@Sheridan:~$
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #201673, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.