apt_check.py crashed with SIGSEGV in pkgCache::FindPkg()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-notifier (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: update-notifier
System Release: Ubuntu lucid 10.04 Alpha 2, kernel 2.6.32-11-generic
Package version:
update-notifier:
Installed: 0.92
Marked: 0.92
Versiontable:
*** 0.92 0
500 http://
100 /var/lib/
The system is running virtualized in a Sun VirtualBox 3.1.2 r56127 virtual machine on a Ubuntu 9.04 with kernel 2.6.28-17-server.
I ran 'sudo apt-get update && sudo apt-get dist-upgrade' in terminal. The updating and upgrading processes terminated successfully without any errors, the crash icon suddenly appeared. I have main, restricted, universe, multiverse, partner, source repositories enabled.
ProblemType: Crash
Architecture: i386
Date: Fri Jan 22 12:37:25 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/
InstallationMedia: Error: [Errno 13] Engedély megtagadva: '/var/log/
InterpreterPath: /usr/bin/python2.6
Package: update-
PackageArchitec
ProcCmdline: /usr/bin/python /usr/lib/
ProcEnviron:
LANG=hu_HU.utf8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x5709e0 <_ZN8pkgCache7F
PC (0x005709e0) ok
source "(%esi)" (0xcd472cf0) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
pkgCache:
pkgCacheGenera
pkgCacheGenera
debStatusIndex
?? () from /usr/lib/
Title: apt_check.py crashed with SIGSEGV in pkgCache::FindPkg()
Uname: Linux 2.6.32-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
visibility: | private → public |
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #467875, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.