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 487859 - crash in Home Folder: file manager?で検索を実行した
crash in Home Folder: file manager?で検索を実行した
Status: RESOLVED DUPLICATE of bug 454799
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-18 11:00 UTC by nobby
Modified: 2007-10-19 01:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description nobby 2007-10-18 11:00:06 UTC 
What were you doing when the application crashed?
file manager?で検索を実行した


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: Clearlooks
Icon Theme: Fedora

Memory status: size: 486842368 vsize: 486842368 resident: 40968192 share: 22728704 rss: 40968192 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192703555 rtime: 841 utime: 741 stime: 100 cutime:0 cstime: 1 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 46912496348208 (LWP 11726)]
[New Thread 1105209680 (LWP 12142)]
(no debugging symbols found)
0x00000037398c82e6 in poll () from /lib64/libc.so.6

+ Trace 171109

Thread 2 (Thread 1105209680 (LWP 12142))

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






Comment 1


André Klapper





          2007-10-19 01:50:56 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 454799 ***