GNOME Bugzilla – Bug 453523
crash in Gimmie: Open "Library" ->Click "...
Last modified: 2007-08-30 23:50:21 UTC
What were you doing when the application crashed? Open "Library" ->Click "Recently Used" Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: H2O-gtk2-Saphire Icon Theme: gartoon 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 (86 sec old) --------------------- *** CLB *** Initializing Google Browser Sync... *** CLB *** Instanciating core objects... *** CLB *** Registering with XPCOM... *** CLB *** Adding categories... *** CLB *** Google Browser Sync initialized succesfully! ** (gnome-cups-icon:5490): WARNING **: 无法启动打印机系统托盘图标，因为连接不到 CUPS 服务器。 无法打开面板启动器的 desktop 文件 /usr/share/applications/putty.desktop: No such file or directory 无法打开面板启动器的 desktop 文件 /usr/share/applications/freeloader.desktop: No such file or directory 无法打开面板启动器的 desktop 文件 /usr/share/applications/listen.desktop: No such file or directory 无法打开面板启动器的 desktop 文件 /usr/share/applications/bmp.desktop: No such file or directory 无法打开面板启动器的 desktop 文件 /usr/share/applications/putty.desktop: No such file or directory 无法打开面板启动器的 desktop 文件 /usr/share/applications/freeloader.desktop: No such file or directory 无法打开面板启动器的 desktop 文件 /usr/share/applications/listen.desktop: No such file or directory 无法打开面板启动器的 desktop 文件 /usr/share/applications/bmp.desktop: No such file or directory -------------------------------------------------- Traceback (most recent call last):
+ Trace 145571
cmp(item1.get_name().lower(), item2.get_name().lower())
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 419093 ***