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 647354 - crash in set_property at ev-properties-view.c line 187
crash in set_property at ev-properties-view.c line 187
Status: RESOLVED OBSOLETE
Product: evince
Classification: Core
Component: general
2.32.x
Other Linux
: Normal critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-04-10 12:42 UTC by Manuel Hiebel
Modified: 2012-07-06 18:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gdb with evince (12.35 KB, text/plain)
2011-04-10 12:42 UTC, Manuel Hiebel
Details
gdb of the pdf http://hiebel.eu/pub/I2.pdf (12.27 KB, text/plain)
2011-04-11 16:02 UTC, Manuel Hiebel
Details

Description Manuel Hiebel 2011-04-10 12:42:52 UTC
Created attachment 185633 [details]
gdb with evince

Description of problem:
If you open properties of a pdf, evince crash.

Version-Release number of selected component (if applicable):
evince-2.32.0-3 (Mageia cauldron)


Steps to Reproduce:
1.open a pdf with evince 
2.file
3.properties

Thanks.
Comment 1 Fabio Durán Verdugo 2011-04-11 12:48:40 UTC
Paste here the attach backtrace.

Program received signal SIGSEGV, Segmentation fault.
0x000000000044a39f in set_property (ties=0x884110, table=0x98e840, property=LINEARIZED_PROPERTY, text=0x1 <Address 0x1 out of bounds>, row=0x7fffffffcdec)
    at ev-properties-view.c:187
