Bug 307885 – >=app-text/evince-2.28.2 segfaults on a DVI file, possibly a ghostscript problem

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Vladimír Čunát 2010-03-05 13:35:05 UTC]

When I open a particular DVI file in evince, it always crashes. In okular it displays OK.
it's evince-2.28.2, flags: dbus debug djvu -doc dvi gnome gnome-keyring nautilus t1lib tiff
app-text/ghostscript-gpl-8.64-r3, flags: X -bindist cairo -cjk cups djvu gtk jpeg2k
media-libs/t1lib-5.1.2, flags: X -doc

I've got a trace:

** (evince:7603): WARNING **: Failed to create dbus proxy for org.gnome.SettingsDaemon: Could not get owner of name 'org.gnome.SettingsDaemon': no such name
[New Thread 0xac67ab70 (LWP 7613)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xac67ab70 (LWP 7613)]
0xab7469b1 in ref_stack_push_block (pstack=0xab643d04, keep=0, add=0) at ./psi/istack.c:515
515	./psi/istack.c: No such file or directory.
	in ./psi/istack.c
(gdb) bt
#0  0xab7469b1 in ref_stack_push_block (pstack=0xab643d04, keep=0, add=0) at ./psi/istack.c:515
#1  0xab746fd7 in ref_stack_push (pstack=0xab643d04, count=1) at ./psi/istack.c:475
#2  0xab743cf9 in scan_token (i_ctx_p=0xab643be4, pref=0x0, pstate=0xab63b73a) at ./psi/iscan.c:510
#3  0xab612895 in scan_font (FontP=0x8485220) at scanfont.c:1278
#4  0xab60a73b in readFont (env=0x84848c0 "/usr/share/texmf-dist/fonts/type1/bluesky/cm/cmsy10.pfb") at fontfcn.c:214
#5  0xab60a78f in fontfcnA (env=0x84848c0 "/usr/share/texmf-dist/fonts/type1/bluesky/cm/cmsy10.pfb", mode=0xac679fa8, Font_Ptr=0x8485220) at fontfcn.c:521
#6  0xab628b50 in T1_LoadFont (FontID=0) at t1load.c:151
#7  0xabe6df17 in t1_really_load_font (params=0x82eaa2c, font=0x8421030, code=15) at t1.c:304
#8  t1_font_get_glyph (params=0x82eaa2c, font=0x8421030, code=15) at t1.c:502
#9  0xabe654e0 in load_one_glyph (dvi=0x82eaa00, font=0x8421030, code=15) at font.c:286
#10 font_get_glyph (dvi=0x82eaa00, font=0x8421030, code=15) at font.c:359
#11 0xabe62286 in set_char (dvi=0x82eaa00, opcode=15) at dviread.c:1291
#12 0xabe63be5 in mdvi_dopage (dvi=0x82eaa00, pageno=0) at dviread.c:1091
#13 0xabe5dc79 in mdvi_cairo_device_render (dvi=0x82eaa00) at cairo-device.c:346
#14 0xabe5ceac in dvi_document_render (document=0x82604b8, rc=0x8268aa0) at dvi-document.c:193
#15 0xb7fa33b0 in ev_document_render (document=0x82604b8, rc=0x8268aa0) at ev-document.c:257
#16 0xb7f78e98 in ev_job_render_run (job=0x847a800) at ev-jobs.c:521
#17 0xb7f75581 in ev_job_run (job=0x847a800) at ev-jobs.c:212
#18 0xb7f7a0b8 in ev_job_thread (data=0x0) at ev-job-scheduler.c:183
#19 ev_job_thread_proxy (data=0x0) at ev-job-scheduler.c:213
#20 0xb720be84 in g_thread_create_proxy (data=0x8348430) at gthread.c:635
#21 0xb746d51f in start_thread () from /lib/libpthread.so.0
#22 0xb6fab7be in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
(gdb) list
510	in ./psi/istack.c
(gdb) q

I'll attach the file. If You need any more info, tell me.

Reproducible: Always

Steps to Reproduce:
Open the file in any way (e.g. recovery).

[Comment 1 Vladimír Čunát 2010-03-05 13:36:44 UTC]

Created attachment 222173 [details]
The crashing DVI

[Comment 2 Christian Kotz 2010-05-29 20:02:14 UTC]

can confirm this:
app-text/evince-2.28.2  USE="dbus djvu dvi gnome gnome-keyring nautilus t1lib tiff -debug -doc"
bugbuddy info see atachment

[Comment 3 Christian Kotz 2010-05-29 20:02:58 UTC]

Created attachment 233447 [details]
bug buddy info to crash

[Comment 4 Christian Kotz 2010-05-29 20:03:48 UTC]

Created attachment 233449 [details]
bug buddy info to crash

[Comment 5 Pacho Ramos 2010-10-17 19:23:00 UTC]

Fixed in 2.32