Problem after I upgrade pacman to 3.1.0

subset · 2008-01-13 09:33:25

I have this message after I upgrade pacman to 3.1.0:

[root@xxxx ~]# pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Targets: alunn-0.7.1.3-1  compiz-core-0.6.2-4  compiz-decorator-gtk-0.6.2-5  
         device-mapper-1.02.24-1  lvm2-2.02.29-1  ntfs-3g-1.1120-1  
         syslog-ng-2.0.6-1  

Total Download Size:    2.11 MB
Total Installed Size:   5.21 MB

Proceed with installation? [Y/n] y
*** glibc detected *** pacman: double free or corruption (out): 0x08908520 ***
======= Backtrace: =========
/lib/libc.so.6[0xb7d98836]
/lib/libc.so.6(cfree+0x89)[0xb7d9a4d9]
/usr/lib/libalpm.so.2(alpm_list_free_inner+0x23)[0xb7ecdd03]
/usr/lib/libalpm.so.2(alpm_option_set_cachedirs+0x39)[0xb7ed6a59]
/usr/lib/libalpm.so.2[0xb7ee2a12]
/usr/lib/libalpm.so.2[0xb7eddff9]
/usr/lib/libalpm.so.2[0xb7ee086b]
/usr/lib/libalpm.so.2(alpm_trans_commit+0x3e)[0xb7ee094e]
pacman[0x8050d9f]
pacman[0x804e97d]
/lib/libc.so.6(__libc_start_main+0xe0)[0xb7d47390]
pacman[0x804b041]
======= Memory map: ========
08048000-08058000 r-xp 00000000 08:02 100218     /usr/bin/pacman
08058000-08059000 rw-p 0000f000 08:02 100218     /usr/bin/pacman
08059000-089a1000 rw-p 08059000 00:00 0          [heap]
b7900000-b7921000 rw-p b7900000 00:00 0 
b7921000-b7a00000 ---p b7921000 00:00 0 
b7b09000-b7b17000 r-xp 00000000 08:02 832        /lib/libresolv-2.7.so
b7b17000-b7b19000 rw-p 0000d000 08:02 832        /lib/libresolv-2.7.so
b7b19000-b7b1b000 rw-p b7b19000 00:00 0 
b7b24000-b7b2e000 r-xp 00000000 08:02 98155      /usr/lib/libgcc_s.so.1
b7b2e000-b7b2f000 rw-p 00009000 08:02 98155      /usr/lib/libgcc_s.so.1
b7b2f000-b7b30000 rw-p b7b2f000 00:00 0 
b7b30000-b7d30000 r--p 00000000 08:02 99239      /usr/lib/locale/locale-archive
b7d30000-b7d31000 rw-p b7d30000 00:00 0 
b7d31000-b7e61000 r-xp 00000000 08:02 2342       /lib/libc-2.7.so
b7e61000-b7e62000 r--p 00130000 08:02 2342       /lib/libc-2.7.so
b7e62000-b7e64000 rw-p 00131000 08:02 2342       /lib/libc-2.7.so
b7e64000-b7e67000 rw-p b7e64000 00:00 0 
b7e67000-b7e76000 r-xp 00000000 08:02 882        /lib/libbz2.so.1.0.4
b7e76000-b7e77000 rw-p 0000f000 08:02 882        /lib/libbz2.so.1.0.4
b7e77000-b7e78000 rw-p b7e77000 00:00 0 
b7e78000-b7e89000 r-xp 00000000 08:02 2373       /lib/libz.so.1.2.3
b7e89000-b7e8a000 rw-p 00010000 08:02 2373       /lib/libz.so.1.2.3
b7e8a000-b7e8d000 r-xp 00000000 08:02 870        /lib/libattr.so.1.1.0
b7e8d000-b7e8e000 rw-p 00002000 08:02 870        /lib/libattr.so.1.1.0
b7e8e000-b7e94000 r-xp 00000000 08:02 872        /lib/libacl.so.1.1.0
b7e94000-b7e95000 rw-p 00005000 08:02 872        /lib/libacl.so.1.1.0
b7e95000-b7eba000 r-xp 00000000 08:02 99504      /usr/lib/libarchive.so.2.4.11
b7eba000-b7ebb000 rw-p 00025000 08:02 99504      /usr/lib/libarchive.so.2.4.11
b7ebb000-b7ebc000 rw-p b7ebb000 00:00 0 
b7ebc000-b7ec6000 r-xp 00000000 08:02 99514      /usr/lib/libdownload.so
b7ec6000-b7ec7000 rw-p 0000a000 08:02 99514      /usr/lib/libdownload.so
b7ec7000-b7eea000 r-xp 00000000 08:02 100203     /usr/lib/libalpm.so.2.0.0
b7eea000-b7eeb000 rw-p 00022000 08:02 100203     /usr/lib/libalpm.so.2.0.0
b7eeb000-b7eec000 rw-p b7eeb000 00:00 0 
b7eee000-b7ef2000 r-xp 00000000 08:02 859        /lib/libnss_dns-2.7.so
b7ef2000-b7ef4000 rw-p 00003000 08:02 859        /lib/libnss_dns-2.7.so
b7ef4000-b7efd000 r-xp 00000000 08:02 853        /lib/libnss_files-2.7.so
b7efd000-b7eff000 rw-p 00008000 08:02 853        /lib/libnss_files-2.7.so
b7eff000-b7f01000 rw-p b7eff000 00:00 0 
b7f01000-b7f02000 r-xp b7f01000 00:00 0          [vdso]
b7f02000-b7f1c000 r-xp 00000000 08:02 826        /lib/ld-2.7.so
b7f1c000-b7f1e000 rw-p 0001a000 08:02 826        /lib/ld-2.7.so
bfd0d000-bfd22000 rw-p bffeb000 00:00 0          [stack]
Aborted

