libgnome-keyring.so.0: ... No such file ...
H. Mark Little
machines, and now the gnome-* programs all fail with the message:
error while loading shared libraries: libgnome-keyring.so.0: cannot open shared object file: No such file or directory
I suspect the May 7 submission of pretty much all new gnome stuff. I haven't
yet gone digging to see what the cause/solution to this trouble might be, but
thought someone here *might* have already tackled it and could save me some
time by sharing.
Has anyone else seen this problem, and if anyone has fixed it, how?
Thanks,
--
Mark
Mads Jensen
H. Mark Little wrote:
> Has anyone else seen this problem, and if anyone has fixed it, how?
"gnome-keyring" should do the trick.
Regarding installation of gnome, then I'm stuck on a warning saying that
I miss libXinerama.so.0, and before that it was some other library file,
so my question is: does anyone know of a "slapt-get" installation
script, that will install all the required libraries ?
thanks,
Mads
--
Mads Jensen - http://www.ddfr.dk
I have not got a suspicious email!
A: Top answers
Q: What's the most annoying thing on UseNet ?
H. Mark Little
> Hi
>
> H. Mark Little wrote:
> > Has anyone else seen this problem, and if anyone has fixed it, how?
> "gnome-keyring" should do the trick.
>
> Regarding installation of gnome, then I'm stuck on a warning saying that
> I miss libXinerama.so.0, and before that it was some other library file,
> so my question is: does anyone know of a "slapt-get" installation
> script, that will install all the required libraries ?
I have been using "swaret", which is in the "extra" area of slackware-current.
This is *meant* to be able to automatically check for and resolve dependencies,
but for some reason, despite the configuration clearly saying to do so, it is
no longer working for me. The solution, in my case, was to run "swaret --dep"
I highly recommend to anyone running slackware-current and trying to keep it
up-to-date with the latest that Patrick puts in the repository to look into
swaret. The confugration isn't *too* complex, and once you are done editing
the config file, it becomes as simple as running:
% swaret --update
% swaret --upgrade
any time you want to bring a system up to the latest-and-greatest. (in my case,
I need to add a third step of "swaret --dep", but that *ought* to be automatic,
if you get the config right).
Enjoy,
--
Mark
PianoMan
> I have been using "swaret", which is in the "extra" area of slackware-current.
> This is *meant* to be able to automatically check for and resolve dependencies,
> but for some reason, despite the configuration clearly saying to do so, it is
> no longer working for me.
I installed a new system with Slack 9.1 CDs early this week and
everything worked fine. Then I grabbed swaret and tried to update
everything to slackware-current. Couldn't get the new Alsa to work, and
the new GNOME also seems to be majorly broken on my machine, bc only
very few icons and graphics-related stuff is displayed (for example
gThumb displays no images). I'm assuming I'm missing some deps, although
I did run Swaret with dep resolution enabled (it said it resolved some
deps, but it doesn't seem to resolve all of them).
I have had similar problems with Swaret on one occasion in the past, so
either I have it misconfigured (although it is not apparent to me how)
or this tool is not-so-hot. It has always worked fine for getting
security updates and patches within the version installed from CD.
I am currently in the process of letting Garnome compile the new GNOME
from source and we'll see how that works.
PM
Scott Cole
I think both writers should compare the changelogs for the new gnome 2.6
with what swaret did. There were several new files that swaret was
unlikely to install. There were also several files to remove that it
is even more unlikely that swaret would handle.
--
Only trust pipe smoking penguins.