GNOME Bugzilla – Bug 439060
crash in Gimmie:
Last modified: 2007-05-19 02:41:31 UTC
What were you doing when the application crashed? 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-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Murrina-GreenMod Icon Theme: nuoveXT-1.6 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 (20 sec old) --------------------- Last playlist loaded Loading page 0 Warning: Gstreamer equalizer element not found, please install the latest gst-plugins-bad package new thread created with Excerpts Fragile Vastness cover thread started /home/peter/.exaile/covers/36d22f30eab5e54c147be9b235731554.jpg updated plays 1, rating 1 Attempting to submit track Little Red Riding Hood from Excerpts by Fragile Vastness to last.fm -AUDIOSCROBBLER- i[0]=2007-05-17%2008%3A23%3A57&b[0]=Excerpts&a[0]=Fragile%20Vastness&s=c640dfeeb1fabed4a51944c131a18c4b&u=Sir_Pepe&m[0]=&t[0]=Little%20Red%20Riding%20Hood&l[0]=396 2007-05-17 08:23:57: Uploaded 1 tracks successfully next track was reported as Weep No More from Excerpts by Fragile Vastness Aborted cover t (mail-notification:5559): mail-notification-WARNING **: m00d6bcd@mail.peterkroener.de: Die SASL-Authentifizierung konnte nicht gestartet werden: SASL(-4): no mechanism available: No worthy mechs found (nautilus:5545): libgnomevfs-WARNING **: gnome-vfs-monitor.c: A monitor handle was destroyed before it was added to the method hash table. This is a bug in the application and can cause crashes. It is -------------------------------------------------- Traceback (most recent call last):
+ Trace 134565
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 ***