After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 316018 - Crash when printing gif file from gthumb
Crash when printing gif file from gthumb
Status: RESOLVED FIXED
Product: gnome-print
Classification: Deprecated
Component: general
CVS
Other All
: High critical
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2005-09-11 19:20 UTC by Julien Gilli
Modified: 2005-09-21 17:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Attachments
It doesn't crash anymore (307 bytes, patch)
2005-09-11 19:22 UTC, Julien Gilli
rejected Details | Review
Another try to prevent libgnomeprint from crashing (367 bytes, patch)
2005-09-11 21:49 UTC, Julien Gilli
rejected Details | Review
Init the bpath. (2.11 KB, patch)
2005-09-19 19:00 UTC, Jody Goldberg
none Details | Review

Description Julien Gilli 2005-09-11 19:20:46 UTC
Steps to reproduce:
1. Start gthumb
2. Open file mentionned at bug 316011
3. Print


Stack trace:
jgilli@susu:~/projets/bug_days/libgnomeprint$ gdb gthumb
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...Using host libthread_db library
"/lib/libthread_db.so.1".

(gdb) r
Starting program: /home/jgilli/custom/bin/gthumb
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 16769)]
[New Thread 32769 (LWP 16770)]
[New Thread 16386 (LWP 16771)]
[New Thread 32771 (LWP 16772)]
[New Thread 49156 (LWP 16773)]
[New Thread 65541 (LWP 16774)]
[New Thread 81926 (LWP 16775)]
[New Thread 98311 (LWP 16776)]
[New Thread 114696 (LWP 16777)]
[New Thread 131081 (LWP 16778)]
[New Thread 147466 (LWP 16781)]
[New Thread 163851 (LWP 16782)]

(gthumb:16769): GnomePrintCupsPlugin-WARNING **: iconv does not support ppd
character encoding: ISOLatin1, trying CSISOLatin1
[Thread 147466 (LWP 16781) exited]

(gthumb:16769): GLib-GObject-WARNING **: IA__g_object_new_valist: object class
`GnomePrintDialog' has no property named `config'

(gthumb:16769): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(gthumb:16769): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion
`G_TYPE_CHECK_INSTANCE (instance)' failed
[New Thread 180236 (LWP 16783)]
[Thread 180236 (LWP 16783) exited]

Program received signal SIGSEGV, Segmentation fault.

Thread 16384 (LWP 16769)

  • #0 image_impl
    at gnome-print-filter-frgba.c line 213
  • #1 gnome_print_filter_image
    at gnome-print-filter.c line 1356
  • #2 gnome_print_image_transform
    at gnome-print.c line 644
  • #3 gpm_render
    at gnome-print-meta.c line 628
  • #4 gnome_print_meta_render_data_page
    at gnome-print-meta.c line 906
  • #5 gnome_print_meta_render_page
    at gnome-print-meta.c line 840
  • #6 gnome_print_job_print
    at gnome-print-job.c line 649
  • #7 print_catalog_cb
    at print-callbacks.c line 1684
  • #8 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #9 IA__g_closure_invoke
    at gclosure.c line 492
  • #10 signal_emit_unlocked_R
    at gsignal.c line 2485
  • #11 IA__g_signal_emit_valist
    at gsignal.c line 2244
  • #12 IA__g_signal_emit
    at gsignal.c line 2288
  • #13 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 _gtk_button_paint
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #16 g_type_class_meta_marshal
    at gclosure.c line 569
  • #17 IA__g_closure_invoke
    at gclosure.c line 492
  • #18 signal_emit_unlocked_R
    at gsignal.c line 2415
  • #19 IA__g_signal_emit_valist
    at gsignal.c line 2244
  • #20 IA__g_signal_emit
    at gsignal.c line 2288
  • #21 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 _gtk_button_paint
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 g_type_class_meta_marshal
    at gclosure.c line 569
  • #25 IA__g_closure_invoke
    at gclosure.c line 492
  • #26 signal_emit_unlocked_R
    at gsignal.c line 2523
  • #27 IA__g_signal_emit_valist
    at gsignal.c line 2254
  • #28 IA__g_signal_emit
    at gsignal.c line 2288
  • #29 gtk_widget_send_expose
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #33 g_main_dispatch
    at gmain.c line 1934
  • #34 IA__g_main_context_dispatch
    at gmain.c line 2484
  • #35 g_main_context_iterate
    at gmain.c line 2565
  • #36 IA__g_main_loop_run
    at gmain.c line 2769
  • #37 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 main
    at main.c line 696


Other information:
I was trying to reproduce bug 316011.
Comment 1 Julien Gilli 2005-09-11 19:22:14 UTC
Created attachment 52099 [details] [review]
It doesn't crash anymore

Although this patch prevent libgnomeprint from crashing, it doesn't print
anything.
Comment 2 Julien Gilli 2005-09-11 21:49:47 UTC
Created attachment 52104 [details] [review]
Another try to prevent libgnomeprint from crashing

This one makes more sense.
Comment 3 Julien Gilli 2005-09-11 21:50:10 UTC
Both print preview and print crash without the above patch on my workstation.

However, it seems that (from the cvs log output) this file hasn't changed since
08/15/2005, and many people are able to print from gthumb. I don't understand
how it is possible. 

Moreover, as pointed out by oGALAXYo on #bugs, the above patch makes more sense.
Comment 4 Jody Goldberg 2005-09-12 15:18:41 UTC
!@$! that file has not changed in recent years!  The code used to live in a
different directory.

The patch does not look correct.  I suspect that this was a cut-n-paste error.
It looks like the author was trying to setup the newly allocated bpath.  Give
CVS a try.
Comment 5 Julien Gilli 2005-09-13 16:36:49 UTC
What do you mean by "give cvs a try" ? I used an up to date cvs working copy, 
and i can't understand how we can dereference a NULL pointer (vpath in this 
case). Can you clarify your thoughts please ?

All the best,
Comment 6 Jody Goldberg 2005-09-13 18:39:26 UTC
my comment was premature.  The patch I was going to propose was a bad idea.
I'm trying to track what the original code here was trying to do.  It makes no
sense to populate the vpath that we are about to populate from a bpath that is
incompletely specified.
Comment 7 Jody Goldberg 2005-09-19 19:00:00 UTC
Created attachment 52402 [details] [review]
Init the bpath.

Try this.
Comment 8 Julien Gilli 2005-09-21 17:16:18 UTC
I tried the above patch. It didn't crash, but it didn't print anything though. I
think that it may be a problem with my GNOME setup. I'll do more tests as soon
as possible.
Comment 9 Jody Goldberg 2005-09-21 17:32:07 UTC
I've committed a more comprehensive patch of that routine.  There are other
issues  in libgnomeprint that are breaking things though.