GNOME Bugzilla – Bug 541214
crash in File Browser:
Last modified: 2008-07-02 12:20:36 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 455462912 vsize: 455462912 resident: 39194624 share: 17829888 rss: 39194624 rss_rlim: 18446744073709551615 CPU usage: start_time: 1214977103 rtime: 2982 utime: 2770 stime: 212 cutime:0 cstime: 4 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b688123d220 (LWP 3874)] [New Thread 0x43005950 (LWP 14621)] (no debugging symbols found) 0x00002b687a1e2edf in waitpid () from /lib/libpthread.so.0
+ Trace 201894
Thread 1 (Thread 0x2b688123d220 (LWP 3874))
----------- .xsession-errors (133 sec old) --------------------- (glade-3:12091): Gtk-CRITICAL **: gtk_combo_box_append_text: assertion `GTK_IS_LIST_STORE (combo_box->priv->model)' failed (glade-3:12091): Gtk-CRITICAL **: gtk_combo_box_append_text: assertion `GTK_IS_LIST_STORE (combo_box->priv->model)' failed (glade-3:12091): Gtk-CRITICAL **: gtk_combo_box_entry_set_text_column: assertion `text_column >= 0' failed ** Message: <info> Forcing device '/org/freedesktop/NetworkManager/Devices/wlan0' ** Message: <info> Ahora está conectado a la red inalámbrica verdnatura. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-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 ***