Bug 559689 – 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 559689 - 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-11-07 02:50 UTC by mrandisi
Modified:	2008-11-07 09:34 UTC

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

Description mrandisi 2008-11-07 02:50:54 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Thu Aug 28 12:00:54 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Shiki-Wise
Icon Theme: gTangish-2.0a1

Memory status: size: 106471424 vsize: 106471424 resident: 32645120 share: 15605760 rss: 32645120 rss_rlim: 4294967295
CPU usage: start_time: 1226026281 rtime: 651 utime: 629 stime: 22 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b52720 (LWP 5838)]
(no debugging symbols found)
0xb7f39424 in __kernel_vsyscall ()

+ Trace 209371

Thread 1 (Thread 0xb6b52720 (LWP 5838))

#0 __kernel_vsyscall
#1 waitpid
from /lib/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 ??
#7 ??
#8 ??
#9 ??
#10 ??
from /usr/lib/libglib-2.0.so.0
#11 ??
#12 ??
#13 ??
#14 ??
from /usr/lib/libglib-2.0.so.0
#15 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(bug-buddy:5831): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Initializing gnome-mount extension
seahorse nautilus module initialized
(nautilus:5838): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(nautilus:5838): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(scite:5910): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(scite:5910): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(bug-buddy:5959): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(bug-buddy:5959): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-11-07 09:34:50 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 ***