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

Bug #340479 reported by Martin Olsson
596
This bug affects 135 people
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Invalid
Medium
Unassigned
Nominated for Lucid by Ben Isaacs

Bug Description

Binary package hint: update-notifier

crash... I was having these annoying package dependency bugs so maybe some uncommon execution path was running??

Hit http://archive.ubuntu.com jaunty-security/multiverse Sources
Hit http://archive.ubuntu.com jaunty-security/universe Sources
Hit http://archive.ubuntu.com jaunty-security/universe Packages
Hit http://archive.ubuntu.com jaunty-security/multiverse Packages
Fetched 13.3MB in 10s (1245kB/s)
Reading package lists... Done
W: GPG error: http://ddebs.ubuntu.com jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ECDCAD72428D7C01
W: You may want to run apt-get update to correct these problems
mnemo@kingfish:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run `apt-get -f install' to correct these.
The following packages have unmet dependencies:
  anjuta: Depends: anjuta-common (= 2:2.24.2-1ubuntu1) but 2:2.25.902-0ubuntu2 is installed
E: Unmet dependencies. Try using -f.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/update-notifier/apt_check.py
InterpreterPath: /usr/bin/python2.6
Package: update-notifier-common 0.76.5
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/update-notifier/apt-check
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 pkgCacheGenerator::MergeList (this=0x7fff9ba4a510, List=@0x7fff9ba49a10,
 debStatusIndex::Merge (this=0x1803860,
 BuildCache (Gen=@0x7fff9ba4a510,
 pkgMakeStatusCache (List=<value optimized out>,
 pkgCacheFile::BuildCaches (this=0x1883b10,
Title: apt_check.py crashed with SIGSEGV in pkgCacheGenerator::MergeList()
Uname: Linux 2.6.28-8-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Revision history for this message
Monkey (monkey-libre) wrote :

Also I have this problem with Linux monkey-desktop 2.6.31-12-generic #40-Ubuntu SMP Wed Oct 7 04:14:43 UTC 2009 i686 GNU/Linux

Changed in update-notifier (Ubuntu):
status: New → Confirmed
tags: added: i386
Revision history for this message
Monkey (monkey-libre) wrote :

I´m using Ubuntu Karmic Koala 9.10 Beta

Revision history for this message
Bluppie (benhyper) wrote :

I was just installing skype when the program synaptic crasht on the installation off skype.
Ubunto Karmic Koala 9.10 beta oktober

Revision history for this message
SubBASS (subbass) wrote :

Since updating to karmic with dist upgrade I have seen this a few times, just received it again now after performing :
sudo update-apt-xapian-index
Due to not seeing updates in Synaptic correctly.

Clean installed netbook has no problems,

Changed in update-notifier (Ubuntu):
assignee: nobody → Benjamin (mastermindbird)
tags: added: bugpattern-needed
Revision history for this message
Tim Bond (timothy-bond) wrote :

Also experienced in Lucid (see Bug 510788) whilst running wajig dist-upgrade.

Changed in update-notifier (Ubuntu):
assignee: Benjamin (mastermindbird) → nobody
Revision history for this message
Brian Murray (brian-murray) wrote :

Bug 509990 which is a duplicate of this contains a stacktrace.

tags: added: bugpattern-written
removed: bugpattern-needed
Revision history for this message
Joe Hurr (joehurr) wrote :

I've just been directed here from a crash in Lucid whilst trying to set up a mobile broadband dongle using Betavine's VMC.

Revision history for this message
Bluppie (benhyper) wrote :

While updating this error came true the updating process in Lucid.

Revision history for this message
Alf Gaida (agaida) wrote :

Nearly every time i update lucid with synaptic this error occured.

Revision history for this message
fraujansen (fraujansen) wrote :

I just clicked on the "Search" button on Synaptic and then this error appeared.

Revision history for this message
Rob David (rob-david) wrote :

I got this problem in lucid, just after removing some packages from my system in synaptic. This was version 0.99.1 of update-notifier-common.

Revision history for this message
Antti Kaihola (akaihola) wrote :

Just did a clean install of Lucid 2010-04-02 on a Dell Mini 9. Installed a few packages with the GUI tool in the Applications menu, then a few more using apt-get. Then added the file /etc/apt/apt.conf/99proxy to use apt-cacher available on one of the boxes on the local network:

    Acquire::http::Proxy "http://192.168.0.3:3142/apt-cacher/";

After that, did a "sudo apt-get update", and moments after it had finished, got the "apt_check.py crashed" error window.

Revision history for this message
xteejx (xteejx) wrote :

Upgrading status to Triaged, Medium. There should be more than enough debugging information from the log files contained in the duplicates here for a developer to take a good look at this. Thank you all for reporting this to us, and please continue to report any other bugs/problems you may find.

tags: added: jaunty karmic lucid
Changed in update-notifier (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
John Winterton (jwinterton) wrote :

[UBUNTU 10.4 Beta 2+updates] mail-notifier cannot access keyring to store password. Keyring-daemon seems to be absent.

Revision history for this message
Christian Kirbach (christian-kirbach-e) wrote :

I came the upgrade path Ubuntu 9.10 -> 10.04beta

I faced this issue while I was manually uninstalling some packages using synaptic.
I have the feeling that the automatic upgrade checker kicked in after I uninstalled a first bunch of packages, just before I uninstalled additional packages.
Did apt_check.py choke on an APT lock file?

Revision history for this message
efa (efa) wrote :

happened on 10.04 LTS (final) in a normal automatic packages update

Revision history for this message
Flávio Etrusco (etrusco) wrote :

@efa, did you install packages from repositories (e.g. proposed) that you later disabled, leaving the packages "obsolete"? I was in this situation and started seeing this problem after a recent update. Then I downgraded the packages back to what the enabled repositories provided and the problem went away.

Revision history for this message
efa (efa) wrote :

as I remember I only installed "final" packages from packages manager.
Out of them, Seamonkey 2 and OpenOffice 3.2 was installed with provided builtin installer on the old Ubuntu 9.10.
I also cleaned the installed packages with:
# apt-get autoremove
before and after the distribution upgrade.

Revision history for this message
Mörgæs (moergaes) wrote :

Closing due to age. No activity since 10.04.

If a similar bug appears in Ubuntu 14.04 please open a new report.

Changed in update-notifier (Ubuntu):
status: Triaged → 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.