Ubuntu
aptitude package

aptitude does not start - symbol lookup error

Bug #1503052 reported by Paul White on 2015-10-05

22

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	aptitude (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

Each time I try to start aptitude I see the following:

paul@N7110:~> sudo aptitude
[sudo] password for paul:
aptitude: symbol lookup error: aptitude: undefined symbol: _ZNK13Configuration10FindVectorB5cxx11EPKc

Seen on two similarly configured PC since last update. This error makes aptitude unusable.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: aptitude 0.7-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 5 22:42:24 2015
InstallationDate: Installed on 2015-07-17 (80 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150717)
SourcePackage: aptitude
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Paul White (paulw2u) wrote on 2015-10-05:

#1

Dependencies.txt Edit (4.9 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (60.1 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (111 bytes, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-10-06:

#2

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in aptitude (Ubuntu):
status:	New → Confirmed

Revision history for this message

matsonfamily (david-matsonfamily) wrote on 2015-10-06:

#3

same thing on 2 15.10 (XFCE and a cli-only) environments. Libept is libept1.4.16 v 1.0.13ubuntu1. is libept just missing the symbol?

Revision history for this message

Michael Vogt (mvo) wrote on 2015-10-06:

#4

Sorry for this temporary hickup, please upgrade apt/libapt-pkg4.16 and aptitude to the current version in wily and the problem should be fixed.

Changed in aptitude (Ubuntu):
status:	Confirmed → Fix Released

Revision history for this message

Robin Kanters (r-kanters) wrote on 2015-10-06:

#5

Can confirm that upgrading those packages fixed the problem! Thanks for the quick solution!

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.