jockey-backend crashed with signal 5 in pselect()

Bug #341777 reported by Dave Morley
8
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Crash when applying strace for another crash

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/jockey/jockey-backend
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
Package: jockey-common 0.5-0ubuntu3
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=256c247d-a347-4b10-a734-c05a72e8c1b4 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/jockey/jockey-backend --debug -l /var/log/jockey.log
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.28-9.31-generic
Signal: 5
SourcePackage: jockey
StacktraceTop:
 pselect () from /lib/libc.so.6
 pkgDPkgPM::Go ()
 pkgPackageManager::DoInstallPostFork ()
 ?? ()
 PyEval_EvalFrameEx ()
Title: jockey-backend crashed with signal 5 in pselect()
UserGroups:

XorgConf:

Revision history for this message
Dave Morley (davmor2) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:__pselect (nfds=27, readfds=0x7f74b32c9a60,
pkgDPkgPM::Go (this=0x3ebf690, OutStatusFd=22)
pkgPackageManager::DoInstallPostFork (
PkgManagerDoInstall (Self=<value optimized out>,
PyEval_EvalFrameEx (f=0x3f59ba0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in jockey:
importance: Undecided → Medium
Revision history for this message
Martin Pitt (pitti) wrote :

This looks like a crash in python-apt.

Revision history for this message
Julian Andres Klode (juliank) wrote :

Looks like an APT bug, where APT aborts with an error on SIGTRAP signals

affects: python-apt (Ubuntu) → apt (Ubuntu)
Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

Changed in apt (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.