GNOME Bugzilla – Bug 483965
crash in Gimmie: I double clicked on a .o...
Last modified: 2007-10-06 11:55:21 UTC
What were you doing when the application crashed? I double clicked on a .odt file in Nautilus. While OO Writer was opening, I double clicked on a different. 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 Sun Sep 23 19:50:39 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 (1051 sec old) --------------------- alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:1837 (CalDAV Eplugin starting up ... (evolution-2.10:8520): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution-2.10:8520): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution-2.10:8520): DEBUG: mailto URL command: evolution %s ** (evolution-2.10:8520): DEBUG: mailto URL program: evolution process 8520: 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. -------------------------------------------------- Traceback (most recent call last):
+ Trace 168185
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 ***