update-manager hangs during pre-config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
I've noticed this in raring with certain kernel packages (though a re-try usually does fine). Basically it looks like there's some sort of deadlock. I tried attaching apport-bug to the aptd, but it just whined that there was no "program" associated with that pid. Perhaps because it's root?
Here's a snippet of `ps fauxw` to show what's going on:
nick 13113 0.5 3.3 789380 132876 ? SNl 07:36 0:33 /usr/bin/python3 /usr/bin/
nick 13923 0.0 0.8 382532 32932 ? SNl 08:43 0:00 \_ /usr/bin/perl -w /usr/bin/
root 13808 0.1 2.0 262304 80948 ? SNl 08:42 0:04 /usr/bin/python3.3 /usr/sbin/aptd
root 13819 0.0 1.2 262488 49980 pts/16 SNs+ 08:42 0:00 \_ /usr/bin/python3.3 /usr/sbin/aptd
root 13820 0.0 0.0 0 0 pts/16 ZN+ 08:42 0:00 \_ [dpkg] <defunct>
root 13918 0.0 0.0 4440 624 pts/16 SN+ 08:43 0:00 \_ /bin/sh -c /usr/sbin/
root 13919 0.0 0.3 67020 15716 pts/16 SN+ 08:43 0:00 \_ /usr/bin/perl -w /usr/sbin/
root 13921 0.0 0.0 0 0 pts/16 ZN+ 08:43 0:00 \_ [dpkg-preconfigu] <defunct>
I usually just solve this by killing that dpkg-preconfigure process and letting all the apt machinery clean up after it. I'm not sure how to get good debug info out of a running Perl process, but here's open files and an strace -p:
/proc/
total 0
lr-x------ 1 root root 64 Apr 3 09:24 0 -> /dev/tty
lrwx------ 1 root root 64 Apr 3 09:24 1 -> /dev/pts/16
lrwx------ 1 root root 64 Apr 3 09:24 2 -> /dev/pts/16
lrwx------ 1 root root 64 Apr 3 09:24 3 -> socket:[756505]
lrwx------ 1 root root 64 Apr 3 09:24 4 -> /var/cache/
lrwx------ 1 root root 64 Apr 3 09:24 5 -> /var/cache/
lrwx------ 1 root root 64 Apr 3 09:24 54 -> /dev/pts/15
lrwx------ 1 root root 64 Apr 3 09:24 6 -> /var/cache/
lr-x------ 1 root root 64 Apr 3 09:24 7 -> pipe:[756506]
# strace -p 13919
Process 13919 attached - interrupt to quit
read(3,
I guess it's waiting for input from the program at the other end of that pty. I'm not sure if that's aptd that's meant to do that, or the debconf-communicate or some other piece of update-manager.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: update-manager 1:0.185
ProcVersionSign
Uname: Linux 3.8.0-16-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Wed Apr 3 09:17:58 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
GsettingsChanges:
b'com.
b'com.
b'com.
b'com.
b'com.
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitec
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: update-manager
UpgradeStatus: Upgraded to raring on 2013-03-19 (14 days ago)
Changed in update-manager (Ubuntu): | |
importance: | Undecided → High |
er of course I meant the other end of the socket, not the pty.