aptDBUSBackend.py crashed with SIGSEGV in strlen()

Bug #363005 reported by adoeller
8
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: packagekit

crashed during update

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/packagekit/aptDBUSBackend.py
InterpreterPath: /usr/bin/python2.6
Package: packagekit-backend-apt 0.3.14-0ubuntu4
ProcAttrCurrent: unconfined
ProcCmdline: python /usr/lib/packagekit/aptDBUSBackend.py
ProcCwd: /
ProcEnviron:

Signal: 11
SourcePackage: packagekit
StacktraceTop:
 strlen () from /lib/tls/i686/cmov/libc.so.6
 std::string::compare () from /usr/lib/libstdc++.so.6
 debPackagesIndex::FindInCache ()
 ?? () from /usr/lib/libapt-pkg-libc6.9-6.so.4.7
 pkgMakeStatusCache ()
Title: aptDBUSBackend.py crashed with SIGSEGV in strlen()
Uname: Linux 2.6.28-11-generic i686
UserGroups:

Revision history for this message
adoeller (adoeller) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:strlen () at ../sysdeps/i386/i486/strlen.S:40
std::string::compare (this=0xbfe536b8,
debPackagesIndex::FindInCache (this=0x8c034f8,
CheckValidity (CacheFile=<value optimized out>, Start=
pkgMakeStatusCache (List=@0xbfe53940, Progress=@0xbfe539bc,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in packagekit (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Steve Beattie (sbeattie)
visibility: private → public
affects: packagekit (Ubuntu) → python-apt (Ubuntu)
Revision history for this message
Julian Andres Klode (juliank) wrote :

APT bug? We're only calling Cache->Open(progress,false) in python-apt, and this should not segfault.

affects: python-apt (Ubuntu) → apt (Ubuntu)
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 363005, and any other logs that are relevant for this particular issue.

Changed in apt (Ubuntu):
status: New → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in apt (Ubuntu):
status: Incomplete → 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.