Bug 543786 – crash in GNOME Commander: I was deleting a folder ...

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 543786 - crash in GNOME Commander: I was deleting a folder ...


Summary:	crash in GNOME Commander: I was deleting a folder ...


Status:	RESOLVED DUPLICATE of bug 539812

Product:	gnome-commander
Classification:	Other
Component:	application
Version:	1.2.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	1.2.7
Assigned To:	epiotr
QA Contact:	epiotr

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-07-19 22:25 UTC by bertux66
Modified:	2008-07-19 22:40 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description bertux66 2008-07-19 22:25:39 UTC

Version: 1.2.6

What were you doing when the application crashed?
I was deleting a folder with only one file inside when GMC crasched.


Distribution: Fedora release 9 (Sulphur)
Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.10-86.fc9.i686 #1 SMP Mon Jul 7 20:46:03 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10499905
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: Fedora

Memory status: size: 69689344 vsize: 69689344 resident: 20746240 share: 13582336 rss: 20746240 rss_rlim: 4294967295
CPU usage: start_time: 1216505370 rtime: 336 utime: 303 stime: 33 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/local/bin/gnome-commander'

[Thread debugging using libthread_db enabled]
[New Thread 0xb7f71770 (LWP 14520)]
[New Thread 0xb64fcb90 (LWP 14638)]
0x00110416 in __kernel_vsyscall ()

+ Trace 203288

Thread 2 (Thread 0xb64fcb90 (LWP 14638))

#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 google_breakpad::ExceptionHandler::InternalWriteMinidump
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 google_breakpad::ExceptionHandler::HandleException
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#8 <signal handler called>
#9 strlen
from /lib/libc.so.6
#10 vfprintf
from /lib/libc.so.6
#11 __vasprintf_chk
from /lib/libc.so.6
#12 g_vasprintf
from /lib/libglib-2.0.so.0
#13 g_strdup_printf
from /lib/libglib-2.0.so.0
#14 delete_progress_callback
at gnome-cmd-delete-dialog.cc line 91
#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 ??
from /usr/lib/libgnomevfs-2.so.0
#19 ??
from /usr/lib/libgnomevfs-2.so.0
#20 gnome_vfs_xfer_delete_list
from /usr/lib/libgnomevfs-2.so.0
#21 perform_delete_operation
at gnome-cmd-delete-dialog.cc line 187
#22 ??
from /lib/libglib-2.0.so.0
#23 start_thread
from /lib/libpthread.so.0
#24 clone
from /lib/libc.so.6



----------- .xsession-errors ---------------------
GCJ PLUGIN: thread 0x88df558: GCJ_New: deleting input fifo: /home/conan/.gcjwebplugin/gcj-instance-3101-0-appletviewer-to-plugin
GCJ PLUGIN: thread 0x88df558: GCJ_New: deleted input fifo: /home/conan/.gcjwebplugin/gcj-instance-3101-0-appletviewer-to-plugin
GCJ PLUGIN: thread 0x88df558: plugin_data_destroy return
GCJ PLUGIN: thread 0x88df558: GCJ_Destroy return
GCJ PLUGIN: thread 0x88df558: NP_Shutdown
GCJ PLUGIN: thread 0x88df558: NP_Shutdown return
  PIPE: appletviewer read: shutdown
APPLETVIEWER: exiting appletviewer
CalDAV Eplugin starting up ...
** (evolution:13931): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:13931): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
Cannot access memory at address 0x84
Cannot access memory at address 0x84
--------------------------------------------------

Comment 1 epiotr 2008-07-19 22:40:01 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 ***