GNOME Bugzilla – Bug 490715
crash in Deskbar: Wasn't doing anything. I...
Last modified: 2007-10-27 16:00:11 UTC
What were you doing when the application crashed? Wasn't doing anything. I had just restarted the computer and the first thing i did was desktop search. I was able to type a word in to see how how it worked, and view a few results before I 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 Sun Oct 14 21:45:15 GMT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled 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 (60 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x6f8fa0: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/tommy/.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) - 0x71c070: Received at thread 42044950 alarm-queue.c:2003 (alarm_queue_add_async) - 0x71ab00 alarm-queue.c:581 (load_alarms_for_today) - From Sat Oct 27 00:08:19 2007 to Sat Oct 27 00:08:19 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x71c070: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x719030: Received at t (gnome-panel:6635): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -28 and height 24 -------------------------------------------------- Traceback (most recent call last):
+ Trace 173168
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 ***