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 390106 - crash in Home Folder:
crash in Home Folder:
Status: RESOLVED DUPLICATE of bug 387738
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-27 19:29 UTC by fandonov
Modified: 2006-12-28 03:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description fandonov 2006-12-27 19:29:02 UTC 
What were you doing when the application crashed?



Distribution: Slackware Slackware 11.0.0
Gnome Release: 2.16.2 2006-11-22 (Dropline GNOME)
BugBuddy Version: 2.16.0

Memory status: size: 86372352 vsize: 0 resident: 86372352 share: 0 rss: 32096256 rss_rlim: 0
CPU usage: start_time: 1167168412 rtime: 0 utime: 4289 stime: 0 cutime:3841 cstime: 0 timeout: 448 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227196736 (LWP 2805)]
0xb76b8071 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 97345

Thread 1 (Thread -1227196736 (LWP 2805))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strrchr
    from /lib/tls/libc.so.6
  • #4 eel_filename_get_rename_region
    from /usr/lib/libeel-2.so.2
  • #5 fm_directory_view_update_menus
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0 






Comment 1


Martin Wehner





          2006-12-28 03:46:18 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 387738 ***