GNOME Bugzilla – Bug 501435
crash in Gimmie:
Last modified: 2008-03-07 11:49:32 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: T-ish-Brushed-bright-Aquastyle Icon Theme: Vista-Inspirate_1.0 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 (3907 sec old) --------------------- fixme:mlang:fnIMLangFontLink_GetStrCodePages (pszSrc=L"\9876\90e8 ", cchSrc=1, dwPriorityCodePages=1) stub fixme:mlang:fnIMLangFontLink_MapFont fixme:mlang:fnIMLangFontLink_GetStrCodePages (pszSrc=L"\90e8 ", cchSrc=1, dwPriorityCodePages=1) stub fixme:mlang:fnIMLangFontLink_MapFont fixme:mlang:fnIMLangFontLink_GetStrCodePages (pszSrc=L"\9876\90e8 ", cchSrc=1, dwPriorityCodePages=1) stub fixme:mlang:fnIMLangFontLink_MapFont fixme:mlang:fnIMLangFontLink_GetStrCodePages (pszSrc=L"\90e8 ", cchSrc=1, dwPriorityCodePages=1) stub fixme:mlang:fnIMLangFontLink_MapFont fixme:mlang:fnIMLangFontLink_GetStrCodePages (pszSrc=L"\9876\90e8 ", cchSrc=1, dwPriorityCodePages=1) stub fixme:mlang:fnIMLangFontLink_MapFont fixme:mlang:fnIMLangFontLink_GetStrCodePages (pszSrc=L"\90e8 ", cchSrc=1, dwPriorityCodePages=1) stub fixme:mlang:fnIMLangFontLink_MapFont fixme:mlang:fnIMLangFontLink_GetStrCodePages (pszSrc=L"\9876\90e8 ", cchSrc=1, dwPriorityCodePages=1) stub ...Too much output, ignoring rest... -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 180665
import gimmie.gimmie
import gnome
from _gnome import *
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 492208 ***