GNOME Bugzilla – Bug 551074
crash in Document Viewer: Opening the datasheet fo...
Last modified: 2008-10-23 22:35:42 UTC
Version: 2.22.2 What were you doing when the application crashed? Opening the datasheet for the CP2102 USB-to-RS232 converter, available at https://www.silabs.com/Support%20Documents/TechnicalDocs/cp2102.pdf . Sorry there are no debug symbols; I have successfully opened this pdf before, so I may not be able to repeat the bug after installing debugging info Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24.2 #2 SMP PREEMPT Sun Mar 9 21:55:53 CDT 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: gnome Memory status: size: 251932672 vsize: 251932672 resident: 44417024 share: 13221888 rss: 44417024 rss_rlim: 18446744073709551615 CPU usage: start_time: 1220674437 rtime: 59 utime: 46 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b75956ea300 (LWP 3581)] [New Thread 0x40800950 (LWP 3582)] (no debugging symbols found) 0x00002b7590cb45ef in waitpid () from /lib/libpthread.so.0
+ Trace 206386
Thread 1 (Thread 0x2b75956ea300 (LWP 3581))
----------- .xsession-errors (385465 sec old) --------------------- (firefox-bin:9844): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: cannot open shared object file: No such file or directory perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = "en_US.UTF-8" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). (firefox-bin:9853): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. ...Too much output, ignoring rest... --------------------------------------------------
After this crash, I opened the same PDF file again with no problems, and I hadn't even installed the debuginfo yet. I don't think there's any useful information in the crash report, and I don't think I can get a better one, so I'm closing the bug.
After opening the same PDF file again many times, I saw that there seem to be four things that can happen when evince starts up viewing page 7 of the CP2102 datasheet PDF, which I will attach: 1. The page renders as it should. 2. The entire page renders as solid black. 3. The rest of the page besides the figure renders fine; the figure itself renders as blank. 4. Evince crashes. Under conditions 1, 2 or 3, the rest of the pages in the PDF seem to render fine. I got the evince-dbg package, but also need to get debuginfo for the libraries before the backtrace will be of any use.
Created attachment 118171 [details] Datasheet for CP2102 chip. Page 7 sometimes has interesting rendering problems.
Got libglib-2.0-0-dbg, libgtk-2.0-0-dbg, libcairo2-dbg. This caused upgrades for the libglib-2.0-0 and libgtk2.0-0 packages. Now it's much harder to get evince to crash, but sometimes it says "Loading..." for a longer time than before, and now that page sometimes shows not all black, but nearly covered by random polygons. Will attach sample screenshot thumbnails. (Combining comments to avoid excessive email traffic.) Having finally gotten it to crash again, I see I'm missing more debuginfo. Fetching poppler-dbg caused an upgrade to libpoppler3, from 0.8.4-1.1 to 0.8.6-1. It seems still capable of rendering seemingly random polygons. Got some sense and ran evince under gdb myself instead of double-clicking the PDF in Nautilus. On a run where it rendered page 7 as completely black, it spit out thousands of rendering errors. Attaching them.
Created attachment 118172 [details] rendering error messages on page 7 of cp2102.pdf
I think this problem is already fixed in evince 2.23.91. Could you confirm it, please?
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 415714 ***