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 442893 - crash in Open Folder: just starting
crash in Open Folder: just starting
Status: RESOLVED DUPLICATE of bug 343488
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-01 12:56 UTC by Roberto Pando
Modified: 2007-06-01 14:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Roberto Pando 2007-06-01 12:56:52 UTC 
What were you doing when the application crashed?
just starting


Distribution: CentOS release 4.5 (Final)
Gnome Release: 2.16.3 2007-03-03 (Joel Barrios D., para Alcance Libre, Inc.)
BugBuddy Version: 2.16.1

System: Linux 2.6.9-55.EL #1 Wed May 2 13:52:16 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 60802000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 66928640 vsize: 0 resident: 66928640 share: 0 rss: 24137728 rss_rlim: 0
CPU usage: start_time: 1180666979 rtime: 0 utime: 268 stime: 0 cutime:242 cstime: 0 timeout: 26 it_real_value: 0 frequency: 40

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208883520 (LWP 658)]
[New Thread -1211450464 (LWP 665)]
0x003547a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

+ Trace 137233

Thread 1 (Thread -1208883520 (LWP 658))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 870 






Comment 1


palfrey





          2007-06-01 14:18:32 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 343488 ***