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 468021 - Print dialog box segfaults (64 bit)
Print dialog box segfaults (64 bit)
Status: RESOLVED DUPLICATE of bug 467643
Product: GIMP
Classification: Other
Component: Plugins
2.4.x
Other Linux
: High critical
: 2.4
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2007-08-18 19:09 UTC by skottish
Modified: 2008-10-30 19:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description skottish 2007-08-18 19:09:11 UTC
The print dialog box segfaults:

/opt/gimp-2.4/lib/gimp/2.0/plug-ins/print: fatal error: Segmentation fault

This is the only information given. Gimp itself does not crash.

64 bit Linux
Kernel: 2.6.22
GCC: 4.2.1
Binutils: 2.17
GlibC: 2.6.1

Gimp was compiled with only the --prefix flag.
Comment 1 Martin Nordholts 2007-08-18 19:18:14 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

I suspect this is a duplicate of bug #467643.
Comment 2 skottish 2007-08-18 23:14:12 UTC
(gimp-2.4:27794): Gtk-WARNING **: Debug: missing action debug-menu
/opt/gimp-2.4/lib/gimp/2.0/plug-ins/print: fatal error: Segmentation f
ault
/opt/gimp-2.4/lib/gimp/2.0/plug-ins/script-fu terminated: Interrupt

Program received signal SIGINT, Interrupt.
[Switching to Thread 47031770698928 (LWP 27794)]
0x00002ac66ed8cc86 in poll () from /lib/libc.so.6
(gdb) thread apply all bt


Comment 3 Martin Nordholts 2007-08-19 05:59:22 UTC
Seems like a different issue, we should look into this before 2.4.
Comment 4 skottish 2007-08-19 16:54:04 UTC
This was mentioned on the developers mailing list:

https://lists.xcf.berkeley.edu/lists/gimp-developer/2007-August/018506.html

There is no print dialog box on my build, so it's definitely not the problem posted in the link above.

Other people that are using Arch Linux are not seeing this. If you're not familiar with Arch, it's a rolling release distro. So, with the exception of custom built packages, most of us have more or less the same software. One of the big differences of course is 64 bit vs. 32 bit.

I'm going to cross reference this discussion with a forum post at Arch to see if I can draw in more information. I'll also check into this thread frequently to provide any information or support I can. And, I'll gladly patch and rebuild Gimp any time you need me to. This is critical. It needs to be done before 2.4.

http://bbs.archlinux.org/viewtopic.php?pid=274391#p274391


 
Comment 5 Emmanuel Touzery 2007-08-20 06:11:24 UTC
it also segfaults for me on a 32-bit computer using windows and the automated installer for Jernej Simončič.

I was using the gimp 2.3.19 from that same automated installer so far and it wasn't crashing when asking to print. But now that I upgraded on 2.4.0rc1 it is crashing instantly when I click "File->print..."

Note that I was using gimp 2.2 & 2.4 in parallel on that computer, installing 2.4rc1 uninstalled gimp 2.2 and set itself up in the 2.2 location. maybe related...
Comment 6 Emmanuel Touzery 2007-08-20 06:31:39 UTC
OK I actually created a new bug for that windows crash, since it might be something completely different, it's bug #468407. So you can ignore this here. sorry for the noise.
Comment 7 Simon Munton 2007-08-23 06:59:43 UTC
I'm also seeing this problem on a 32 bit machine running Slackware 12 plus gtk+ 2.10.14 and glib 2.14.0.


Program received signal SIGSEGV, Segmentation fault.
0xb7bb416c in gtk_page_setup_get_paper_width () from /usr/lib/libgtk-x11-2.0.so.0

Backtrace from print plugin:

  • #0 gimp_plugin_sigfatal_handler
    at gimp.c line 1471
  • #1 <signal handler called>
  • #2 gtk_page_setup_get_paper_width
    from /usr/lib/libgtk-x11-2.0.so.0
  • #3 gtk_page_setup_get_page_width
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 print_size_info_get_page_dimensions
    at print-page-layout.c line 557
  • #5 gimp_size_info_get_max_offsets
    at print-page-layout.c line 570
  • #6 print_size_info_update_offsets
    at print-page-layout.c line 612
  • #7 print_offset_frame
    at print-page-layout.c line 490
  • #8 print_page_layout_gui
    at print-page-layout.c line 188
  • #9 _gtk_marshal_OBJECT__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #14 get_print_dialog
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 _gtk_print_operation_platform_backend_run_dialog
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_print_operation_run
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 run
    at print.c line 215
  • #18 gimp_main
    at gimp.c line 1810
  • #19 main
    at print.c line 77


Tracing through print_size_info_get_page_dimensions() it looks as though the call to gtk_print_operation_get_default_page_setup() returns NULL which then triggers the segfault in gtk_page_setup_get_paper_width()


Comment 8 Michael Natterer 2007-08-23 18:38:07 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 467643 ***