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


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 485997

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:	2007-10-12 14:17 UTC by dezo
Modified:	2007-10-13 00:27 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description dezo 2007-10-12 14:17:10 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

System: Linux 2.6.22-2-486 #1 Thu Aug 30 23:45:36 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Simple
Icon Theme: Nuvola

Memory status: size: 68771840 vsize: 68771840 resident: 17965056 share: 13684736 rss: 17965056 rss_rlim: 4294967295
CPU usage: start_time: 1192198418 rtime: 101 utime: 92 stime: 9 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 0xb6bee9f0 (LWP 3682)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 169733

Thread 1 (Thread 0xb6bee9f0 (LWP 3682))

#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 _gdk_keymap_key_is_modifier
from /usr/lib/libgdk-x11-2.0.so.0
#7 ??
from /usr/lib/libgdk-x11-2.0.so.0
#8 ??
#9 ??
#10 ??
#11 ??
#0 __kernel_vsyscall



----------- .xsession-errors (150 sec old) ---------------------
This is not a supported use of GTK+. You must create a helper
program instead. For further details, see:
    http://www.gtk.org/setuid.html
Refusing to initialize GTK+.
/etc/gdm/Xsession: Beginning session setup...
can't lock memory: Cannot allocate memoryWARNING: not using secure memory for passwords
SESSION_MANAGER=local/ipetovsky:/tmp/.ICE-unix/3610
** (x-session-manager:3610): WARNING **: Host name lookup failure on localhost.
Window manager warning: Failed to read saved session file /home/ip/.metacity/sessions/default0.ms: Failed to open file '/home/ip/.metacity/sessions/default0.ms': No such file or directory
Initializing gnome-mount extension
seahorse nautilus module initialized
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
--------------------------------------------------

Comment 1 Christian Kirbach 2007-10-13 00:27:23 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 485997 ***