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.
Quote: And I tell you, you are Patrick, and on this rock-solid distro I will build my desktop,and Bill Gates of Windows shall not prevail against it. (Matthew 16:18, first draft)
kikinovak:
That, to me, is particularly profound, as the relevance of that particular verse is made more poignant by its being put in that context.
May there be a problem with the default values of fdisk in Slackware 14? As seen in this thread it created the first partition at sector 63, a behavior that should normally be obsolete and not occur in newer versions: http://www.linuxquestions.org/questi...ry-4175426683/
When I upgraded the netatalk package (netatalk-2.2.3-x86_64-3.txz) the installer won`t replace the old rc.atalk or create a new rc.atalk.new. It`s still the old rc.atalk script. I need to uninstall the netatalk package, manually delete the rc.atalk script and install netatalk again.
There's maybe a bug in the installer (or slackpkg?): when installing the latest -current, I chose all except "kdei" series. Now if "slackpkg install-new" is issued, the calligra-l10n-* packages in kdei are considered NEW, but not the kde-l10n-* ones.
if "slackpkg install-new" is issued, the calligra-l10n-* packages in kdei are considered NEW, but not the kde-l10n-* ones.
slackpkg considers as NEW only those: grep ": Added" ChangeLog.txt
i.e. added in new release packages, not "new for my installation". So, kde-l10n-* were in previous versions and they are not NEW in this sense.
nepomukservices[1864]: segfault at 0 ip (null) sp 00007fffbaff7968 error 14 in nepomukservicestub[400000+7000]
When I start Xfce
Code:
nm-applet[2160]: segfault at d ip 00007f6bcaede37e sp 00007fff5d68cab0 error 4 in libc-2.15.so[7f6bcae94000+1b5000]
I deleted all the old .configs in the home folder, it`s a clean install of -current. Those errors are old but I need to resurrect them, maybe they will be fixed.
I just updated my slackware-current mirror and installed the new packages.
When I open this page: http://javatester.org/version.html
I can see the correct Java version: "Java Version 1.7.0_07 from Oracle Corporation"
But when I open this page: http://www.java.com/en/download/help/testvm.xml
Firefox crashes completely as long as the directory "/usr/lib/java/jre/lib/fonts/fallback/" exists in my system, no matter if this directory is empty or not.
Not sure if the problem is in Firefox or in Java. I thought Firefox should not crash even if the Java plugin crashes. Am I mistaken?
Ok it's no only Java. Firefox-15.0.1 also crashes with other web pages sometimes. Java only crashes it most easily.
Since long long ago I've not experienced a plugin crashing the whole Firefox. Any hint why this happens to Firefox 15?
Now included in 14.0 and previous stable version as well since it's a security fix
Code:
a/patch-2.7-i486-1.txz: Upgraded.
This version of patch ignores destination filenames that are absolute or
that contain a component of "..", unless such a filename is provided as
an argument.
For more information, see:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4651
(* Security fix *)
Now included in 14.0 and previous stable version as well since it's a security fix
I actually barely agree that it's a security fix. To me, a patch is like a script -- you gotta read it, and can't just blindly trust it. If it patches the files that it says it will patch, how is that a security problem with patch?
But there's a CVE, and upstream feels it's a security issue, so I'll side with them. It is known to break some unusual uses of patch, though. They said they would accept patches to add an --unsafe option for the old behavior, but nobody has submitted any yet.
I have a bit of a problem that I have noticed. Around rc3 to rc4 rar unrar (not free) stopped working. It was working before, but now it does not. I get the following message:
/sbin/rar (or unrar): file not found
rar and unrar are present on the system, and it happens when I am root, even if I am in /sbin
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.