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 512789 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 480179
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-29 13:10 UTC by Christian Holm Christensen
Modified: 2008-01-29 18:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Christian Holm Christensen 2008-01-29 13:10:37 UTC 
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: LiNsta2
Icon Theme: glass-icons

Memory status: size: 73158656 vsize: 73158656 resident: 21196800 share: 14422016 rss: 21196800 rss_rlim: 4294967295
CPU usage: start_time: 1201612259 rtime: 152 utime: 136 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b9f6c0 (LWP 32114)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 187195

Thread 1 (Thread 0xb6b9f6c0 (LWP 32114))

  • #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 gconf_client_remove_dir
    from /usr/lib/libgconf-2.so.4
  • #7 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #8 ??
  • #9 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #10 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
<gtk.gdk.Pixbuf object at 0xb6f717d4 (GdkPixbuf at 0x838d338)>
<gtk.gdk.Pixbuf object at 0xb6f717d4 (GdkPixbuf at 0x82cdd18)>
<gtk.gdk.Pixbuf object at 0xb6f717d4 (GdkPixbuf at 0x82cdd18)>
<gtk.gdk.Pixbuf object at 0xb6f717d4 (GdkPixbuf at 0x838d338)>
<gtk.gdk.Pixbuf object at 0xb6f717d4 (GdkPixbuf at 0x82cdd50)>
<gtk.
(PySwitcher.py:10288): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed
(PySwitcher.py:10288): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed
(PySwitcher.py:10288): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed
(PySwitcher.py:10288): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed
(PySwitcher.py:10288): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-29 18:21:02 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 480179 ***