[apport] zapping crashed with SIGSEGV in gtk_widget_set_sensitive()

Bug #103539 reported by Rui Mesquita
2
Affects Status Importance Assigned to Milestone
zapping (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: zapping

Seems selecting any option from the app menus causes this crash. I tried edit->channels, and edit->preferences.

ProblemType: Crash
Architecture: i386
Date: Fri Apr 6 00:52:49 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/zapping
Package: zapping 0.9.6-3ubuntu5
PackageArchitecture: i386
ProcCmdline: zapping
ProcCwd: /media/hdb5/rpedro
ProcEnviron:
 LANGUAGE=pt_PT.UTF-8@euro
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pt_PT.UTF-8@euro
 SHELL=/bin/bash
Signal: 11
SourcePackage: zapping
Stacktrace:
 #0 0xb7bd15df in gtk_widget_set_sensitive ()
    from /usr/lib/libgtk-x11-2.0.so.0
 #1 0x08065a53 in ?? ()
 #2 0x00000003 in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 gtk_widget_set_sensitive ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux ubuntubox 2.6.20-13-lowlatency #2 SMP PREEMPT Sun Mar 25 00:23:53 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Rui Mesquita (rpedro78) wrote :
Revision history for this message
Martin Pitt (pitti) wrote : Symbolic stack trace

StacktraceTop:IA__gtk_widget_set_sensitive (widget=0x3, sensitive=0) at gtkwidget.c:4614
no_channel_selected (ce=0x8497358) at channel_editor.c:471
on_channel_selection_changed (selection=0x84bc820, ce=0x8497358) at channel_editor.c:1172
IA__g_cclosure_marshal_VOID__VOID (closure=0x84bc398, return_value=0x0, n_param_values=1, param_values=0xbfd9c08c, invocation_hint=0xbfd9bf9c,
IA__g_closure_invoke (closure=0x84bc398, return_value=0x0, n_param_values=1, param_values=0xbfd9c08c, invocation_hint=0xbfd9bf9c) at gclosure.c:490

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic threaded stack trace
Changed in zapping:
importance: Undecided → Medium
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.