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.
-Current working good here except for thunar opened with “kdesu thunar” from mortal user account doesn’t have trash or network in KDE or XFCE.
If I log in to KDE or XFCE root session then everything works.
I Googled it and found several bug reports on thunar so I don't think it's a Slack problem.
However I'm very happy to now be able to access my samba servers via thunar from user accounts.
Things just keep getting better and better.
Thanks Slack crew!
Thanks, Pat and the entire team for all the hard work to reach RC1. This is a great set of updates and I can't wait for the release of 14.0!
Me neither. I'm ordering a virgin laptop for my university studies (READ: It has not had the cold,dead hand of Bill G. upon it), and it would be a great match for the release of Slackware 14.0.
I get segmentation fault when I try to run slapt-get and clementine. Messages in dmesg:
Code:
[40340.879702] clementine[14422]: segfault at 0 ip 00007f62320875a6 sp 00007fff616c1088 error 4 in libc-2.15.so[7f6232002000+1b3000]
[40420.097463] slapt-get[14466]: segfault at 0 ip 00007fe0c02745a6 sp 00007fffc0f70258 error 4 in libc-2.15.so[7fe0c01ef000+1b3000]
I get segmentation fault when I try to run slapt-get
you have to rebuild slapt-get yourself from source: you will need also this patch from its git repository.
after patching, do a "make pkg" to build an installable/removable package.
I though that openjdk would make its way in Slackware 14... It seems that I was wrong.
No worries though, as we can either build a package for the Oracle jdk or jre with the slackbuilds provided in /extre/source or use the openjdk packages or SlackBuilds provided by AlienBOB.
So far, so good, thanks to PV and the team.
Last edited by Didier Spaier; 08-10-2012 at 03:34 PM.
Is there any reason of having seperate seamonkey-solibs now that mozilla-nss, which includes nspr, was added?
IMO there isnt but someone else might have better insight than me.
edit: seperate js was added as well.
From the seamonkey-solibs slack-desc:
Code:
This package contains a subset of the shared libraries from Seamonkey to provide runtime support for programs that require nss, nspr, and js.
all of which are part of Slackware now.
edit2: that also means seamonkey doesnt need to mess with /etc/ld.so.conf anymore.
There's a small bug in Slackware64's version of yptools. Utilities like 'ypinit' seem to look for their counterparts in '/usr/lib' and not in '/usr/lib64', which produces a series of 'command not found' errors.
It's easy to fix this bug with a quick & dirty workaround like this:
Was this intentional, I always though that aaa_... packages should be upgrade, installed first first and the reason they are start with aaa_.
If you're already up-to-date with current and just applying the latest batch of updates that Pat has provided then there's usually nothing to worry about. If you're applying several batches at once because you've fallen behind, then order might be an issue. aaa_elflibs is the main one to watch out for as if you do it in the wrong order you,might actually downgrade some libraries. aaa_base is just a bunch of empty directories so there's not much scope for damage.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.