GNOME Bugzilla – Bug 533886
crash in Open Folder: opening a windows share
Last modified: 2008-05-19 19:02:29 UTC
Version: 2.20.0 What were you doing when the application crashed? opening a windows share 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: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 76120064 vsize: 76120064 resident: 21356544 share: 14745600 rss: 21356544 rss_rlim: 4294967295 CPU usage: start_time: 1211183521 rtime: 367 utime: 327 stime: 40 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 0xb6b82720 (LWP 4101)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198134
Thread 1 (Thread 0xb6b82720 (LWP 4101))
----------- .xsession-errors (7 sec old) --------------------- ** (gnome-cups-manager:29102): CRITICAL **: hookup_check_button: assertion `option->n_choices == 2' failed ** (gnome-cups-manager:29102): CRITICAL **: hookup_check_button: assertion `option->n_choices == 2' failed ** (gnome-cups-manager:29102): CRITICAL **: hookup_check_button: assertion `option->n_choices == 2' failed ** (gnome-cups-manager:29102): CRITICAL **: hookup_check_button: assertion `option->n_choices == 2' failed ** (gnome-cups-manager:29102): CRITICAL **: hookup_check_button: assertion `option->n_choices == 2' failed 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 ***