GNOME Bugzilla – Bug 496940
crash in Deskbar:
Last modified: 2007-11-15 14:44:40 UTC
What were you doing when the application crashed? 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-386 #2 Sun Sep 23 19:47:10 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome 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 (7 sec old) --------------------- alarm-queue.c:497 (load_alarms) alarm-notify.c:393 (cal_opened_cb) file:///home/scottanon/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80cd6e8: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80c3f98: Received at thread b45d9b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80cbf20 alarm-queue.c:560 (load_alarms_for_today) - From Wed Nov 14 21:40:55 2007 to Wed Nov 14 21:40:55 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80c3f98: 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:3 -------------------------------------------------- Traceback (most recent call last):
+ Trace 177795
deskbar.DeskbarApplet.DeskbarApplet(applet)
self.ui = CuemiacButtonUI (applet, self.prefs)
self.cuemiac.set_layout_by_orientation (applet.get_orient())
self.layout.set_layout_by_orientation (self, orient)
self.on_change_size (self.applet)
self.cbutton.set_button_image_from_file (join(deskbar.ART_DATA_DIR, image_name), s)
pixbuf = gtk.gdk.pixbuf_new_from_file_at_size (filename, size, -1)
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 354391 ***