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 405996 - crash in Computer: copying files from one d...
crash in Computer: copying files from one d...
Status: RESOLVED DUPLICATE of bug 363856
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-09 03:34 UTC by frexican
Modified: 2007-02-10 19:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description frexican 2007-02-09 03:34:14 UTC
What were you doing when the application crashed?
copying files from one drive to another


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 486498304 vsize: 486498304 resident: 24383488 share: 23363584 rss: 47747072 rss_rlim: 1793459200
CPU usage: start_time: 1170989390 rtime: 2088 utime: 1516 stime: 572 cutime:16 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47020137779840 (LWP 10138)]
[New Thread 1082132800 (LWP 11766)]
[New Thread 1099053376 (LWP 11765)]
(no debugging symbols found)
0x00002ac3b819ec5f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 47020137779840 (LWP 10138))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_unicode_canonical_ordering
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #4 g_utf8_collate_key
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #5 g_utf8_collate_key_for_filename
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #6 nautilus_file_get_uri
  • #7 nautilus_file_get_uri
  • #8 nautilus_file_get_parent_uri
  • #9 g_list_foreach
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #10 g_list_foreach
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #11 g_list_foreach
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #12 g_list_foreach
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #13 g_list_foreach
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #14 g_list_foreach
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #15 g_list_foreach
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #16 g_list_foreach
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #17 POA_Nautilus_MetafileMonitor__init
  • #18 fm_directory_view_bump_zoom_level
  • #19 fm_directory_view_bump_zoom_level
  • #20 g_source_get_current_time
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #21 g_main_context_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #22 g_main_context_prepare
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #23 g_main_loop_run
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #24 gtk_main
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #25 POA_Nautilus_MetafileMonitor__init
  • #26 __libc_start_main
    from /lib64/libc.so.6
  • #27 g_cclosure_marshal_VOID__ENUM
  • #28 ??
  • #29 ??
  • #0 waitpid
    from /lib64/libpthread.so.0

Comment 1 André Klapper 2007-02-10 13:39:19 UTC
Thanks for taking the time to report this bug.
Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash.

Could you please help fixing this by installing some debugging packages [1], start Nautilus as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] Please install the following debug packages provided by SuSE: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo.

More details can be found here: http://live.gnome.org/GettingTraces

SuSE provides a debuginfo package repository, that users can add to their installation sources, under http://download.opensuse.org/distribution/XXX/repo/debug/suse/ . 'XXX' is the version number of your SuSE release, for example '10.2'.
Comment 2 Marc-Andre Lureau 2007-02-10 19:01:48 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 363856 ***