GNOME Bugzilla – Bug 450126
crash in Gimmie: 1.-iniciando crosover 2...
Last modified: 2007-06-23 16:26:57 UTC
What were you doing when the application crashed? 1.-iniciando crosover 2.-intentando utilizar el menu "gente" 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-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: UbuntuStudio Icon Theme: UbuntuStudio 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 --------------------- ** (update-notifier:5677): WARNING **: no cdrom: disk Advertencia del gestor de ventanas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000027 (Reproducto) Advertencia del gestor de ventanas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. checking for valid crashreport now closing ** Message: <information> Ahora está conectado a la red inalámbrica Enter System. Xlib: extension "XFree86-DRI" missing on display ":0.0". Xlib: extension "XFree86-DRI" missing on display ":0.0". Xlib: extension "XFree86-DRI" missing on display ":0.0". Xlib: extension "XFree86-DRI" missing on display ":0.0". Advertencia del gestor de ventanas: Treating resize request of legacy application 0x5000001 () as a fullscreen request Xlib: extension "XFree86-DRI" missing on display ":0.0". Advertencia del gestor de ventanas: WM_TRANSIENT_FOR inválido para la ventana 0x5000006 especificada para 0x5000008 (). -------------------------------------------------- Traceback (most recent call last):
+ Trace 142948
self.recent_items[recent_item.get_uri()] = recent_item
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 417988 ***