GNOME Bugzilla – Bug 504914
crash in Deskbar: Starting Firefox
Last modified: 2007-12-25 11:54:16 UTC
What were you doing when the application crashed? Starting Firefox 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 Tue Dec 18 08:02:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Blubuntu Icon Theme: nuoveXT.2.2 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 (91 sec old) --------------------- alarm-queue.c:2003 (alarm_queue_add_async) - 0x80dd0c0 alarm-queue.c:581 (load_alarms_for_today) - From Fri Dec 21 19:16:43 2007 to Fri Dec 21 19:16:43 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80e7028: 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_rece/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format Fontconfig error: "~/.fonts.conf", line 1: XML declaration not well-formed PID TTY TIME CMD Fontconfig error: "~/.fonts.conf", line 1: XML declaration not well-formed /usr/share/themes/Blubuntu/gtk-2.0/gtkrc:169: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. Fontconfig error: "~/.fonts.conf", line 1: XML declaration not well-formed -------------------------------------------------- Traceback (most recent call last):
+ Trace 182557
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 ***