GNOME Bugzilla – Bug 456722
crash in Gimmie: playing assault cube
Last modified: 2007-09-08 22:11:02 UTC
What were you doing when the application crashed? playing assault cube Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-lowlatency #2 SMP PREEMPT Thu Jun 7 20:23:03 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: UbuntuStudio Icon Theme: UbuntuStudio 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 (85 sec old) --------------------- alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d4530 alarm-queue.c:560 (load_alarms_for_today) - From Fri Jul 13 16:10:41 2007 to Fri Jul 13 16:10:41 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d7f98: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/dazzle/.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) - 0modinfo: could not find module fglrx modinfo: could not find module nvidia_legacy modinfo: could not find module nvidia_new modinfo: could not find module nvidia (gnome-panel:5949): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 27 -------------------------------------------------- Traceback (most recent call last):
+ Trace 147876
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)
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 ***