GNOME Bugzilla – Bug 445046
crash in Gimmie: Kiba-dock beendet und da...
Last modified: 2007-09-08 22:10:29 UTC
What were you doing when the application crashed? Kiba-dock beendet und dann die such unter "Anwndungen" verwendet 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 Wed May 23 01:49:41 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 (558 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80d37d8: Replied to GUI thread alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80bbf08: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) (gnome-panel:5593): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -12 and height 24 ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) -------------------------------------------------- Traceback (most recent call last):
+ Trace 139008
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 ***