Bug 545622 – crash in Open Folder: I clicked the expand arr...

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 545622 - crash in Open Folder: I clicked the expand arr...


Summary:	crash in Open Folder: I clicked the expand arr...


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-07-31 01:24 UTC by ajohnson
Modified:	2008-07-31 09:31 UTC

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

Description ajohnson 2008-07-31 01:24:47 UTC

Version: 2.20.0

What were you doing when the application crashed?
I clicked the expand arrow on an SMB folder mounted with GVFS


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

System: Linux 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 83333120 vsize: 83333120 resident: 31342592 share: 15724544 rss: 31342592 rss_rlim: 4294967295
CPU usage: start_time: 1217462795 rtime: 2378 utime: 1001 stime: 1377 cutime:0 cstime: 1 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 0xb6ae6720 (LWP 2500)]
(no debugging symbols found)
0xb7f15424 in __kernel_vsyscall ()

+ Trace 204234

Thread 1 (Thread 0xb6ae6720 (LWP 2500))

#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 (315 sec old) ---------------------
#8 [0xb2615bfa]
#9 [0xb260fb3b]
#10 [0xb260fb3b]
#11 [0xb260d219]
#12 /usr/lib/jvm/java-1.5.0-sun-1.5.0.16/jre/lib/i386/client/libjvm.so [0xb77b52ec]
#13 /usr/lib/jvm/java-1.5.0-sun-1.5.0.16/jre/lib/i386/client/libjvm.so [0xb78c9f08]
#14 /usr/lib/jvm/java-1.5.0-sun-1.5.0.16/jre/lib/i386/client/libjvm.so [0xb77b511f]
#15 /usr/lib/jvm/java-1.5.0-sun-1.5.0.16/jre/lib/i386/client/libjvm.so(JVM_DoPrivileged+0x32d) [0xb7812bcd]
#16 /usr/lib/jvm/java-1.5.0-sun-1.5.0.16/jre/lib/i386/libjava.so(Java_java_security_AccessController_doPrivileged__Ljava_security_PrivilegedAction_2+0x3d) [0xb75ac30d]
#17 [0xb26154ab]
#18 [0xb260fa64]
#19 [0xb260d219]
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3400007 specified for 0x3400010 (License Ag).
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-07-31 09:31:24 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 ***