Cannot open shared object file errors preventing boot up

Graeme Nichols gnichols at tpg.com.au
Sun Aug 15 03:04:09 UTC 2004


On Thu, 2004-08-12 at 02:40, Rick Stevens wrote:

<snip>
> > Hello Rick, please see my reply to Bob. X started up OK today but there
> > is still the original problem similar to this one: 'error while loading
> > shared libraries: libqt-mt.so.3: cannot open shared object file: No such
> > file or directory'. Any clues? Doesn't appear to be a permission
> > problem, but what the problem is I have no idea. Sound familiar :-)
> 
> It runs OK as root but not as a mortal user?  That smacks of permissions
> problems.  The library should be in /usr/lib/qt-3.1/lib (may be a
> different version, but you get the idea).  Make sure that all files in
> that directory and the directory itself has at least world read/execute
> permissions:
> 
> 	# cd /usr/lib
> 	# chmod -R o+rw qt-3.1

No. Doesn't run as either root of my mortal self. I ran the chmod
command above just to make sure. The are several versions of qt on my
system, viz.

[graeme at barney lib]$ ls qt*
qt2:
bin  doc  include  lib
 
qt-2.3.1:
bin  doc  include  lib
 
qt-3.0.5:
bin  etc  lib  plugins
 
qt-3.3:
bin  etc      lib      phrasebooks  templates
doc  include  mkspecs  plugins      translations
[graeme at barney lib]$

I ran the chmod command on all of them. As you can see, lib-mt.so.3 is a
symbolic link to a later version.

[graeme at barney lib]$ ls -la libqt-mt.so.3
lrwxrwxrwx  1 root root 17 Jul 14 17:06 libqt-mt.so.3 ->
libqt-mt.so.3.3.2
[graeme at barney lib]$

The problem appears to be only associated with KDE applications, e.g.,
quanta, Korganizer, Kmail etc. and always the same library. I have
re-installed a heap of RPMs, including all the KDE related RPMs but
nothing seems to fix the problem.

Do you have any further ideas. I don't really want to re-install FC2 if
I can possibly avoid it. Also, can you recommend a simple backup utility
that can follow symlinks, hardlinks and make a COMPLETE backup of
particular directories. Flexbackup is almost useless, particularly as
the man page is in error and restoring files won't work for me. tar
fails because it complains of the backup being too large and bombs out.
Mirrordir wont follow hard links, although the idea is great. cp is OK
except it won't follow hard links either. Pumps out a lot of errors to
that effect, particularly in /usr.

TIA,

ps. sorry about the delay in getting back to you, but I haven't had a
lot of time and I've only just got the system back up enough to connect
to the internet.

--
----------------------------------------------------------------------
Kind regards, Graeme Nichols.
----------------------------------------------------------------------
QOTD: "She's about as smart as bait."
----------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/redhat-install-list/attachments/20040815/bb29b05d/attachment.sig>


More information about the Redhat-install-list mailing list