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 484715 - crash in Home Folder: I pressed "UP" button,th...
crash in Home Folder: I pressed "UP" button,th...
Status: RESOLVED DUPLICATE of bug 417962
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-08 13:15 UTC by leo_king11
Modified: 2007-10-08 20:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description leo_king11 2007-10-08 13:15:24 UTC 
What were you doing when the application crashed?
I pressed "UP" button,then it crashed.


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 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: aero-clone
Icon Theme: nuoveXT-aero

Memory status: size: 540897280 vsize: 540897280 resident: 68562944 share: 27222016 rss: 68562944 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191835288 rtime: 1895 utime: 1725 stime: 170 cutime:0 cstime: 9 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 46912496450608 (LWP 13095)]
[New Thread 1084229968 (LWP 18531)]
(no debugging symbols found)
0x000000359ca0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 168766

Thread 1 (Thread 46912496450608 (LWP 13095))

  • #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 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 gtk_tree_row_reference_free
    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 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 gtk_tree_view_set_cursor_on_cell
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #18 ??
  • #19 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #20 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #22 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #23 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors ---------------------
/home/leo/.themes/aero-clone/gtk-2.0/gtkrc:191: Overlay image options specified without filename
warning: .dynamic section for "/usr/lib64/libnautilus-extension.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib64/libeel-2.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib64/libpoppler-glib.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib64/libpoppler.so.1" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 Susana 2007-10-08 20:37:27 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 ***