GNOME Bugzilla – Bug 606047
crash in Document Viewer: just open a dvi file
Last modified: 2010-12-30 21:42:24 UTC
Version: 2.28.1 What were you doing when the application crashed? just open a dvi file Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-11-21 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.30-2-686-bigmem #1 SMP Fri Dec 4 02:13:28 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal GTK+ Modules: gnomebreakpad Memory status: size: 270049280 vsize: 270049280 resident: 189001728 share: 17117184 rss: 189001728 rss_rlim: 18446744073709551615 CPU usage: start_time: 1262631968 rtime: 6334 utime: 5625 stime: 709 cutime:1835 cstime: 374 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' [Thread debugging using libthread_db enabled] [New Thread 0xb33f7b70 (LWP 21830)] [New Thread 0xb594fb70 (LWP 20100)] 0xb80a4424 in __kernel_vsyscall ()
+ Trace 219884
Thread 3 (Thread 0xb594fb70 (LWP 20100))
A debugging session is active. Inferior 1 [process 20099] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** GLib-GObject **: g_value_set_object: assertion `G_IS_OBJECT (v_object)' failed ** GLib-GObject **: g_value_set_object: assertion `G_IS_OBJECT (v_object)' failed ** GLib-GObject **: g_value_set_object: assertion `G_IS_OBJECT (v_object)' failed ** GLib-GObject **: g_value_set_object: assertion `G_IS_OBJECT (v_object)' failed ** GLib-GObject **: g_value_set_object: assertion `G_IS_OBJECT (v_object)' failed ** GLib-GObject **: g_value_set_object: assertion `G_IS_OBJECT (v_object)' failed ----------- .xsession-errors --------------------- [124] [125] [126] [127] [128] [129] [130] [131] [132] [133] [134] [135] [136] [137] [138] [139] [140] [141] [142] [143] [144] [145] [146] [147] [148] [149] [150] [151] [152] [153] [154] [155] [156] [157] [158] [159] [160] [161] [162] [163] [164] [165] [166] [167] [168] [169] [170] [171] [172] [173] [174] [175] [176] [177] [178] [179] [180] [181] [182] [183] [184] [185] [186] [187] [188] [189] [190] [191] [192] [193] [194] [195] [196] [197] [198] [199] [200] [201] [202] [203] [204] [205] [206] [207] [208] [209] [210] [211] [212] [213] [214] [215] [216] [217] [218] [219] [220] [221] [222] [223] [224] [225] [226] [227] [228] [229] [230] [231] [232] [233] [234] [235] [236] [237] [238] [239] [240] [241] [242] [243] [244] [245] [246] [247] [248] [249] [250] [251] [252] [253] [254] [255] mktexpk: /home/mirkog/.texmf-var/fonts/pk/modeless/public/lm/ec-lmss10.657pk: successfully generated. some font thing failed some font thing failed Fontconfig error: Cannot load config file "70-no-bitmaps.conf" --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
I can't provide much more info, but I've exactly the same problem here (on x86_64, not x86): When opening a .dvi document, the evince window appears for some fractions of a second, and then evince dumps core. Unfortunately, my whole system is optimized and without symbols (Gentoo, everything compiled here, so there are no debug packages), but the stack trace shows exactly the same functions as the one attached above:
+ Trace 220339
So that's when reading a font in libgs (from ghostscript-gpl-8.70 in my case) and libt1 (from t1lib-5.1.2 in my case). strace also shows that it happens when reading a TeX font: 32427 open("/usr/share/texmf-dist/fonts/type1/public/amsfonts/cm/cmr17.pfb", O_RDONLY) = 18 32427 read(18, "\200", 1) = 1 32427 lseek(18, 0, SEEK_SET) = 0 32427 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
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 bug 600552 ***
Please reopen, as far as I can tell from the traces, these are completely different crashes.
INCOMPLETE - There is simply nothing that can be done here without a good stacktrace or an example document.
Problem disappeared in 2.32.
... at least for me (see Comment 2).