synaptic crashed (on startup) with SIGABRT in raise()

Bug #874078 reported by Alan Jenkins
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ran synaptic normally (from Unity); it crashed.

This is probably the first time I've tried to do so. Previously, I was using Kubuntu (11.04). I've just upgraded today and am giving Unity a try-out.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: synaptic 0.75.2ubuntu8
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Fri Oct 14 11:59:11 2011
ExecutablePath: /usr/sbin/synaptic
ProcCmdline: /usr/sbin/synaptic
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
Signal: 6
SourcePackage: synaptic
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
Title: synaptic crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)
UserGroups:

Revision history for this message
Alan Jenkins (aj504) wrote :
Revision history for this message
Alan Jenkins (aj504) wrote :

But it's not unique to Unity.

$ sudo synaptic
terminate called after throwing an instance of 'std::out_of_range'
  what(): vector::_M_range_check

Alan Jenkins (aj504)
visibility: private → public
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.