SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My machine recently have Gnome SlackBuild upgraded to version 3.2. Before, it had GSB 2.x, over a Slackware 13.37 baseline.
When I try to log in selecting GNOME, I got an error which could be traced to seahorse-agent. The .xsession-error shows a broken dependency related to that executable.
Now, my surprise is to check seahorse-agent dependencies:
I double-checked the MANIFEST.bz2 file from Slackware 13.37 and from GSB 3.2 and found nothing like libcryptui.so. I haven't tried to search for libnotify.so, which is also missing. My question is if someone has seen this sort of thing before, and how to proceed? Of course I could check slackbuilds.org and other resources, but IMHO things are not supposed to work this way.
Some hours ago I realized that seahorse-agent could be some kind of "legacy" from older installations. And bingo, it was! There were a package, seahorse-agent, which is related to GSB 2.x and not to GSB 3.x, and was not removed from the machine.
The reason for not having it removed could be investigated as well - I ran slapt-get -c <conffile> --remove-obsolete --upgrade for upgrading GSB, which is supposed to remove older packages - but for now I'm satisfied that the problem reported in this thread is not happening anymore.
To be fair, I still can't see GNOME running, but it seems there is some other easy trick to be found.
For willysr, my sincere thanks for your reply. I suppose the dependency problem related to libnotify.so could be about their versions, but as seahorse-agent is not here anymore, this question has gone as well.
I'll turn this thread into "solved" very soon, I hope.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.