GNOME Bugzilla – Bug 78734
segmentation fault in glade with drv_z42/z42tool (glade Crash at 163.117.145.39)
Last modified: 2009-08-15 18:40:50 UTC
Package: glade Version: 0.6.4 Severity: >Synopsis: segmentation fault in glade with drv_z42/z42tool >Class: sw-bug System: laptop Kapok 2700c GNU/Linux Debian Woody libc6 2.2.5-4 (KDE2 or Gnome) >Description: z42tool is an application to align the cartridges of the printer Lexmark Z42, that comes with the driver found at http://www.xs4all.nl/~pastolk/. The tool source code has to be generated with glade, but when doing 'construct', it gives a segmentation fault. >How-To-Repeat: cp drv_z42-0.3.4.tar.gz /tmp/ cd /tmp/ tar xvzf drv_z42-0.3.4.tar.gz cd drv_z42/z42tool/ glade z42tool.glade & (GUI) -> I press button "Construir" ("Build") I get the error (I translate): "glade" application (process 3243) has failed due to a fatal error (segmentation fault) ------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-04-15 04:17 ------- The original reporter (rcasero@tsc.uc3m.es) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, damon@ximian.com.
I can't reproduce. Can you attach a stack trace? (The files should really be included in the tarball, so you don't need to generate them with Glade.)
I'm sorry, I do not know how to generate a stack trace, but if you tell me how, I'll do it.
The easiest way is to run Glade in gdb, with 'gdb glade'. Then generate the code so Glade crashes. Then type 'bt' into the gdb window and it should print out a stack trace.
Here's the stack trace you asked for. I must say, I've been having problems with gnome in woody. Maybe that's the problem. E.g., I had problems whith bonobo and some other packets when doing apt-get upgrade. Program received signal SIGSEGV, Segmentation fault. 0x0806d909 in gb_widget_write_standard_source () (gdb) bt
+ Trace 21031
This is a unique stack trace. Can it be reproduced with a recent version?
According to the stack trace, this bug occurred in a Gnome 1.x application. Please upgrade to a newer and improved version of gnome, e.g. 2.8.