GNOME Bugzilla – Bug 429455
crash in Gimmie: I just clicked "Programs...
Last modified: 2007-04-22 22:23:17 UTC
What were you doing when the application crashed? I just clicked "Programs". Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-14-386 #2 Mon Apr 2 20:34:35 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human 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 (359 sec old) --------------------- (evolution-2.10:5689): e-utils-WARNING **: Plugin 'Plugin de não solicitados Spamassassin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution-2.10:5689): DEBUG: mailto URL command: evolution %s ** (evolution-2.10:5689): DEBUG: mailto URL program: evolution process 5689: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details. Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection. ** Message: <information> Está agora ligado à rede sem fios 'ptchallenge'. CalDAV Eplugin starting up ... (evolution-2.10:10066): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution-2.10:10066): e-utils-WARNING **: Plugin 'Plugin de não solicitados Spamassassin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution-2.10:10066): DEBUG: mailto URL command: evolution %s ** (evolution-2.10:10066): DEBUG: mailto URL program: evolution -------------------------------------------------- Traceback (most recent call last):
+ Trace 127533
elif ev_win.get_toplevel() != self.window:
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 ***