GNOME Bugzilla – Bug 503060
crash in Deskbar: I was trying to start xt...
Last modified: 2007-12-13 13:28:09 UTC
What were you doing when the application crashed? I was trying to start xterm with it. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (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: Disabled GTK+ Theme: Mist 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 (37 sec old) --------------------- alarm-notify.c:349 (alarm_msg_received) - 0x80bf3b8: Received at thread b4bfdb90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80dc7a0 alarm-notify.c:337 (alarm_msgport_replied) - 0x80d5c78: Replied to GUI thread alarm-queue.c:581 (load_alarms_for_today) - From Tue Dec 11 15:43:22 2007 to Tue Dec 11 15:43:22 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80bf3b8: 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) - 0/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format (gnome-panel:5758): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -17 and height 24 -------------------------------------------------- Traceback (most recent call last):
+ Trace 181552
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
if text.startswith(query):
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 475351 ***