Thx

Last edited by subset (2008-01-13 09:33:56)

shining · 2008-01-13 10:23:53

Right, known issue, at least the segfault will be fixed in 3.1.1 .
Could you please show me the permission of the cache dir :
ls -l /var/cache/pacman/pkg
If it's a symlink, the permission of the target also. Thanks

Edit : bug reported here : http://bugs.archlinux.org/task/9186

Last edited by shining (2008-01-13 10:33:01)

subset · 2008-01-13 10:50:51

Here is some:
root@x# ls -l /var/cache/pacman/pkg

-rw-r--r-- 1 root root     14743 2007-12-17 11:17 xorg-xinit-1.0.7-2-i686.pkg.tar.gz
-r--r--r-- 1 root root    164582 2007-12-03 16:23 xorg-xkb-utils-1.0.2-2.pkg.tar.gz
-r--r--r-- 1 root root     69282 2007-12-03 16:23 xorg-xsm-1.0.1-2.pkg.tar.gz
-r--r--r-- 1 root root     78458 2007-12-03 16:22 xproto-7.0.11-1-i686.pkg.tar.gz
-rw-r--r-- 1 root root    345465 2007-12-14 11:11 xsp-1.2.6-1-i686.pkg.tar.gz
-r--r--r-- 1 root root    205055 2007-12-03 16:22 xterm-229-2.pkg.tar.gz
-r--r--r-- 1 root root     56158 2007-12-03 16:21 xtrans-1.0.4-1.pkg.tar.gz
-r--r--r-- 1 root root  11241708 2007-12-03 16:23 xulrunner-1.8.1.9-1-i686.pkg.tar.gz
-r--r--r-- 1 root root    470003 2007-12-03 16:22 xvidcore-1.1.3-1.pkg.tar.gz
-rw-r--r-- 1 root root    623874 2007-12-05 18:19 yelp-2.20.0-2-i686.pkg.tar.gz
-r--r--r-- 1 root root    920399 2007-12-03 16:23 your-freedom-20071031-1.pkg.tar.gz
-rw-r--r-- 1 root root   1941795 2007-12-26 22:54 zenity-2.20.1-1-i686.pkg.tar.gz
-r--r--r-- 1 root root     71767 2007-12-03 16:22 zip-2.32-1.pkg.tar.gz
-rw-r--r-- 1 root root    107651 2007-12-03 16:22 zlib-1.2.3-4-i686.pkg.tar.gz
-rw-r--r-- 1 root root    694211 2007-12-25 11:54 zope-interface-3.3.0-2.pkg.tar.gz

Thx

shining · 2008-01-13 10:57:15

Sorry, I am stupid. What I meant is : ls -ld /var/cache/pacman/pkg

subset · 2008-01-13 20:31:27

Here is

[root@x ~]# ls -ld /var/cache/pacman/pkg/
dr-xr-xr-x 2 root root 57344 2008-01-12 23:58 /var/cache/pacman/pkg/

shining · 2008-01-13 21:06:53

Yes, that's it, your /var/cache/pacman/pkg/ is not writable.
Even though root should still be able to write to it, pacman always checks if the cache dir has a write attribute.
If it doesn't, it won't use it.
Anything wrong with running : chmod +w /var/cache/pacman/pkg/ ?

subset · 2008-01-13 23:00:48

shining wrote:

Yes, that's it, your /var/cache/pacman/pkg/ is not writable.
Even though root should still be able to write to it, pacman always checks if the cache dir has a write attribute.
If it doesn't, it won't use it.
Anything wrong with running : chmod +w /var/cache/pacman/pkg/ ?

Hi !

Many-many tanks from Hungary
It is working !!!!

Thx

Arch Linux

#1 2008-01-13 09:33:25

Problem after I upgrade pacman to 3.1.0

#2 2008-01-13 10:23:53

Re: Problem after I upgrade pacman to 3.1.0

#3 2008-01-13 10:50:51

Re: Problem after I upgrade pacman to 3.1.0

#4 2008-01-13 10:57:15

Re: Problem after I upgrade pacman to 3.1.0

#5 2008-01-13 20:31:27

Re: Problem after I upgrade pacman to 3.1.0

#6 2008-01-13 21:06:53

Re: Problem after I upgrade pacman to 3.1.0

#7 2008-01-13 23:00:48

Re: Problem after I upgrade pacman to 3.1.0

Board footer