GNOME Bugzilla – Bug 508284
crash in File Browser: proprietà icona
Last modified: 2008-01-10 01:15:00 UTC
Version: 2.18.3 What were you doing when the application crashed? proprietà icona Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: oxygnome Icon Theme: Oxygen-Refit Memory status: size: 109592576 vsize: 109592576 resident: 35807232 share: 16244736 rss: 35807232 rss_rlim: 4294967295 CPU usage: start_time: 1199824675 rtime: 10703 utime: 9030 stime: 1673 cutime:115 cstime: 35 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6e296b0 (LWP 10192)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 184662
Thread 1 (Thread 0xb6e296b0 (LWP 10192))
----------- .xsession-errors --------------------- (gnome-terminal:25023): Gtk-WARNING **: Impossibile trovare il motore del tema in module_path: «murrine», Invoking /usr/lib/wine/wine.bin uninstaller.exe ... /home/roberto/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style' (gnome-terminal:26915): Gtk-WARNING **: Impossibile trovare il motore del tema in module_path: «murrine», Wine exited with a successful status ** Message: drive = 0 ** Message: volume = 0 Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store)) aborting... /home/roberto/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style' (bug-buddy:27493): Gtk-WARNING **: Impossibile trovare il motore del tema in module_path: «murrine», --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 440988 ***