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 465158 - crash in Open Folder: Clicking the up-director...
crash in Open Folder: Clicking the up-director...
Status: RESOLVED DUPLICATE of bug 417962
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-09 19:17 UTC by steven.goss
Modified: 2007-08-10 14:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description steven.goss 2007-08-09 19:17:11 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Clicking the up-directory button.  I also just installed the NVidia CUDA driver a few minutes ago, but everything seems to be working ok since then, other than this crash.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 477274112 vsize: 477274112 resident: 47923200 share: 27181056 rss: 47923200 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186686068 rtime: 736 utime: 512 stime: 224 cutime:12 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/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 46912586785456 (LWP 31290)]
(no debugging symbols found)
0x00002aaaad71197f in waitpid () from /lib64/libpthread.so.0

+ Trace 154041

Thread 1 (Thread 46912586785456 (LWP 31290))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /lib64/libglib-2.0.so.0
  • #6 g_log
    from /lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /lib64/libglib-2.0.so.0
  • #8 ??
  • #9 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #10 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #11 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 gtk_tree_row_reference_free
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #14 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #16 gtk_tree_view_set_cursor_on_cell
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 ??
  • #18 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #19 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #21 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #22 main
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Susana





          2007-08-10 14:36:44 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 417962 ***