update-manager crashed with SIGSEGV

Bug #164483 reported by Aurel Branzeanu
64
This bug affects 3 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: update-manager

found this crash in /var/crash

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Nov 22 13:03:03 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/update-manager
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: fglrx
Package: update-manager 1:0.81
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.5 /usr/bin/update-manager
ProcCwd: /home/thunder
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: update-manager
Stacktrace: #0 0x080f33a0 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: update-manager crashed with SIGSEGV
Uname: Linux thunder-mobile 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev scanner tape users video

Tags: apport-crash
Revision history for this message
Aurel Branzeanu (thunder-riscom) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in update-manager:
importance: Undecided → Medium
Revision history for this message
Jean-Baptiste Lallement (jibel) 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? Can you try with latest Ubuntu release? Thanks in advance.

Changed in update-manager:
status: New → Incomplete
Revision history for this message
drsaamah (saam-r-sany) wrote : Re: [Bug 164483] Re: update-manager crashed with SIGSEGV

I would love to help out, but I need a little direction. These bug reports
have always been somewhat cryptic to me. What is "SIGSEGV" and how would I
make sure its running while performing operations with update-manager?
Please let me know, as I would love to participate in testing this. By the
way, I am now running x86-64 Intrepid Ibex.
~Saam

On Sat, Dec 6, 2008 at 6:32 PM, Jean-Baptiste Lallement <
<email address hidden>> 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? Can you try with latest Ubuntu release? Thanks in advance.
>
> ** Changed in: update-manager (Ubuntu)
> Status: New => Incomplete
>
> --
> update-manager crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/164483
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Hi drsaamah, for a definition of SIGSEGV you can read http://en.wikipedia.org/wiki/SIGSEGV

Are you experiencing the same issue as the original reporter ? If so, please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in update-manager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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