After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 577183 - crash in GNOME Commander:
crash in GNOME Commander:
Status: RESOLVED DUPLICATE of bug 539812
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: High critical
: 1.2.8
Assigned To: epiotr
epiotr
Depends on:
Blocks:
 
 
Reported: 2009-03-29 12:54 UTC by gino.latino58
Modified: 2009-03-29 13:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description gino.latino58 2009-03-29 12:54:32 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 ()

Thread 2 (Thread 0xb5dbfb90 (LWP 10687))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 <signal handler called>
  • #8 strlen
    from /lib/libc.so.6
  • #9 vfprintf
    from /lib/libc.so.6
  • #10 __vasprintf_chk
    from /lib/libc.so.6
  • #11 g_vasprintf
    from /lib/libglib-2.0.so.0
  • #12 g_strdup_printf
    from /lib/libglib-2.0.so.0
  • #13 delete_progress_callback
    at gnome-cmd-delete-dialog.cc line 91
  • #14 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #15 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #16 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #17 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #18 gnome_vfs_xfer_delete_list
    from /usr/lib/libgnomevfs-2.so.0
  • #19 perform_delete_operation
    at gnome-cmd-delete-dialog.cc line 187
  • #20 ??
    from /lib/libglib-2.0.so.0
  • #21 start_thread
    from /lib/libpthread.so.0
  • #22 clone
    from /lib/libc.so.6


----------- .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
--------------------------------------------------
Comment 1 Gianluca Borello 2009-03-29 13:05:48 UTC
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 ***