View Full Version : Nautilus won't run
etrigan63
12th June 2004, 05:25 PM
Just installed a fresh copy of FC2 AMD64 (DVD) and I have two main problems:
[list=1]
Nautilus won't run on the system. It just bombs out with an error message and never loads.
When I try to seup my multihead display (QuadroFX 2000 + 2 LCD's), X won't run saying the "entity already exists" and I have to rollback the xorg.conf file.
[/list=1]
Any clues?
Jman
13th June 2004, 03:50 AM
Which error message? You can also run nautilus in a terminal (Main Menu > System Tools > Terminal) to get the error output.
etrigan63
16th June 2004, 05:48 PM
No error message. It just pops up the dialog box saying that nautilus couldn't start and do I want to report it to the developers.
perotin101
17th June 2004, 05:08 AM
There's a fix for problem here:
http://bugzilla.gnome.org/show_bug.cgi?id=138986
Just do the following (as root):
- download the patch attached to the bug report
- copy the patch file to /usr/src/redhat/SOURCES
- Install the source package ORBit2-2.10.0-2.src.rpm
- cd /usr/src/redhat/SOURCES
- tar -xvjf ORBit2-2.10.0.tar.bz2
- patch -p0 <ORBit2-2.10.0.1-cbl-nautilus-crasher-fix.patch
- tar -cvjf ORBit2-2.10.0.tar.bz2 ORBit2-2.10.0
- cd ../SPECS
- rpmbuild -bb ORBit2.spec
- rpm -Uvh --force ../RPMS/x86_64/ORBit2-2.10.0-2.x86_64.rpm
- now restart nautilus... no more crashes :-)
lightismagic
18th June 2004, 07:49 AM
Itried this but rpmbuild stopped with this error:
/usr/lib/libpopt.so: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[3]: *** [orbit-idl-2] Error 1
make[3]: Leaving directory `/usr/src/redhat/BUILD/ORBit2-2.10.0/src/idl-compiler'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/redhat/BUILD/ORBit2-2.10.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/redhat/BUILD/ORBit2-2.10.0'
make: *** [all] Error 2
Fehler: Bad exit status from /var/tmp/rpm-tmp.10017 (%build)
I'm not really a linux expert so a little help would be nice...!
Thank you
lightismagic
perotin101
18th June 2004, 09:24 AM
Do this in your shell just before running the rpmbuild command:
export LIBRARY_PATH=/usr/lib64
I forgot that I had to do this. Sorry. For some reason, it doesn't look in /usr/lib64 for libpopt. This environment setting ensures that it gets picked up.
lightismagic
18th June 2004, 11:33 AM
Thanks a lot! Nautilus is starting up now.
regards
lightismagic
ReeprFlame
22nd June 2004, 12:03 PM
definatly works wonders
Potato
28th June 2004, 07:23 PM
I got the following error:
>>>>>>>>>>
[root@206-97-63-237 SOURCES]# patch -p0 <nautilus-crasher-fix.patch
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -Naur --exclude=CVS ORBit2/src/orb/orb-core/allocators.c ORBit2.patched/src/orb/orb-core/allocators.c
|--- ORBit2/src/orb/orb-core/allocators.c 2003-07-07 09:11:31.000000000 -0400
|+++ ORBit2.patched/src/orb/orb-core/allocators.c 2004-06-17 13:13:07.563883105 -0400
--------------------------
File to patch:
>>>>>>>
Sorry, I am new to patches and don't know what is going wrong. I named the (patch nautilus-crasher-fix.patch) and followed the instructions given by Perotin101.
Potato
30th June 2004, 01:35 PM
Figured it out.
The file it was looking for was ORBit2/src/... but mine was named ORBit2-2.10.0/src/... I just told it the exact files to patch and it seemed to work. I'm sure there is a better way, but that worked. Otherwise everything worked great.
GandalfX
2nd July 2004, 11:21 AM
I realize this is pretty simple for most but I have been unable to download the patch referred to in these posts, and am assuming that the scripting/commands can be run in Terminal?
SmyTTor
4th July 2004, 06:15 AM
Just right click and save the following url as whatever you want to name the patch.
http://bugzilla.gnome.org/attachment.cgi?id=28806&action=view
cornedbeef
4th July 2004, 09:47 AM
Sorry, I am really new to all this--
I was wondering if someone could post exact (detailed) instructions on how to fix this problem. Like what file type to save the patch as... and all the steps to fix it. I just barely started using linux.
Thanks a bunch in advance. :eek:
GandalfX
5th July 2004, 02:01 AM
As I thought; simple enough if ur used to Linux, just a little beyond my very limited experience, as yet. Thanks again.
Gandy
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.