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


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 480179

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.22.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-11 20:59 UTC by scheisse
Modified:	2008-06-11 21:46 UTC

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

Description scheisse 2008-06-11 20:59:35 UTC

Version: 2.22.3

What were you doing when the application crashed?



Distribution: Ubuntu 8.04.1 (hardy)
Gnome Release: 2.22.2 2008-06-03 (Ubuntu)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-19-generic #1 SMP Wed Jun 4 16:35:01 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Human

Memory status: size: 89784320 vsize: 89784320 resident: 35037184 share: 20332544 rss: 35037184 rss_rlim: 4294967295
CPU usage: start_time: 1213215421 rtime: 1216 utime: 934 stime: 282 cutime:4 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6b24720 (LWP 23985)]
0xb7f65410 in __kernel_vsyscall ()

+ Trace 200185

Thread 1 (Thread 0xb6b24720 (LWP 23985))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 gconf_client_remove_dir
from /usr/lib/libgconf-2.so.4
#7 ??
from /usr/lib/nautilus/extensions-2.0/libnautilus-actions.so
#8 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#9 ??
from /usr/lib/nautilus/extensions-2.0/libnautilus-actions.so
#10 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#11 free_module_objects
at nautilus-module.c line 219
#12 eel_debug_shut_down
from /usr/lib/libeel-2.so.2
#13 main
at nautilus-main.c line 578
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** (nautilus:22135): WARNING **: Unable to add monitor: DBus error org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 127
seahorse nautilus module initialized
Initializing nautilus-share extension
** (nautilus:22326): WARNING **: Unable to add monitor: DBus error org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 127
Gtk-WARNING **: Failed to load module "libgnomebreakpad.so": libgnomebreakpad.so: cannot open shared object file: No such file or directory
seahorse nautilus module initialized
Initializing nautilus-share extension
** (nautilus:23985): WARNING **: Unable to add monitor: DBus error org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 127
seahorse nautilus module shutdown
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------

Comment 1 A. Walton 2008-06-11 21:46:19 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 480179 ***