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 456940 - crash in Home Folder:
crash in Home Folder:
Status: RESOLVED DUPLICATE of bug 456131
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-14 20:44 UTC by duffy
Modified: 2007-07-25 13:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description duffy 2007-07-14 20:44:24 UTC
What were you doing when the application 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.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Neu

Memory status: size: 513822720 vsize: 513822720 resident: 67248128 share: 24866816 rss: 67248128 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184403099 rtime: 6310 utime: 5382 stime: 928 cutime:2895 cstime: 269 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 46912496397360 (LWP 3341)]
[New Thread 1136679248 (LWP 14052)]
(no debugging symbols found)
0x0000003c19424530 in g_type_check_instance_is_a ()
   from /lib64/libgobject-2.0.so.0

Thread 2 (Thread 1136679248 (LWP 14052))

  • #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 strstr
    from /lib64/libc.so.6
  • #4 ??
  • #5 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #7 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #8 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #9 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #10 gnome_vfs_directory_visit_uri
    from /usr/lib64/libgnomevfs-2.so.0
  • #11 ??
  • #12 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #13 start_thread
    from /lib64/libpthread.so.0
  • #14 clone
    from /lib64/libc.so.6


----------- .xsession-errors (42751 sec old) ---------------------
bad image index
(rhythmbox:3350): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
bad image index
(rhythmbox:3350): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
bad image index
(rhythmbox:3350): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
bad image index
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-07-25 13:41:01 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 456131 ***