[apport] zapping crashed with SIGSEGV in gtk_widget_set_sensitive()

Bug #111205 reported by cchester
6
Affects Status Importance Assigned to Milestone
zapping (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: zapping

Was trying to set up channels when first ever start of zapping.

ProblemType: Crash
Architecture: i386
Date: Mon Apr 30 06:07:22 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/zapping
Package: zapping 0.9.6-3ubuntu5
PackageArchitecture: i386
ProcCmdline: zapping
ProcCwd: /home/chris
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: zapping
Stacktrace:
 #0 0xb7bb05df in gtk_widget_set_sensitive ()
    from /usr/lib/libgtk-x11-2.0.so.0
 #1 0x08065a2d in ?? ()
 #2 0x00000145 in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 gtk_widget_set_sensitive ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux chris-desktop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
cchester (christopherwchester-earthlink) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__gtk_widget_set_sensitive (widget=0x145, sensitive=0) at gtkwidget.c:4614
no_channel_selected (ce=0x83ba0f8) at channel_editor.c:469
on_channel_selection_changed (selection=0x83d43a0, ce=0x83ba0f8) at channel_editor.c:1172
IA__g_cclosure_marshal_VOID__VOID (closure=0x83d72f8, return_value=0x0, n_param_values=1, param_values=0xbf96c9dc, invocation_hint=0xbf96c8ec,
IA__g_closure_invoke (closure=0x83d72f8, return_value=0x0, n_param_values=1, param_values=0xbf96c9dc, invocation_hint=0xbf96c8ec) at gclosure.c:490

Revision history for this message
Apport retracing service (apport) 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.