crash on ctrl-left-arrow in Evince when filling a PDF form
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evince (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: evince
When filling in a PDF form, I typed ctrl+left-arrow and Evince crashed. By running via GDB, I gained the following output:
Starting program: /usr/bin/evince /home/john/
[Thread debugging using libthread_db enabled]
[New Thread 0xb6832b70 (LWP 13956)]
[New Thread 0xb569cb70 (LWP 13957)]
Program received signal SIGSEGV, Segmentation fault.
doc_rect_
doc_rect=0x0, view_rect=
965 ev-view.c: No such file or directory.
in ev-view.c
(gdb) where
#0 doc_rect_
doc_rect=0x0, view_rect=
#1 0x00a37335 in ev_view_
page=<value optimised out>, mapping_list=0x0, data=0x8511970,
area=
#2 0x00a39877 in ev_view_
field=<value optimised out>) at ev-view.c:1645
#3 0x00a3990f in ev_view_
widget=
#4 0x0043b951 in weak_refs_notify (data=0x864eef8)
at /build/
#5 0x005d2e83 in g_data_set_internal (datalist=
data=0x0, destroy_func=0)
at /build/
#6 IA__g_datalist_
destroy_func=0) at /build/
#7 0x0043bf89 in g_object_
at /build/
#8 0x00ba4ed1 in gtk_object_dispose (gobject=0x860c818)
at /build/
#9 0x00ca6360 in gtk_widget_dispose (object=0x860c818)
at /build/
#10 0x0043c110 in IA__g_object_unref (_object=0x860c818)
---Type <return> to continue, or q <return> to quit---
at /build/
#11 0x0045c688 in IA__g_value_unset (value=0x849b12c)
at /build/
#12 0x00450b56 in IA__g_signal_
detail=0, var_args=0xbfc24ff0 "HP¿0\017I")
at /build/
#13 0x00450fb6 in IA__g_signal_emit (instance=
detail=0) at /build/
#14 0x00aeb9b1 in IA__gtk_
widget=
#15 0x00a320c5 in ev_view_remove_all (view=<value optimised out>)
at ev-view.c:3143
#16 0x00a32138 in ev_view_
at ev-view.c:5225
#17 0x00a321b4 in ev_view_rotate_left (view=0x0) at ev-view.c:5212
#18 0x004479fc in IA__g_cclosure_
return_
invocation_
at /build/
#19 0x0043a072 in IA__g_closure_
n_param_
at /build/
#20 0x0044f7a8 in signal_
---Type <return> to continue, or q <return> to quit---
detail=<value optimised out>, instance=0x8355a60, emission_
instance_
at /build/
#21 0x00450b2d in IA__g_signal_
detail=0, var_args=0xbfc253ac "\304d\252")
at /build/
#22 0x00450fb6 in IA__g_signal_emit (instance=
detail=0) at /build/
#23 0x00aa4ed5 in _gtk_action_
at /build/
#24 0x00aa78c4 in closure_
return_
invocation_
at /build/
#25 0x0043a072 in IA__g_closure_
return_
invocation_
at /build/
#26 0x0044f7a8 in signal_
detail=<value optimised out>, instance=0x83aa800,
emission_
at /build/
#27 0x004509b8 in IA__g_signal_
---Type <return> to continue, or q <return> to quit---
detail=1107,
var_
at /build/
#28 0x00450fb6 in IA__g_signal_emit (instance=
detail=1107) at /build/
#29 0x00aa0ae1 in IA__gtk_
accel_
accel_
at /build/
#30 0x00aa0be5 in IA__gtk_
accel_
at /build/
#31 0x00cb3634 in IA__gtk_
event=
#32 0x00cb36bc in gtk_window_
event=
#33 0x00b7f474 in _gtk_marshal_
return_
invocation_
at /build/
#34 0x004386f9 in g_type_
return_
invocation_
---Type <return> to continue, or q <return> to quit---
at /build/
#35 0x0043a072 in IA__g_closure_
return_
invocation_
at /build/
#36 0x0044f49e in signal_
detail=<value optimised out>, instance=0x8393100,
emission_
at /build/
#37 0x004509b8 in IA__g_signal_
detail=0, var_args=0xbfc25b20 "\\[¿\364Of")
at /build/
#38 0x00450fb6 in IA__g_signal_emit (instance=
detail=0) at /build/
#39 0x00c9b95e in gtk_widget_
event=
#40 0x00b77ceb in IA__gtk_
at /build/
#41 0x00b78ea9 in IA__gtk_
at /build/
#42 0x002bc65a in gdk_event_dispatch (source=0x835f9d0, callback=0,
user_data=0x0) at /build/
#43 0x005e7e88 in g_main_dispatch (context=0x8334060)
---Type <return> to continue, or q <return> to quit---
at /build/
#44 IA__g_main_
at /build/
#45 0x005eb730 in g_main_
block=<value optimised out>, dispatch=1, self=0x8328050)
at /build/
#46 0x005ebb9f in IA__g_main_loop_run (loop=0x832a220)
at /build/
#47 0x00b79419 in IA__gtk_main ()
at /build/
#48 0x08080c52 in main (argc=1, argv=0xbfc25f14) at main.c:497
(gdb)
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.