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 538413 - crash in File Browser:
crash in File Browser:
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-15 09:07 UTC by sanvervio
Modified: 2008-06-15 10:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description sanvervio 2008-06-15 09:07:33 UTC 
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (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: SlicknesS
Icon Theme: black-white_2-Gloss

Memory status: size: 132673536 vsize: 132673536 resident: 65499136 share: 20783104 rss: 65499136 rss_rlim: 4294967295
CPU usage: start_time: 1213461718 rtime: 8728 utime: 8145 stime: 583 cutime:288 cstime: 52 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 0xb6b90720 (LWP 3510)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 200473

Thread 1 (Thread 0xb6b90720 (LWP 3510))

  • #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 istr_hash
    at nautilus-directory-async.c line 170
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (45435 sec old) ---------------------
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
(PySwitcher.py:3623): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed
(PySwitcher.py:3623): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
(PySwitcher.py:3623): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-15 10:07:44 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 ***