GNOME Bugzilla – Bug 532634
crash in File Browser:
Last modified: 2008-05-11 17:49:38 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-486 #1 Fri Apr 18 23:53:06 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Enabled GTK+ Theme: Industrial Icon Theme: Human Memory status: size: 122572800 vsize: 122572800 resident: 67321856 share: 17690624 rss: 67321856 rss_rlim: 4294967295 CPU usage: start_time: 1210487701 rtime: 3268 utime: 3088 stime: 180 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b59940 (LWP 3367)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 197460
Thread 1 (Thread 0xb6b59940 (LWP 3367))
----------- .xsession-errors (8 sec old) --------------------- gstplaybasebin.c(1663): gen_source_element (): /play: No URI handler for mms TotemEmbedded-Message: Viewer state: STOPPED TotemEmbedded-Message: totem_embedded_set_error: 'Per riprodurre questo filmato è necessario un plugin Sorgente protocollo MMS (Microsoft Media Server) che non è installato.' TotemEmbedded-Message: totem_embedded_set_error_logo called by browser plugin ** Message: totemGMPPlugin dtor [0xfb4c8d0] ** Message: totemPlugin dtor [0xfb4c5d0] ** Message: NP_Shutdown connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:3367): WARNING **: Non è stata trovata alcuna descrizione per il tipo MIME «x-directory/smb-share» (relativa al file «D»); avvisare cortesemente la mailing list di gnome-vfs. --------------------------------------------------
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 ***