Control: tags -1 found apt/0.9.14.2 Indeed upgrading only libapt-pkg4.12 is enough to trigger this.
On 00:07, Robert Millan wrote: > Does "ktrace -d" yield anything interesting? Or maybe one of dpkg's > debug flags? (see dpkg --debug=help) I think this is the interesting part: 6058 apt-get CALL read(0xd,0x7fffffffbd10,0x400) 6058 apt-get GIO fd 13 read 0 bytes "" 6058 apt-get RET read 0 6058 apt-get CALL wait4(0x19ed,0x7fffffffc330,0x1<WNOHANG>,0) 6058 apt-get RET wait4 0 6058 apt-get CALL pselect(0x10,0x7fffffffc3c0,0,0,0x7fffffffc2c0,0xb39b4c) 6058 apt-get RET pselect 1 6637 dpkg RET fsync 0 6637 dpkg CALL close(0x8) 6637 dpkg RET close 0 6637 dpkg CALL close(0x4) 6637 dpkg RET close 0 6637 dpkg CALL munmap(0x8007f8000,0x4000) 6637 dpkg RET munmap 0 6637 dpkg CALL unlink(0x753d20) 6637 dpkg NAMI "/var/lib/dpkg/updates/tmp.i" 6637 dpkg RET unlink 0 6637 dpkg CALL fcntl(0x3,<invalid=8>,0xffffffffffffd2c0) 6637 dpkg RET fcntl 0 6637 dpkg CALL write(0x2,0x42a788,0x2a) 6637 dpkg RET write -1 errno 6 No such device or address 6637 dpkg CALL write(0x2,0x800bb70a3,0x1) 6637 dpkg RET write -1 errno 6 No such device or address 6637 dpkg CALL write(0x2,0x7fffffffac00,0x6) 6637 dpkg RET write -1 errno 6 No such device or address 6637 dpkg CALL write(0x2,0x800bb70a3,0x1) 6637 dpkg RET write -1 errno 6 No such device or address 6637 dpkg CALL exit(0x1) 6058 apt-get CALL read(0xd,0x7fffffffbd10,0x400) 6058 apt-get GIO fd 13 read 0 bytes "" 6058 apt-get RET read 0 6058 apt-get CALL wait4(0x19ed,0x7fffffffc330,0x1<WNOHANG>,0) 6058 apt-get RET wait4 0 6058 apt-get CALL pselect(0x10,0x7fffffffc3c0,0,0,0x7fffffffc2c0,0xb39b4c) 6058 apt-get RET pselect 2 Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140112200505.gf8...@squeeze.pyro.eu.org