GNOME Bugzilla – Bug 483381
crash in Gimmie:
Last modified: 2007-10-06 11:01:32 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gperfection2 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 (61 sec old) --------------------- (nautilus:5410): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\stmailhot\sTemplates\sdocumentation\sproject' to action group 'TemplatesGroup' (nautilus:5410): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\stmailhot\sTemplates\sdocumentation' to action group 'TemplatesGroup' (nautilus:5410): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\stmailhot\sTemplates\sdocumentation\sproject' to action group 'TemplatesGroup' INFO [SERVICE ] Submitting song to Last.fm /bin/sh: /usr/bin/esd: not found /bin/sh: /usr/bin/esd: not found INFO [PLAYER ] Stop INFO [PLAYER ] Started play of file 08._Anti-Flag_-_The_Panama_Deception.mp3 INFO [PROCESS ] Checking for repository changes... (10:28:00) INFO [SERVICE ] Submitting song to Last.fm INFO [PLAYER ] Stop INFO [PLAYER ] Started play of file 09._Anti-Flag_-_Culture_Revolution.mp3 INFO [SERVICE ] Submitting song to Last.fm -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 167718
printer.connect("attributes_changed", lambda p: self.emit("reload"))
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 475020 ***