GNOME Bugzilla – Bug 485581
crash in Deskbar:
Last modified: 2007-10-12 10:20:43 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-14-generic #1 SMP Wed Oct 10 06:00:47 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Tangerine 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 (245 sec old) --------------------- alarm-notify.c:349 (alarm_msg_received) - 0x80fb318: Received at thread b4afdb90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80fdbb0 alarm-queue.c:581 (load_alarms_for_today) - From Thu Oct 11 03:57:42 2007 to Thu Oct 11 03:57:42 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80fb318: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/erbe/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80f1188: ReceivedAvís del gestor de finestres: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000056 (Llista d'a) Avís del gestor de finestres: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. (gnome-panel:5890): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -28 and height 24 PID TTY TIME CMD -------------------------------------------------- Traceback (most recent call last):
+ Trace 169384
cell.set_property ("has-more-actions", len(match.get_actions()) > 1)
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 471672 ***