GNOME Bugzilla – Bug 488672
crash in Gimmie: I clicked the "Recently ...
Last modified: 2007-10-21 21:35:04 UTC
What were you doing when the application crashed? I clicked the "Recently Used" button in the Linux Tab. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Murrina_ArtOfCappuccino Icon Theme: Buuf 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) --------------------- Raydium: Object num 28: 150 vertex(s) - loaded as "lania2b.tri" Raydium: Object num 29: 96 vertex(s) - loaded as "wania13.tri" Raydium: Object num 30: 192 vertex(s) - loaded as "mania_whaut.tri" Raydium: Object num 31: 27384 vertex(s) - loaded as "/home/hoellp/.mania_drive/mania_visebien.mni.tri" Raydium: sound: Deleting sources Raydium: sound: Deleting buffers Raydium: sound: Releasing OpenAL Raydium: path: read: "/home/hoellp/.mania_drive/data" Raydium: path: write: "/home/hoellp/.mania_drive/data" (gnome-panel:11693): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 26 Desktop-Datei file:///usr/share/applications/gaim.desktop konnte nicht für Panel-Starter : geöffnet werdenNo such file or directory Desktop-Datei /usr/share/applications/googleearth.desktop konnte nicht für Panel-Starter : geöffnet werdenNo such file or directory Desktop-Datei file:///usr/share/applications/gaim.desktop konnte nicht für Panel-Starter : geöffnet werdenNo such file or directory Desktop-Datei /usr/share/applications/googleearth.desktop konnte nicht für Panel-Starter : geöffnet werdenNo such file or directory -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 171740
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 ***