GNOME Bugzilla – Bug 577183
crash in GNOME Commander:
Last modified: 2009-03-29 13:05:48 UTC
Version: 1.2.7 What were you doing when the application crashed? Distribution: Fedora release 10 (Cambridge) Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc) BugBuddy Version: 2.24.2 System: Linux 2.6.27.19-170.2.35.fc10.i686 #1 SMP Mon Feb 23 13:21:22 EST 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 80715776 vsize: 80715776 resident: 22781952 share: 14184448 rss: 22781952 rss_rlim: 18446744073709551615 CPU usage: start_time: 1238330800 rtime: 1265 utime: 1133 stime: 132 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/gnome-commander/gnome-commander' [Thread debugging using libthread_db enabled] [New Thread 0xb80d2770 (LWP 10673)] [New Thread 0xb5dbfb90 (LWP 10687)] [New Thread 0xb6951b90 (LWP 10680)] 0x00db2416 in __kernel_vsyscall ()
+ Trace 213965
Thread 2 (Thread 0xb5dbfb90 (LWP 10687))
----------- .xsession-errors --------------------- Could not open /dev/em8300-0 for reading: No such file or directory Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x3c00020 non valido per 0x3c06f33 (Opzioni to). (gnome-commander:10437): libgnomevfs-CRITICAL **: gnome_vfs_uri_get_host_name: assertion `uri != NULL' failed Cannot access memory at address 0x84 Cannot access memory at address 0x84 Cannot access memory at address 0x84 Cannot access memory at address 0x84 *** NSPlugin Viewer *** /usr/lib/firefox-3.0.8/run-mozilla.sh: line 131: 9210 Segmentation fault "$prog" ${1+"$@"} ERROR: NPN_InvalidateRect() invoke: Connessione abbattuta dal corrispondente *** NSPlugin Viewer *** WARNING:(../src/npw-viewer.c:1291):invoke_NPN_InvalidateRect: assertion failed: (rpc_method_invoke_possible(g_rpc_connection)) (gnome-commander:10673): libgnomevfs-CRITICAL **: gnome_vfs_uri_get_host_name: assertion `uri != NULL' failed Cannot access memory at address 0x84 Cannot access memory at address 0x84 --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 539812 ***