Bug 537645 – crash in Open 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 537645 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 522534

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-06-10 18:22 UTC by barthezz
Modified:	2008-06-10 19:09 UTC

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

Description barthezz 2008-06-10 18:22:37 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 103440384 vsize: 103440384 resident: 28987392 share: 17321984 rss: 28987392 rss_rlim: 4294967295
CPU usage: start_time: 1213119938 rtime: 469 utime: 432 stime: 37 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6ab6940 (LWP 3644)]
[New Thread 0xb38a1b90 (LWP 3926)]
[New Thread 0xb5e64b90 (LWP 3899)]
[New Thread 0xb4e62b90 (LWP 3896)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 200055

Thread 1 (Thread 0xb6ab6940 (LWP 3644))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
#3 IA__g_spawn_command_line_sync
at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 istr_hash
at nautilus-directory-async.c line 170
#7 g_hash_table_insert_internal
at /build/buildd/glib2.0-2.16.3/glib/ghash.c line 118
#8 istr_set_insert
at nautilus-directory-async.c line 189
#9 dequeue_pending_idle_callback
at nautilus-directory-async.c line 848
#10 directory_load_callback
at nautilus-directory-async.c line 1035
#11 dispatch_job_callback
at gnome-vfs-job.c line 237
#12 g_idle_dispatch
at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 4087
#13 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2009
#14 g_main_context_iterate
at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2642
#15 IA__g_main_loop_run
at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2850
#16 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#17 main
at nautilus-main.c line 556
#18 __libc_start_main
from /lib/i686/cmov/libc.so.6
#19 _start
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
** (nautilus:3644): WARNING **: Hit unhandled case 31 (Operation cancelled) in fm_report_error_loading_directory
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: save-authentication!!!
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-06-10 19:09:37 UTC

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 ***