GNOME Bugzilla – Bug 428771
crash in Gimmie: I opened a LaTeX .dvi fi...
Last modified: 2007-04-12 22:33:59 UTC
What were you doing when the application crashed? I opened a LaTeX .dvi file from the Nautilus left-click menu, selecting "Custom application" then typing "xdvi" into the box and pressing Enter. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-11 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20.3-ubuntu1-oaktree3 #1 SMP Tue Mar 27 13:14:13 MDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Peace Icon Theme: Tango Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors --------------------- xdvi: Can't find pixel font op; using cmr10 instead at 420 dpi. kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+120/600 --dpi 720 opb mktexpk: don't know how to create bitmap font for opb. xdvi: Can't find pixel font opb; using cmr10 instead at 720 dpi. kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 0+360/600 --dpi 360 mtsyn mktexpk: don't know how to create bitmap font for mtsyn. xdvi: Can't find pixel font mtsyn; using cmr10 instead at 360 dpi. xdvi.bin: Warning: Checksum mismatch (dvi = 1495685498, vf = 3028759162) in font file /usr/share/texmf-tetex/fonts/vf/yandy/mathtime/mtmi.vf kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+240/600 --dpi 840 opb mktexpk: don't know how to create bitmap font for opb. xdvi: Can't find pixel font opb; using cmr10 instead at 840 dpi. kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 2+44/600 --dpi 1244 opb mktexpk: don't know how to create bitmap font for opb. xdvi: Can't find pixel font opb; using cmr10 instead at 1244 dpi. kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+264/600 --dpi 864 opb -------------------------------------------------- Traceback (most recent call last):
+ Trace 126982
self.recent_items[recent_item.get_uri()] = recent_item
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. *** This bug has been marked as a duplicate of 417988 ***