apport-gtk crashed with SIGSEGV in gtk_scrolled_window_unset_placement@plt()

Bug #264360 reported by Perfecto
88
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pygtk (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: apport

It crashed while I was reporting a crashed

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
Package: apport-gtk 0.113
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=/home/perfe/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: apport
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 gtk_scrolled_window_unset_placement@plt ()
 ?? ()
Title: apport-gtk crashed with SIGSEGV in gtk_scrolled_window_unset_placement@plt()
Uname: Linux 2.6.27-2-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare scanner tape users video

Revision history for this message
Perfecto (perfecto) 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 : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

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

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in pygtk:
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 pygtk:
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.