GNOME Bugzilla – Bug 531913
crash in File Browser: connessione a risorsa co...
Last modified: 2008-05-07 12:19:33 UTC
Version: 2.20.0 What were you doing when the application crashed? connessione a risorsa condivisa su pc windows xp professional sp2 italiano 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: 69046272 vsize: 69046272 resident: 23236608 share: 15740928 rss: 23236608 rss_rlim: 4294967295 CPU usage: start_time: 1210150047 rtime: 1121 utime: 1032 stime: 89 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 0xb6c2a720 (LWP 2935)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 197112
Thread 1 (Thread 0xb6c2a720 (LWP 2935))
----------- .xsession-errors (16 sec old) --------------------- ** (gnome-cups-add:3109): WARNING **: model named 'Officejet H470' doesn't have a recognized structure ** (gnome-cups-add:3109): WARNING **: authenticating with 192.168.1.3 for IPC$ ** (gnome-cups-add:3109): WARNING **: authenticating with MESCAL for IPC$ ** (gnome-cups-add:3109): WARNING **: authenticating with TRINITA for IPC$ Selected ppd file = lsb/usr/foomatic-rip/openprinting-gs-builtin/HP/HP-LaserJet_6L-ljet4.ppd.gz ** (gnome-cups-add:3109): WARNING **: IPP request failed with status 1028 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 ***