Bug 537848 – crash in Open Folder: i tried to open folder o...

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 537848 - crash in Open Folder: i tried to open folder o...


Summary:	crash in Open Folder: i tried to open folder o...


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-11 19:33 UTC by sashko_g
Modified:	2008-06-11 20:43 UTC

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

Description sashko_g 2008-06-11 19:33:32 UTC

Version: 2.20.0

What were you doing when the application crashed?
i tried to open folder on other computer in network.


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (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: 70975488 vsize: 70975488 resident: 23040000 share: 14999552 rss: 23040000 rss_rlim: 4294967295
CPU usage: start_time: 1213212129 rtime: 354 utime: 335 stime: 19 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b7d720 (LWP 2891)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 200172

Thread 1 (Thread 0xb6b7d720 (LWP 2891))

#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 (15 sec old) ---------------------
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2800172 specified for 0x280017e (Remote Des).
Color depth: 24
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x58 specified for 0x28001e6 (Connection).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2800201 specified for 0x2800217 (Remote Des).
Color depth: 24
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x58 specified for 0x280026e (Connection).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2800282 specified for 0x280028e (Remote Des).
Color depth: 24
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x58 specified for 0x28002eb (Connection).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x28002ff specified for 0x280030b (Remote Des).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x58 specified for 0x280002a (Invitation).
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------

Comment 1 A. Walton 2008-06-11 20:43:57 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 522534 ***