From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040217 Description of problem: Nautilus crashes upon action (i.e. trying to open the home folder window). To crash dialog is provided. Running nautilus from the commandline produces this error: nautilus: relocation error: nautilus: undefined symbol: nautilus_get_uri_shortname_for_display Version-Release number of selected component (if applicable): nautilus-2.5.8-1 How reproducible: Always Steps to Reproduce: 1.Run GNOME desktop 2.nautilus attomatically starts 3.use nautilus Actual Results: nautilus crashed when I tried to use it. Expected Results: nautilus would not crash when accessed. Additional info: All components are up to date with fedora-devlopment (02/25/2004).
Oops, "To crash dialog is provided." should be "No crash dialog is provided." (i.e. bug-buddy).
Very strange. Its as if you have an older version of libnautilus-private. Are you sure you fully logged out and got rid of all running versions before trying?
Yes. I downgraded yesterday night, redownloaded this morning, logged out, logged in as root and reinstalled from the terminal, rebooted (to load the newest kernel) and got the same error when I restarted. I can try recompiling nautilus myself to see if it is a problem unique to my system.
What does "ldd nautilus" output?
Created attachment 98246 [details] results of ldd /usr/bin/nautilus The results of ldd /usr/bin/nautilus are attached.
Strange. nautilus_get_uri_shortname_for_display is surely in /usr/lib/libnautilus-private.so.2, and your nautilus is using that. I have no idea why its claiming its not there, but nobody but you is seeing this.
Is this still happeneing with the latest version of nautilus?
Yes, I am still have crashes when I try to open a nautilus window. After the crash trying to start nautilus from the command line still produces the same error. nautilus-2.5.7-1 works flawlessly though. If the problem is only on my system, then the bug should be closed. A clean install using fc2-test2 when it is released should fix whatever is causing the problem.
I have found the source of the problem. When the new version of nautilus was install the symlinks were being linked to an older prelinked version of the various nautilus libraries (specifically libnautilus-private.so.2.0.0.#prelink#.AhuPix from Feb 13). So this is either notabug or or problem with prelink not allowing newer libraries to be used after an upgrade. I have been getting several errors due to improperly prelinked files lately. However, a freshly installed system will presumably not have these problems.
I dunno if this is a prelink problem or if nautilus is doing something wrong. Reassigning to prelink.
The presence of file like: libnautilus-private.so.2.0.0.#prelink#.AhuPix means either that prelink process has been killed or the box powered down while prelinking was in progress (in whcih case just remove the file in question, rerun ldconfig and you should be all set), or it could mean that prelink crashed while processing that library (but in that case if it has been from the cron job you should have received a mail about it). If the latter is true, I need more details so that I can reproduce it myself (particularly the library on which it crashed, all its dependencies and prelink command line options and its version).
I do not think that that the problem was/is caused by one single library, but that prelink was aborted at some point a few months ago and the problem propagated out of control until I noticed. It would be nice if there was a way for prelink to clean up previously aborted sessions. As my system is now a mess a desperately in need a a fresh install.