GNOME Bugzilla – Bug 433893
crash in Gimmie: open docs
Last modified: 2007-05-26 01:45:37 UTC
What were you doing when the application crashed? open docs Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks 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 (48 sec old) --------------------- QImage::smoothScale: Image is a null image QImage::smoothScale: Image is a null image Unable to open desktop file /usr/share/applications/nexuiz.desktop for panel launcher: No such file or directory Unable to open desktop file file:///home/necrodome/Desktop/IE6.0.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/nexuiz.desktop for panel launcher: No such file or directory Unable to open desktop file file:///home/necrodome/Desktop/IE6.0.desktop for panel launcher: No such file or directory CalDAV Eplugin starting up ... ** (evolution-2.10:14595): WARNING **: LDAP authentication failed (0x51) (evolution-2.10:14595): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution-2.10:14595): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution-2.10:14595): DEBUG: mailto URL command: evolution %s ** (evolution-2.10:14595): DEBUG: mailto URL program: evolution -------------------------------------------------- Traceback (most recent call last):
+ Trace 130913
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 ***