Ubuntu
update-notifier package

apt_check.py crashed with SIGSEGV in pkgCacheGenerator::MergeList()

Bug #447218 reported by juacarra on 2009-10-09

This bug report is a duplicate of: Bug #340479: apt_check.py crashed with SIGSEGV in pkgCacheGenerator::MergeList(). Edit Remove

206

This bug affects 47 people

Affects		Status	Importance	Assigned to	Milestone
	update-notifier (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: update-notifier

apt_check.py crashed with SIGSEGV in pkgCacheGenerator::MergeList()

ProblemType: Crash
Architecture: i386
Date: Fri Oct 9 09:22:53 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/update-notifier/apt_check.py
InterpreterPath: /usr/bin/python2.6
Package: update-notifier-common 0.88
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/update-notifier/apt-check
ProcEnviron:
LANG=es_CL.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
SegvAnalysis:
Segfault happened at: 0x173c7f <_ZN17pkgCacheGenerator9MergeListERNS_10ListParserEPN8pkgCache11VerIteratorE+1407>: mov (%edx),%edx
PC (0x00173c7f) ok
source "(%edx)" (0xb88d51b0) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
pkgCacheGenerator::MergeList(pkgCacheGenerator::ListParser&, pkgCache::VerIterator*) () from /usr/lib/libapt-pkg-libc6.10-6.so.4.8
debStatusIndex::Merge(pkgCacheGenerator&, OpProgress&) const
?? () from /usr/lib/libapt-pkg-libc6.10-6.so.4.8
pkgMakeStatusCache(pkgSourceList&, OpProgress&, MMap**, bool) () from /usr/lib/libapt-pkg-libc6.10-6.so.4.8
pkgCacheFile::BuildCaches(OpProgress&, bool) ()
Title: apt_check.py crashed with SIGSEGV in pkgCacheGenerator::MergeList()
Uname: Linux 2.6.31-12-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(gnome-settings-daemon:13987): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-settings-daemon:13987): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(nautilus:14033): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
(polkit-gnome-authentication-agent-1:14083): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Tags:

Revision history for this message

juacarra (juacarrag) wrote on 2009-10-09:

Dependencies.txt Edit (950 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (3.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (755 bytes, text/plain; charset="utf-8")
Registers.txt Edit (576 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.6 KiB, text/plain; charset="utf-8")

Revision history for this message

sQuonk (squonk-anarchic-teapot) wrote on 2009-10-20:

Seems to want to update when I'm already running update manager!

Benjamin (mastermindbird) on 2009-11-03

Changed in update-notifier (Ubuntu):
status:	New → Confirmed
assignee:	nobody → Benjamin (mastermindbird)

Revision history for this message

tommaso (mb3-tim) wrote on 2009-12-06:

9.10 version, it seems this one,
at first update rescan,
the second closed normally,
this before the requested rebooting.

Best Regards
Tommaso

Revision history for this message

Monkey (monkey-libre) wrote on 2010-04-06:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #340479, so it 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. Feel free to continue to report any other bugs you may find.