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 577177 - crash in GNOME Commander: firefox
crash in GNOME Commander: firefox
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 11:06 UTC by gino.latino58
Modified: 2009-03-29 11:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description gino.latino58 2009-03-29 11:06:27 UTC
Version: 1.2.7

What were you doing when the application crashed?
firefox


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: 68050944 vsize: 68050944 resident: 22237184 share: 15228928 rss: 22237184 rss_rlim: 18446744073709551615
CPU usage: start_time: 1238324419 rtime: 584 utime: 499 stime: 85 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 0xb7f12770 (LWP 10437)]
[New Thread 0xb6791b90 (LWP 10447)]
0x00d24416 in __kernel_vsyscall ()

Thread 2 (Thread 0xb6791b90 (LWP 10447))

  • #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 ---------------------
Avviso del window manager: Received a _NET_WM_MOVERESIZE message for 0x1803c88 (PEN 8G); these messages lack timestamps and therefore suck.
(gsf-office-thumbnailer:10289): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
error: The metadata does not have a thumbnail property
error: The metadata does not have a thumbnail property
error: The metadata does not have a thumbnail property
error: The metadata does not have a thumbnail property
Could not open /dev/em8300-0 for writing: No such file or directory
Width: 1280, Height: 1024, Depth: 24
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
--------------------------------------------------
Comment 1 Gianluca Borello 2009-03-29 11:13:15 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 ***