GNOME Bugzilla – Bug 541615
crash in Gimmie: clicked "Recently used"
Last modified: 2008-07-06 14:36:03 UTC
What were you doing when the application crashed? clicked "Recently used" Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.2 2008-06-03 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome 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 (44 sec old) --------------------- Unable to open desktop file /home/yunta/Desktop/PlaneShift Client.desktop for panel launcher: No such file or directory evolution-alarm-notify-Message: Alarm callback! evolution-alarm-notify-Message: Process alarm with trigger 1215216000 evolution-alarm-notify-Message: alarm.c:246: Requested removal of nonexistent alarm! evolution-alarm-notify-Message: Setting timeout for 86400 1215302400 1215216000 evolution-alarm-notify-Message: Sun Jul 6 02:00:00 2008 evolution-alarm-notify-Message: Sat Jul 5 02:00:00 2008 Incoming PEX message flood detected, dropping spamming peer connection.L: 122.107.152.139: 29318 [Azureus 3.1.1.0] Unable to open desktop file /home/yunta/Desktop/PlaneShift Client.desktop for panel launcher: No such file or directory Unable to open desktop file /home/yunta/Desktop/PlaneShift Client.desktop for panel launcher: No such file or directory Unable to open desktop file /home/yunta/Desktop/PlaneShift Client.desktop for panel launcher: No such file or directory Unable to open desktop file /home/yunta/Desktop/PlaneShift Client.desktop for panel launcher: No such file or directory Unable to open desktop file /home/yunta/Desktop/PlaneShift Client.desktop for panel launcher: No such file or directory -------------------------------------------------- Gimmie Version: 0.2.8 Traceback (most recent call last):
+ Trace 202079
printer.connect("attributes_changed", lambda *args: self.emit("reload"))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 475020 ***