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 530542 - crash in Computer: I have made a copy of a ...
crash in Computer: I have made a copy of a ...
Status: RESOLVED DUPLICATE of bug 483884
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-29 12:00 UTC by sebastien.zola
Modified: 2008-04-30 08:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description sebastien.zola 2008-04-29 12:00:02 UTC 
Version: 2.20.0

What were you doing when the application crashed?
I have made a copy of a folder. When i simply browse this new folder the crash append.


Distribution: Slackware Slackware 12.0.0
Gnome Release: 2.20.0 2007-10-14 (GNOME.Org)
BugBuddy Version: 2.20.1

System: Linux 2.6.21.5-smp #4 SMP Mon Feb 11 17:13:56 CST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 80818176 vsize: 80818176 resident: 29827072 share: 15589376 rss: 29827072 rss_rlim: 4294967295
CPU usage: start_time: 1209470107 rtime: 716 utime: 602 stime: 114 cutime:14 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1228367664 (LWP 19230)]
0xb7085b01 in ?? () from /lib/libpthread.so.0

+ Trace 196434

Thread 1 (Thread -1228367664 (LWP 19230))

  • #0 ??
    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 run_bug_buddy
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 check_if_gdb
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 <signal handler called>
  • #8 nautilus_icon_factory_possibly_free_cached_icon
  • #9 g_hash_table_foreach_remove_or_steal
    from /usr/lib/libglib-2.0.so.0
  • #10 nautilus_icon_factory_sweep
  • #11 g_timeout_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 main
  • #0 ??
    from /lib/libpthread.so.0 


----------- .xsession-errors (53300 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
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-04-30 08:59:21 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 483884 ***