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 530700 - crash in Open Folder: I was browsing through n...
crash in Open Folder: I was browsing through n...
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-04-30 09:09 UTC by asilvestrov
Modified: 2008-04-30 09:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description asilvestrov 2008-04-30 09:09:27 UTC 
Version: 2.20.0

What were you doing when the application crashed?
I was browsing through network computers. Those are win computers and I'm using samba. It enters some folders normally, but fails to open others. It seems that those folders that fail to open have lots of contents and those that don't fail have not more than ten items.


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 Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 64061440 vsize: 64061440 resident: 25239552 share: 15532032 rss: 25239552 rss_rlim: 4294967295
CPU usage: start_time: 1209540779 rtime: 891 utime: 808 stime: 83 cutime:0 cstime: 1 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 0xb6bd9720 (LWP 3962)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 196513

Thread 1 (Thread 0xb6bd9720 (LWP 3962))

  • #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 (14 sec old) ---------------------
(eog:4434): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
(eog:4434): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
(eog:4434): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `pixbuf != NULL' failed
(eog:4434): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_has_alpha: assertion `pixbuf != NULL' failed
(eog:4434): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `pixbuf != NULL' failed
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00003 (Export Fil)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-04-30 09:26:07 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 ***