GNOME Bugzilla – Bug 494269
crash in Deskbar: made a search with Deskb...
Last modified: 2007-11-08 19:13:51 UTC
What were you doing when the application crashed? made a search with Deskbar-Applet 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 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Enabled GTK+ Theme: Human Icon Theme: Buuf 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 (147 sec old) --------------------- alarm-notify.c:349 (alarm_msg_received) - 0x80ee388: Received at thread b5528b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x81043a0 alarm-queue.c:581 (load_alarms_for_today) - From Tue Nov 6 00:00:00 2007 to Tue Nov 6 00:00:00 2007 alarm-queue.c:518 (load_alarms) alarm-notify.c:393 (cal_opened_cb) file:///home/christoph/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x8101c88: Received at thre Verbinden mit Daemon [ ### ] Verbinden mit Daemon [ ### ] Verbinden mit Daemon [### ] Verbinden mit Daemo gnome-mount 0.6 (gnome-panel:6555): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x811db88 (gnome-panel:6555): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x811db88 -------------------------------------------------- Traceback (most recent call last):
+ Trace 175818
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 ***