GNOME Bugzilla – Bug 419275
crash in Gimmie: clicked on "Applications...
Last modified: 2007-05-26 01:29:23 UTC
What were you doing when the application crashed? clicked on "Applications" -> "last used" Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 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 --------------------- alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d88e8: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/jorma/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80dc4c0:** Message: drive = 0 ** Message: volume = 0 (gnome-panel:5276): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 ** Message: <information> Sie sind nun mit dem drahtlosen Netzwerk 'LinuxRoute' verbunden. checking for valid crashreport now DOUBLE-CLICK: 400 --> -1 THRESHOLD: 8 --> -1 current dist not found in meta-release file checking for valid crashreport now checking for valid crashreport now -------------------------------------------------- Traceback (most recent call last):
+ Trace 119360
icon_size = self._set_item(item, iter, store)
icon = item.get_icon(icon_size)
found = gnomedesktop.find_icon(icon_theme, self.icon_name, icon_size, 0)
What version of Gimmie are you using? This should be fixed in 0.2.5.
The version I am using is 0.2.4.repack-0ubuntu1.
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 415965 ***