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 465209 - crash in Open Folder: opening external drive
crash in Open Folder: opening external drive
Status: RESOLVED DUPLICATE of bug 485771
Product: nautilus
Classification: Core
Component: general
2.19.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-09 22:44 UTC by davisrkx
Modified: 2007-10-19 02:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description davisrkx 2007-08-09 22:44:32 UTC
Version: 2.19.5

What were you doing when the application crashed?
opening external drive


Distribution: Fedora release 7.90 (Rawhide)
Gnome Release: 2.19.5 2007-07-08 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-2925.14.fc8xen #1 SMP Tue Jul 24 15:30:41 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 94769152 vsize: 94769152 resident: 37314560 share: 23334912 rss: 37314560 rss_rlim: 4294967295
CPU usage: start_time: 1186697190 rtime: 289 utime: 256 stime: 33 cutime:0 cstime: 2 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208449264 (LWP 3396)]
(no debugging symbols found)
0x008b4402 in __kernel_vsyscall ()

Thread 1 (Thread -1208449264 (LWP 3396))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/i686/nosegneg/libc.so.6
  • #5 ??
  • #6 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #7 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #8 ??
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 g_cclosure_marshal_VOID__BOXED
    from /lib/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #14 ??
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #17 gtk_tree_model_row_deleted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 ??
  • #21 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #23 ??
    from /lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #26 nautilus_file_emit_changed
  • #27 nautilus_directory_emit_change_signals
  • #28 emit_change_signals_for_all_files
  • #29 ??
  • #30 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #31 Nautilus_MetafileMonitor_metafile_ready
  • #32 ??
  • #33 ??
  • #34 ??
    from /usr/lib/libeel-2.so.2
  • #35 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #36 ??
  • #37 ??
  • #38 ??
  • #39 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #40 ??
  • #41 ??
  • #42 ??
  • #43 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #44 ??
  • #45 ??
  • #46 ??
  • #47 g_thread_self
    from /lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall


----------- .xsession-errors (62 sec old) ---------------------
Package jakarta-taglibs-standard - 1.1.1-7jpp.1.i386 already installed and latest version
Package jakarta-oro - 2.0.8-3jpp.1.i386 already installed and latest version
Package regexp - 1.4-3jpp.1.fc7.i386 already installed and latest version
Package jakarta-commons-logging - 1.0.4-6jpp.2.i386 already installed and latest version
Package libgcj-src - 4.1.2-17.i386 already installed and latest version
Package xml-commons-apis - 1.3.03-0jpp.1.fc7.i386 already installed and latest version
Package jakarta-commons-modeler - 2.0-3jpp.1.fc7.i386 already installed and latest version
Package classpathx-mail - 1.1.1-4jpp.3.i386 already installed and latest version
Package jakarta-commons-validator - 1.1.4-5jpp.1.i386 already installed and latest version
Package ldapjdk - 4.17-1jpp.7.i386 already installed and latest version
Package xerces-j2 - 2.7.1-7jpp.2.i386 already installed and latest version
Package java_cup - 1:0.10-0.k.6jpp.1.i386 already installed and latest version
Package log4j - 1.2.14-3jpp.1.fc8.i386 already installed and latest version
Package xalan-j2 - 2.7.0-6jpp.1.i386 already installed and latest version
Package classpathx-jaf - 1.0-9jpp.1.i386 already installed and latest version
--------------------------------------------------
Comment 1 Susana 2007-08-10 14:37:49 UTC
Thanks for taking the time to report this bug.
Unfortunately, that 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 install some debugging packages [1], start the application as normal, and 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] debugging packages for nautilus, pango, gtk, glib, gnome-vfs, libgnome and libgnomeui. More details can be found here:
http://live.gnome.org/GettingTraces
Comment 2 André Klapper 2007-10-19 02:01:06 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 ***