synaptic crashed with SIGSEGV in pkgRecords::Lookup()

Bug #1098481 reported by pablomme on 2013-01-11
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
Undecided
Unassigned

Bug Description

I got the above segfault in Synaptic while trying to select all packages in "Not Installed (Residual Config)" with Ctrl+A. This is in up-to-date raring. The application didn't close, and I received multiple prompts to report a bug, the first couple of which crashed too, so this may not be the first error triggered by that action.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: synaptic 0.80~exp1
ProcVersionSignature: Ubuntu 3.8.0-0.2-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic x86_64
ApportVersion: 2.8-0ubuntu1
Architecture: amd64
Date: Fri Jan 11 09:34:49 2013
ExecutablePath: /usr/sbin/synaptic
InstallationDate: Installed on 2012-12-13 (28 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121213)
MarkForUpload: True
ProcCmdline: /usr/sbin/synaptic
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f0cc354c534 <_ZN10pkgRecords6LookupERKN8pkgCache15VerFileIteratorE+20>: mov (%rax),%eax
 PC (0x7f0cc354c534) ok
 source "(%rax)" (0x7f12fa138000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: synaptic
StacktraceTop:
 pkgRecords::Lookup(pkgCache::VerFileIterator const&) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: synaptic crashed with SIGSEGV in pkgRecords::Lookup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

pablomme (pablomme) wrote :
pablomme (pablomme) wrote :

Ok, namely the problem was with selecting libtelepathy-logger2 among the packages. libtelepathy-logger2 has no "Installed version", "Available version", etc, in the listing. This package was just replaced, if I remember correctly, by libtelepathy-logger3 in an update (with lt-l2 remaining installed), but beyond that I don't know what about this package should cause synaptic to misbehave.

pablomme (pablomme) wrote :

apt-get remove --purge libtelepathy-logger2 removed the package correctly. Still, synaptic shouldn't have crashed when trying to perform the same operation.

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1097532, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers