GNOME Bugzilla – Bug 557143
crash in Document Viewer:
Last modified: 2008-11-02 22:40:08 UTC
Version: 2.22.2 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Raleigh Icon Theme: gnome Memory status: size: 85049344 vsize: 85049344 resident: 56881152 share: 17309696 rss: 56881152 rss_rlim: 4294967295 CPU usage: start_time: 1224528798 rtime: 4449 utime: 4037 stime: 412 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' [Thread debugging using libthread_db enabled] [New Thread 0xb6b43700 (LWP 6716)] [New Thread 0xb6871b90 (LWP 6717)] 0xb7f5e424 in __kernel_vsyscall ()
+ Trace 208450
Thread 2 (Thread 0xb6871b90 (LWP 6717))
----------- .xsession-errors --------------------- [109] [110] [111] [112] [113] [114] [115] [116] [117] [118] [119] [120] [121] [122]) (/usr/share/texmf-texlive/fonts/source/jknappen/ec/exrdigit.mf Ok [48] [49] [50] [51] [52] [53] [54] [55] [56] [57]) (/usr/share/texmf-texlive/fonts/source/jknappen/ec/exrligtb.mf Ok) ) ) ) Font metrics written on ecrm0700.tfm. Output written on ecrm0700.600gf (256 characters, 37524 bytes). Transcript written on ecrm0700.log. mktexpk: /home/sebas/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecrm0700.600pk: successfully generated. kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 ecbx0700 mktexpk: /home/sebas/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecbx0700.600pk already exists. (evince:6716): GLib-GObject-WARNING **: cannot add interface type `EvDocumentThumbnails' to type `DviDocument', since type `DviDocument' already conforms to interface (evince:6716): GLib-GObject-WARNING **: cannot add interface type `EvFileExporter' to type `DviDocument', since type `DviDocument' already conforms to interface --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade to 2.24. *** This bug has been marked as a duplicate of 519679 ***