serpentine crashed with SIGSEGV in g_type_check_instance()

Bug #183684 reported by darthanubis
2
Affects Status Importance Assigned to Milestone
serpentine (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: serpentine

Tried to close the app via file>quit, after a burn, and it froze.

ProblemType: Crash
Architecture: amd64
Date: Wed Jan 16 23:12:16 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/serpentine
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
Package: serpentine 0.9-1ubuntu2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/serpentine -o
ProcCwd: /home/anubis
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: serpentine
StacktraceTop:
 g_type_check_instance ()
 g_signal_handlers_disconnect_matched ()
 gtk_accel_label_set_accel_closure ()
 gtk_accel_label_set_accel_widget ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: serpentine crashed with SIGSEGV in g_type_check_instance()
Uname: Linux amd 2.6.24-3-server #1 SMP Thu Jan 3 23:20:57 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin mythtv netdev plugdev powerdev sambashare scanner tape users video

Tags: apport-crash
Revision history for this message
darthanubis (darthanubis) wrote :
Revision history for this message
Parthan SR (parth-technofreak) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in serpentine:
status: New → Confirmed
status: Confirmed → New
Revision history for this message
Parthan SR (parth-technofreak) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #91168 (Ubuntu 7.04), #132737 (Ubuntu 7.10), so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.

The earlier bug #132737 had been reported to developers of the software. To track the bug and make comments refer: http://bugzilla.gnome.org/show_bug.cgi?id=484786

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.