GNOME Bugzilla – Bug 533004
crash in File Browser: Distribution: Debian len...
Last modified: 2008-05-13 23:25:42 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: black-white_2-Neon_big Memory status: size: 81104896 vsize: 81104896 resident: 26185728 share: 15339520 rss: 26185728 rss_rlim: 4294967295 CPU usage: start_time: 1210688354 rtime: 483 utime: 122 stime: 361 cutime:0 cstime: 0 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 0xb6bcc720 (LWP 3313)] (no debugging symbols found) 0xffffe402 in __kernel_vsyscall ()
+ Trace 197649
Thread 1 (Thread 0xb6bcc720 (LWP 3313))
----------- .xsession-errors (10 sec old) --------------------- (gnome-appearance-properties:3451): Gtk-WARNING **: Imposible encontrar el motor de temas en la ruta al _modulo: «murrine», (gnome-appearance-properties:3451): Gtk-WARNING **: Imposible encontrar el motor de temas en la ruta al _modulo: «murrine», (gnome-appearance-properties:3451): Gtk-WARNING **: Imposible encontrar el motor de temas en la ruta al _modulo: «murrine», <stdin>:130:14: warning: missing terminating ' character <stdin>:130:14: warning: missing terminating ' character <stdin>:130:14: warning: missing terminating ' character <stdin>:130:14: warning: missing terminating ' character <stdin>:130:14: warning: missing terminating ' character connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
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 522534 ***