187		if (text == NULL || text[0] == '\000') {
(gdb) bt full
  • #0 set_property
    at ev-properties-view.c line 187
  • #1 ev_properties_view_set_info
    at ev-properties-view.c line 360
  • #2 ev_properties_dialog_set_document
    at ev-properties-dialog.c line 101
  • #3 ev_window_cmd_file_properties
    at ev-window.c line 3373
  • #4 g_closure_invoke
    at gclosure.c line 767
  • #5 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #6 g_signal_emit_valist
    at gsignal.c line 2983
  • #7 g_signal_emit
    at gsignal.c line 3040
  • #8 _gtk_action_emit_activate
    at gtkaction.c line 794
  • #9 g_closure_invoke
    at gclosure.c line 767
  • #10 signal_emit_unlocked_R
    at gsignal.c line 3182
  • #11 g_signal_emit_valist
    at gsignal.c line 2983
  • #12 g_signal_emit
    at gsignal.c line 3040
  • #13 IA__gtk_widget_activate
    at gtkwidget.c line 5026
  • #14 IA__gtk_menu_shell_activate_item
    at gtkmenushell.c line 1283
  • #15 gtk_menu_shell_button_release
    at gtkmenushell.c line 710
  • #16 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 86
  • #17 g_closure_invoke
    at gclosure.c line 767
  • #18 signal_emit_unlocked_R
    at gsignal.c line 3290
  • #19 g_signal_emit_valist
    at gsignal.c line 2993
  • #20 g_signal_emit
    at gsignal.c line 3040
  • #21 gtk_widget_event_internal
    at gtkwidget.c line 4995
  • #22 IA__gtk_propagate_event
    at gtkmain.c line 2488
  • #23 IA__gtk_main_do_event
    at gtkmain.c line 1683
  • #24 gdk_event_dispatch
    at gdkevents-x11.c line 2377
  • #25 g_main_dispatch
    at gmain.c line 2440
  • #26 g_main_context_dispatch
    at gmain.c line 3013
  • #27 g_main_context_iterate
    at gmain.c line 3091
  • #28 g_main_loop_run
    at gmain.c line 3299
  • #29 IA__gtk_main
    at gtkmain.c line 1255
  • #30 main
    at main.c line 322

Manuel, it is possible can you attach the pdf file? Thank.
Comment 2 Manuel Hiebel 2011-04-11 16:02:39 UTC
Created attachment 185724 [details]
gdb of the pdf http://hiebel.eu/pub/I2.pdf
Comment 3 Manuel Hiebel 2011-04-11 16:04:50 UTC
the pdf is here: http://hiebel.eu/pub/I2.pdf

And the attach 185724 is for this file.

(I'm not sure it was this one)
Comment 4 Fabio Durán Verdugo 2011-04-11 16:10:32 UTC
I can't reproduce in evince 3.0 using poppler/cairo 0.16.4 and test with evince 2.32 poppler/cairo 0.16.4 and can't reproduce too
Comment 5 Pascal Terjan 2011-05-11 22:43:04 UTC
The problem is in poppler:

Starting program: /home/pterjan/co/poppler/BUILD/poppler-0.16.4/glib/.libs/test-poppler-glib file:///home/pterjan/I2.pdf 1
[Thread debugging using libthread_db enabled]
Poppler version 0.16.4
Backend is POPPLER_BACKEND_CAIRO
	---------------------------------------------------------
	Document Metadata
	---------------------------------------------------------
	format:		PDF-1.5
	author:		boeglen
	creator:	Acrobat PDFMaker 9.0 pour Word
	producer:	Adobe PDF Library 9.0

Program received signal SIGSEGV, Segmentation fault.
0xf7c45043 in vfprintf () from /lib/i686/libc.so.6
Missing debug package(s), you should install: cairo-debug-1.10.2-3.mga1.i586 fontconfig-debug-2.8.0-5.mga1.i586 freetype2-debug-2.4.4-4.mga1.i586 gcc-debug-4.5.2-4.mga1.i586 gdk-pixbuf2.0-debug-2.22.1-3.mga1.i586 glib2.0-debug-2.28.6-1.mga1.i586 glibc-debug-2.12.1-11.mga1.i586 libjpeg-debug-8b-5.mga1.i586 libpng-debug-1.2.44-3.mga1.i586 libx11-debug-1.4.3-1.mga1.i586 libxau-debug-1.0.6-1.mga1.i586 libxcb-debug-1.7-1.mga1.i586 libxdmcp-debug-1.1.0-1.mga1.i586 libxrender-debug-0.9.6-1.mga1.i586 openjpeg-debug-1.3-7.mga1.i586 pcre-debug-8.12-1.mga1.i586 pixman-debug-0.20.2-1.mga1.i586 zlib-debug-1.2.5-3.mga1.i586
(gdb) bt
  • #0 vfprintf
    from /lib/i686/libc.so.6
  • #1 __printf_chk
    from /lib/i686/libc.so.6
  • #2 printf
    at /usr/include/bits/stdio2.h line 105
  • #3 print_document_info
    at test-poppler-glib.cc line 136
  • #4 main
    at test-poppler-glib.cc line 419
  • #0 vfprintf
    from /lib/i686/libc.so.6
  • #1 __printf_chk
    from /lib/i686/libc.so.6
  • #2 printf
    at /usr/include/bits/stdio2.h line 105
  • #3 print_document_info
    at test-poppler-glib.cc line 136

Comment 6 Pascal Terjan 2011-05-11 22:50:32 UTC
It seems "linearized" is used as gchar * in test-poppler-glib.cc and evince, while it is a boolean

  g_object_class_install_property (G_OBJECT_CLASS (klass),
                                   PROP_LINEARIZED,
                                   g_param_spec_boolean ("linearized",
                                                         "Fast Web View Enabled",
                                                         "Is the document optimized for web viewing?",
                                                         FALSE,
                                                         G_PARAM_READABLE));
Comment 8 José Aliste 2011-05-11 22:55:38 UTC
Pascal, which version of evince are you viewing? there is an incompatibility between evince 2.32 and poppler-0.16. Basically, poppler 0.16 was released after evince 2.32, and there was an api change in the poppler-glib bindings.
Comment 9 Pascal Terjan 2011-05-11 23:05:44 UTC
2.32.0 with poppler 0.16.4 which in comment 4 you said you tested :)

I will apply the patch to my 2.32, do you think it is worth adding to the 2-32 branch? that branch contains some security fixes so it would be nice to have a 2.32.1 release :)
Comment 10 Christian Persch 2012-07-06 18:37:56 UTC
This doesn't happen on 3.x , and 2.32 is obsolete; closing.