Bug 140317 (IT_35337) - Possible crash on nautilus startup
Summary: Possible crash on nautilus startup
Alias: IT_35337
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: gnome-vfs2   
(Show other bugs)
Version: 3.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: John (J5) Palmieri
QA Contact:
: 146197 (view as bug list)
Depends On:
Blocks: 136201 132991
TreeView+ depends on / blocked
Reported: 2004-11-22 10:26 UTC by Bastien Nocera
Modified: 2013-03-13 04:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-19 13:45:05 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:148 normal SHIPPED_LIVE gnome-vfs2 bug fix update 2005-05-19 04:00:00 UTC

Description Bastien Nocera 2004-11-22 10:26:57 UTC
Every now and then, nautilus would crash on startup:
#3  <signal handler called>
No symbol table info available.
#4  0xf56c2870 in FAMClose () from /usr/lib/libfam.so.0
No symbol table info available.
#5  0xf56c29f5 in FAMMonitorDirectory () from /usr/lib/libfam.so.0
No symbol table info available.
#6  0xf570e7d7 in ?? () from /usr/lib/gnome-vfs-2.0/modules/libfile.so
No symbol table info available.

This is the same as GNOME upstream bug 111147

Those 3 patches should help (need to be applied in that order):

Comment 1 Bastien Nocera 2005-01-26 10:50:13 UTC
*** Bug 146197 has been marked as a duplicate of this bug. ***

Comment 2 John (J5) Palmieri 2005-02-10 00:26:32 UTC
Patched and building as errata

Comment 3 John (J5) Palmieri 2005-02-10 01:26:08 UTC
Errata submitted

Comment 4 Tim Powers 2005-05-19 13:45:05 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.