synaptic crashed with SIGSEGV

Bug #269398 reported by LavianoTS386
6
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: synaptic

using update manager when I got this bug report

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/synaptic
NonfreeKernelModules: ath_hal nvidia
Package: synaptic 0.62.1ubuntu8
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 52428803 --update-at-startup
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: synaptic
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: synaptic crashed with SIGSEGV
Uname: Linux 2.6.27-2-generic x86_64
UserGroups:

Tags: apport-crash
Revision history for this message
LavianoTS386 (lavianots386) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:RPackageViewSections::addPackage (this=0x11b7180, package=0x168fea0) at rpackageview.cc:95
RPackageView::refresh (this=0x11b7180) at rpackageview.cc:89
RPackageLister::openCache (this=0x11d4e90) at rpackagelister.cc:411
RGMainWindow::cbUpdateClicked (self=<value optimized out>, data=0x10f1200)
main (argc=6, argv=0x7fff1e080a38) at gsynaptic.cc:545

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in synaptic:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? May you please try the same with Jaunty? Thanks in advance.

Changed in synaptic (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in synaptic (Ubuntu):
status: Incomplete → 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.