GNOME Bugzilla – Bug 491543
crash in Deskbar: Meu gutsy estava apenas ...
Last modified: 2007-10-30 11:21:27 UTC
What were you doing when the application crashed? Meu gutsy estava apenas iniciando. Não havia feito absolutamente nada ainda. 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: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mist 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 --------------------- alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80e4ac0: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/jader/.evolution/tasks/local/system - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80e82f8: Received at thread b4dd1b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80e6240 alarm-queue.c:581 (load_alarms_for_today) - From Mon Oct 29 20:53:34 2007 to Mon Oct 29 20:53:34 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80e82f8: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/jader/.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) - 0x80ec210:/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format -------------------------------------------------- Traceback (most recent call last):
+ Trace 173774
dapplet = DeskbarApplet(applet)
self.on_change_size()
self.set_button_image_from_file (join(deskbar.ART_DATA_DIR, image_name), s)
pixbuf = gtk.gdk.pixbuf_new_from_file_at_size (filename, -1, size)
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 ***