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 489205 - crash in Open Folder: Changing up one director...
crash in Open Folder: Changing up one director...
Status: RESOLVED DUPLICATE of bug 356672
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-22 23:15 UTC by causticfluids
Modified: 2007-10-23 13:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description causticfluids 2007-10-22 23:15:59 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Changing up one directory. (cd ..)


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 110227456 vsize: 110227456 resident: 48455680 share: 30703616 rss: 48455680 rss_rlim: 4294967295
CPU usage: start_time: 1193079057 rtime: 2343 utime: 2005 stime: 338 cutime:10 cstime: 3 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 -1208240416 (LWP 3399)]
(no debugging symbols found)
0x00110402 in ?? () from /lib/libcrypto.so.6

+ Trace 172076

Thread 1 (Thread -1208240416 (LWP 3399))

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


----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libpango-1.0.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libdbus-glib-1.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib/libssl.so.6" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib/libcrypto.so.6" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib/libselinux.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Cosimo Cecchi 2007-10-23 13:49:20 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 356672 ***