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 475898 - crash in Home Folder: Software updates, USB dr...
crash in Home Folder: Software updates, USB dr...
Status: RESOLVED DUPLICATE of bug 433983
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-11 15:58 UTC by soop
Modified: 2007-10-21 16:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description soop 2007-09-11 15:58:12 UTC 
What were you doing when the application crashed?
Software updates, USB drive, and I made klic "up one directory"


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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Mist

Memory status: size: 102027264 vsize: 102027264 resident: 43966464 share: 27455488 rss: 43966464 rss_rlim: 4294967295
CPU usage: start_time: 1189525656 rtime: 874 utime: 761 stime: 113 cutime:220 cstime: 18 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 -1208690976 (LWP 2645)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 162110

Thread 1 (Thread -1208690976 (LWP 2645))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #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 __kernel_vsyscall 


----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libgssapi_krb5.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libkrb5.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libk5crypto.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libkrb5support.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 André Klapper 2007-10-21 16:59:05 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 433983 ***