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 479101 - crash in Open Folder: try to estimate the size...
crash in Open Folder: try to estimate the size...
Status: RESOLVED DUPLICATE of bug 485771
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 486562 491597 494999 495088 495281 496840 497263 497907 498227 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-09-21 20:49 UTC by fede.pont
Modified: 2007-11-24 20:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description fede.pont 2007-09-21 20:49:48 UTC 
Version: 2.18.3

What were you doing when the application crashed?
try to estimate the size of a directory


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 401817600 vsize: 401817600 resident: 36106240 share: 17825792 rss: 36106240 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190380470 rtime: 3166 utime: 2756 stime: 410 cutime:1784 cstime: 280 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 0x2ae72056ebc0 (LWP 28668)]
(no debugging symbols found)
0x00002ae719af4c7f in waitpid () from /lib/libpthread.so.0

+ Trace 164521

Thread 1 (Thread 0x2ae72056ebc0 (LWP 28668))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib/libc.so.6
  • #4 ??
  • #5 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #6 ??
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
  • #17 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #18 ??
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 nautilus_file_emit_changed
  • #22 nautilus_directory_emit_change_signals
  • #23 nautilus_file_changed
  • #24 ??
  • #25 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #26 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #27 ??
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #29 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 main
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (201 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 palfrey 2007-10-15 12:42:41 UTC 
*** Bug 486562 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2007-10-19 01:56:56 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 485771 ***
Comment 3 palfrey 2007-10-30 11:37:23 UTC 
*** Bug 491597 has been marked as a duplicate of this bug. ***
Comment 4 palfrey 2007-11-08 18:09:34 UTC 
*** Bug 494999 has been marked as a duplicate of this bug. ***
Comment 5 palfrey 2007-11-09 15:29:05 UTC 
*** Bug 495088 has been marked as a duplicate of this bug. ***
Comment 6 palfrey 2007-11-09 15:31:30 UTC 
*** Bug 495281 has been marked as a duplicate of this bug. ***
Comment 7 palfrey 2007-11-15 15:00:08 UTC 
*** Bug 496840 has been marked as a duplicate of this bug. ***
Comment 8 palfrey 2007-11-16 16:09:12 UTC 
*** Bug 497263 has been marked as a duplicate of this bug. ***
Comment 9 Susana 2007-11-24 20:06:32 UTC 
*** Bug 498227 has been marked as a duplicate of this bug. ***
Comment 10 Susana 2007-11-24 20:19:56 UTC 
*** Bug 497907 has been marked as a duplicate of this bug. ***