GNOME Bugzilla – Bug 424986
crash in Gimmie:
Last modified: 2007-04-02 06:54:36 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: T-ish-Ubuntulooks-Aquastyle Icon Theme: OSX 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 (32 sec old) --------------------- ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) Cutting log (size: 101676, max: 100000)Spinner image is wrong size Ostrzeżenie menedżera okien: Nieprawidłowa wartość WM_TRANSIENT_FOR dla okna 0x75 określona w 0x2a000f4 (). Ostrzeżenie menedżera okien: Nieprawidłowa wartość WM_TRANSIENT_FOR dla okna 0x75 określona w 0x2a002b7 (). (gnome-background-properties:6426): Gtk-WARNING **: Nie można odnaleźć modułu obsługującego motyw w module_path: "pixmap", ** (nautilus:5843): WARNING **: Hit unhandled case 38 (Usługa nie jest dostępna) in fm_report_error_loading_directory ** (nautilus:5843): WARNING **: Nie odnaleziono opisu typu MIME "x-directory/smb-share" (plik "Siec"), napisz na listę gnome-vfs (w języku angielskim). Ostrzeżenie menedżera okien: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200003 (Odtwarzacz) Ostrzeżenie menedżera okien: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. -------------------------------------------------- Traceback (most recent call last):
+ Trace 123920
cmp(item1.get_name().lower(), item2.get_name().lower())
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 419093 ***