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 468031 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 243160
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-18 20:13 UTC by anagathon
Modified: 2007-08-25 06:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description anagathon 2007-08-18 20:13:38 UTC 
What were you doing when the application crashed?



Distribution: Mandriva Linux release 2007.0 (Official) for i586
Gnome Release: 2.16.0 2006-09-04 (Mandriva)
BugBuddy Version: 2.16.0

Memory status: size: 22921216 vsize: 0 resident: 22921216 share: 0 rss: 7987200 rss_rlim: 0
CPU usage: start_time: 1187453627 rtime: 0 utime: 14 stime: 0 cutime:12 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227540800 (LWP 6042)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 156209

Thread 1 (Thread -1227540800 (LWP 6042))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 do_lookup_x
    at do-lookup.h line 72
  • #5 _dl_lookup_symbol_x
    at dl-lookup.c line 233 






Comment 1


Pascal Terjan





          2007-08-25 06:18:45 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 243160 ***