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 538069 - crash in Open Folder: browsing subdirectories ...
crash in Open Folder: browsing subdirectories ...
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-12 22:01 UTC by Chad Feller
Modified: 2008-06-13 08:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Chad Feller 2008-06-12 22:01:07 UTC 
Version: 2.20.0

What were you doing when the application crashed?
browsing subdirectories from cifs mounted partition from within nautilus


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 450904064 vsize: 450904064 resident: 31100928 share: 17526784 rss: 31100928 rss_rlim: 18446744073709551615
CPU usage: start_time: 1213198136 rtime: 1158 utime: 968 stime: 190 cutime:0 cstime: 1 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2ae2cacdc240 (LWP 25168)]
(no debugging symbols found)
0x00002ae2c41d2edf in waitpid () from /lib/libpthread.so.0

+ Trace 200278

Thread 1 (Thread 0x2ae2cacdc240 (LWP 25168))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
  • #13 __libc_start_main
    from /lib/libc.so.6
  • #14 ??
  • #15 ??
  • #16 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x8a00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
/dev/dsp: Device or resource busy
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
warning: .dynamic section for "/lib/libacl.so.1" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-13 08:50:10 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 ***