Slackware 14.0 RC4

Alien Bob · 09-14-2012, 08:46 AM

Quote:

Originally Posted by eeades

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

Eric

Sounds like a package may have been installed or upgraded which was not suited for your Slackware architecture (32-bit vs. 64-bit).

Eric

eeades · 09-14-2012, 10:36 AM

I am not sure what is going on, but it worked, then I updated, and it stopped working. I have do a re-install with current as of tuesday night, and it still does not work, either with the pre-compiled binaries from rarlabs, or one that I just did from slackbuilds.org. I am using amd_64 if that helps.

Eric

eeades · 09-14-2012, 10:38 AM

Quote:

Originally Posted by Alien Bob

Sounds like a package may have been installed or upgraded which was not suited for your Slackware architecture (32-bit vs. 64-bit).

Eric

Ok I will have to look at that. The odd thing is that I pulled down the latest packages from a local mirror Tuesday night, to do a fresh install, and I am still having this problem.

Eric

eeades · 09-14-2012, 10:50 AM

Now I feel stupid. I had a bunch of packages that I have built along the way, and I have not updated them. I only recently moved to 64 bit, and I did not think to update the packages at all. I have removed them and it works now. (That includes an old rar/unrar package that I created)

Thanks for the help!

Eric

dram · 09-15-2012, 01:58 AM

python -c "import PyKDE4"

failed with:

Code:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib64/python2.7/site-packages/PyKDE4/__init__.py", line 1, in <module>
    import sys,DLFCN
ImportError: No module named DLFCN

I'm running 64-current + multilib. Does anyone else has this problem?

dram · 09-15-2012, 02:20 AM

Quote:

Originally Posted by dram

python -c "import PyKDE4"

failed with:

Code:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib64/python2.7/site-packages/PyKDE4/__init__.py", line 1, in <module>
    import sys,DLFCN
ImportError: No module named DLFCN

I'm running 64-current + multilib. Does anyone else has this problem?

It's caused by virtualenv, not Slackware's fault.

kabamaru · 09-15-2012, 02:43 AM

May I suggest not specifying the absolute path to a specific image file in some *.desktop files? When you change the icon theme the 'old' icon doesn't change and stands out.

Example:

Firefox follows icon theme:

Code:

Icon=firefox

Thunderbird doesn't:

Code:

Icon=/usr/share/pixmaps/thunderbird.png

PS. RC4 runs great for me so far

elyk · 09-16-2012, 12:24 AM

On a fresh install, if I try to wget an HTTPS site I get an error:

Code:

$ wget https://www.google.com/
--2012-09-16 00:02:21--  https://www.google.com/
Resolving www.google.com (www.google.com)... 74.125.227.48, 74.125.227.52, 74.125.227.51, ...
Connecting to www.google.com (www.google.com)|74.125.227.48|:443... connected.
ERROR: cannot verify www.google.com's certificate, issued by ‘/C=ZA/O=Thawte Consulting (Pty) Ltd./CN=Thawte SGC CA’:
  Unable to locally verify the issuer's authority.
To connect to www.google.com insecurely, use `--no-check-certificate'.

lynx also complains:

Code:

SSL error:unable to get local issuer certificate-Continue? (y)

Turns out I have to run /usr/bin/c_rehash to generate symlinks in /etc/ssl/certs, and then they both work. I see that OpenSSL's doinst.sh should run c_rehash. Is there some reason why doinst.sh isn't creating them?

elyk · 09-16-2012, 01:02 AM

Quote:

Originally Posted by elyk

Turns out I have to run /usr/bin/c_rehash to generate symlinks in /etc/ssl/certs, and then they both work. I see that OpenSSL's doinst.sh should run c_rehash. Is there some reason why doinst.sh isn't creating them?

Hmm, maybe this already got fixed in ca-certificates-20120623-noarch-2. I'll have to try it.

Alien Bob · 09-16-2012, 04:19 AM

Strange. The c_rehash command is run by "/usr/sbin/update-ca-certificates" which is called by the doinst.sh script of the ca-certificates package.

Eric

xspartan · 09-16-2012, 09:09 AM

Doesn't the 32 bit version support Intel Pentium M CPU's anylonger?
cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 9
model name : Intel(R) Pentium(R) M processor 1500MHz
stepping : 5
cpu MHz : 600.000
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 tm pbe up bts est tm2
bogomips : 1196.25
clflush size : 64
cache_alignment : 64
address sizes : 32 bits physical, 32 bits virtual

TobiSGD · 09-16-2012, 11:36 AM

If you have a Pentium M with 400MHz frontside bus then your CPU does not support PAE, which is enabled by default in the smp kernel. You can use the non-smp kernel to start the system and then build a smp-kernel with PAE disabled.

aaazen · 09-16-2012, 04:59 PM

I found an expired certificate in the new ca-certificates-20120623-noarch-2 package using a weekly cron script based on code from Alien Bob:

http://alien.slackbook.org/blog/watc...-certificates/

The expired certificate is:

!!! SSL CERTIFICATE EXPIRY !!!
==============================
The following SSL certificates in /etc/ssl/certs are expired or
will expire within the next 31 days:
--Expiration Date------- --Certificate---------------------
Jan 14 16:29:17 2007 GMT /usr/share/ca-certificates/spi-inc.org/spi-ca-2003.crt

BlackRider · 09-16-2012, 05:07 PM

I don't know if it has been noticed, but just in case, I must post that there are known problems with the "eject" version in Slackware 14.0 RC4.

There is a discussion in this thread: https://www.linuxquestions.org/quest...297/page2.html

Woodsman has pointed that the Arch team has deployed a set of patches to solve the issue: https://bugs.archlinux.org/task/25405

kabamaru · 09-16-2012, 05:21 PM

It seems there is problem with tumbler and unmounting external drives that contain video files. Tumbler tries to create thumbnails through the gstreamer plugin but it fails, freezes (the files remain open), and you cannot eject the device. Thunar displays an error (attached png). If you kill tumblerd, or turn thumbnails off (through Thunar's options), the problem goes away.

This is an already filed bug.

The Ubuntu fellas have a patch for this (attached txt). I tested it and it works. I'm not saying this should be applied to Slackware, but I will use it if it doesn't as it solves my problem.