Main menu:

Sponsoring

Please consider a small donation:

 

Also appreciated: support me by clicking the ads (costs nothing) :-)

 

Or you can donate bitcoin:

 

Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank

Fame

FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

Your feedback

Me

Do you have any questions with regard to my packages, SlackBuild scripts, other scripts, or my documentation? Or do you have a request to make? Please use this space to write down your ideas and I will try to answer. Other readers are of course also allowed to voice their thoughts about what you write.

Keep your posts on topic please. No flamewars, trolling, or other nastiness allowed. This is not meant to be a replacement for LinuxQuestions.org

If the blog refuses to accept your post, then perhaps you are affected by a bug in the SQLite plugin. Check if your post contains a string of text which is enclosed by the characters ( ). Is there a pipe symbol or a comma inside those round brackets? Try to remove those and re-post your comment.

Continue to my blog articles if you want.

Eric

Comments

Comment from aiden
Posted: July 31, 2012 at 18:25

Thanks for creating this space, and for being such a force for the Slackware community.

Comment from aiden
Posted: July 31, 2012 at 22:57

Okay, so the good news is that Handbrake 0.9.8 works perfectly. The bad news is it doesn’t contain any features, only bug fixes. And according to the devs, the current trunk won’t be released as the official build until next year – https://forum.handbrake.fr/viewtopic.php?f=12&t=24951. Is there any way I could get you to build the 4883svn nightly (https://trac.handbrake.fr/browser/trunk?rev=4883)?

Comment from cesarion76
Posted: August 1, 2012 at 03:53

hi, just noticed the handbreak package in “restricted_slackbuilds” is still version 0.9.5 in 32/64 versions.

Do I get all the features if I get the regular pkg from slackware.com server?

best regards

Comment from alienbob
Posted: August 1, 2012 at 11:07

O… I forgot that I had to place the packages in restricted_slackbuilds due to the lame and faac encoders… I will set that right tonight and update the repositories.

Actually, it is easy for you to build your own package from a SVN trunk checkout. I will stick to the official releases but you can grab the SlackBuild and edit it so that it has these two lines:

VERSION=${VERSION:-r4883}
RELREV=${RELREV:-””}

Which causes the script to checkout revision 4883 from trunk and build a package for that.

Eric

Comment from aiden
Posted: August 1, 2012 at 16:23

Thanks Bob. Unfortunately it’s not going to be that simple, because sourceforge.net only has the official releases. It looks like the only way to grab a nightly for a build is to use a subversion repository call, which is failing badly for me when I try it.

Comment from aiden
Posted: August 1, 2012 at 16:55

Hm… I reread your post, and understand my confusion now. The current .build file contains no references to SVN, so it defaulted to sourceforge.

Comment from aiden
Posted: August 2, 2012 at 00:42

Well, after a lengthy process of finding all the dependencies necessary for a compile in unRAID, I have a working executable. I’m not 100% of the best way to make it into a package, though. I ran “make install” in the build directory and that has me going for now, but is there a simple way to make the .build file?

Comment from cesarion76
Posted: August 2, 2012 at 03:57

Hi Eric, slackpkg won’t blacklist last multilib update

Mon Jul 30 20:12:24 UTC 2012
current/gcc-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt.
current/gcc-g++-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt.
current/gcc-gfortran-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt. Fixed the
64-bit libgfortranbegin.a library which got overwritten by the 32-bit
version. Thanks to hiptobecubic for reporting this.
current/gcc-gnat-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt.
current/gcc-go-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt.
current/gcc-java-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt.
current/gcc-objc-4.7.1_multilib-x86_64-1fix1_alien.txz: Rebuilt.

I had to add:

“[0-9]+fix1_alien” to /etc/slackpkg/blacklist so they don’t get replace by slackware’s native pkg

best regards

Comment from alienbob
Posted: August 2, 2012 at 08:59

Hi cesarion76

I think I may have to rename the packages so that they end on “fix1_1alien” instead of “1fix1_alien” because having to add yet another line to the blacklist file of slackpkg is not an elegant solution. Thanks for mentioning it.

Cheers, Eric

Comment from alienbob
Posted: August 2, 2012 at 09:01

aiden, I am a bit confused as to what you are trying. A “.build” file? Could you not just use the hints I gave 6 comments back and run the edited handbrake.SlackBuild with changed variable definitions? That will checkout a trunk snapshot and build that for you.

Eric

Comment from aiden
Posted: August 2, 2012 at 16:44

Bob, yes I tried that first, of course. But I got an “invalid scheme” error. So instead I went down the road of manually checking it out and compiling it locally based on Handbrake’s wiki instructions. What I would like to do is make a package out of that binary so I can post it on the unRAID forums for other users to download. I appreciate your patience, because I’m clearly a novice at these things.

Comment from alienbob
Posted: August 2, 2012 at 21:14

I never saw an “invalid scheme” error. Perhaps if you can post a full log of your failed compilation on http://pastebon.com/ then I could have a look at it.

Eric

Comment from gbdj
Posted: August 21, 2012 at 17:50

Hi. Are there any difficulties in building recent qemu-kvm-1.1.1 for slack 13.1 or 0.14 packages just left from old SlackBuild version?
Thank you

Comment from Colint
Posted: September 10, 2012 at 07:43

Thanks Eric for the kde 4.9.1, it has helped me out a lot.

Comment from Krisz
Posted: September 27, 2012 at 09:53

Hello Erik!

Could you please create a package for virt-manager? Or create a howto how we can install it? I found some howtos on the net for slackware and virt-manager, but I was unable to make it.

Thank you.
Krisz

Comment from alienbob
Posted: September 27, 2012 at 14:34

Hi Krisz

I have been looking at virt-manager, especially for the VNC viewer features, and it is possible that I will create packages and/or write an article about it, when I get some free time.

Eric

Comment from willian
Posted: October 3, 2012 at 17:11

Alien, everyone would like to know how is your perfect Slackware installation, from beginning to end, partitioning, filesystem, packages, tweaks and also a screenshot of your computer, this can be an upcoming article.

Comment from alienbob
Posted: October 3, 2012 at 18:05

Hi willian

My own computers are not all that interesting to talk about. They are functional but not shiny. I add only a few packages to a full Slackware install, depending on the needs (my laptop for work has some other stuff than the desktop I share with the family).
Even the background on this laptop is the standard KDE bakground…

Eric

Comment from Duodecimo
Posted: October 15, 2012 at 11:32

Hi Eric
First of all I wish to thank you for the amazing packages you place and all the contribution you do for slackware.
In your post about LibreOffice, you mentioned somewhere that packages under 13.37 might work for 14.0.
I wonder if I should try it for lame and others, in the restricted packages, or wine, in the regular ones, and even for packages for older versions, like xawtv for 12.0 (I have multilib installed).
I am using slackware 14.0.
cheers!

Comment from alienbob
Posted: October 15, 2012 at 14:41

Hi Duodecimo.

The golden rule for binary packages is, if they are not available for the Slackware release you are currently using, try a package for an older release. Often that will just work (but not always). If I find a package for Slackware 13.37 which fails on Slackware 14 then I will specifically compile a new package for Slackware 14.

So, yes, you can use the “older” packages for lame and wine. If you encounter any issues, like library linking errors. let me know so that I can compile a new package!

With sources it is different. You will find that often, the source for an older version of software will no longer compile on a newer Linux distribution. That is typically caused by updates to the gcc and glibc packages which introduce new library calls and interfaces which were not available at the time the older software was written. For successful compilation you would have to find patches or even use a newer version of the source. At the same time, a binary which was compiled from that old source, on an older Slackware release, will usually still work without issues on the new Slackware.

Eric

Comment from MartinOwaR
Posted: October 16, 2012 at 16:17

Hello Eric.

Just to report that qemu-kvm 1.2.0 does not work on 14.0 (missing libgnutls.so.26). I had to recompile it in order to make it to function.

Comment from alienbob
Posted: October 16, 2012 at 21:20

Hi MartinOwaR

Thanks for mentioning this. I have just finished uploading some fresh qemu-kvm and vde packages, built on Slackware 14.

Cheers, Eric

Comment from Jean-Francois Blavier
Posted: October 17, 2012 at 21:35

Hi Eric,

Just a note to let you know about the release of IcedTea 2.3.3, see http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2012-October/020571.html

And, once again, many thanks for all the work you do on Slackware!!

Cheers, Jean-Francois

Comment from alienbob
Posted: October 18, 2012 at 11:49

Hi Jean-Francois

The new openjdk packages have been built already, and I will upload them soon. A blog article will have to wait until tonight.

Cheers, Eric

Comment from Jean-Francois Blavier
Posted: October 19, 2012 at 18:06

Hi Eric,

Thanks for the openjdk upgrade. I installed the new package and it works great!

Cheers, Jean-Francois

Comment from Donald R Laster Jr
Posted: October 21, 2012 at 22:25

Just saying thanks for all of the work you have done. I use Slackware for my own network and for work related things. And the work you and the others do is appreciated.

Comment from neonwarf
Posted: November 18, 2012 at 04:26

thanx.

Comment from Troc
Posted: December 13, 2012 at 13:06

Thanks for the packages and updates. They work flawlessly ! Amazing stuff.

Comment from JJ
Posted: December 29, 2012 at 01:59

Hi Eric, the the *.info for your http://alien.slackbook.org/AST/ tool is out of date for SBo. The new .info file is updated to add a REQUIRES line, and removed APPROVED per http://slackbuilds.org/guidelines/

Comment from alienbob
Posted: December 29, 2012 at 02:28

Hi JJ,

You are right, I fixed the .info generator. Thanks for notifying me.

Cheers, Eric

Comment from chris
Posted: January 5, 2013 at 15:30

just wanted to say thank you for all your work.

Comment from drago
Posted: February 6, 2013 at 16:34

Hello!
Want to write howto page in docs.slackware .com, registerd, log in, try to “add page”, and got
You are here: start » howtos » misc » sb_live_5.1
Permission Denied

Sorry, you don’t have enough rights to continue. Perhaps you forgot to login?

what we can do?

Comment from OlPhart
Posted: February 8, 2013 at 11:04

alienbob – Got one heck of a question for you. I’ve been tinkering, building a new system and in the name of keeping my wife happy, decided to take a stab at getting handbrake-gtk installed. So far, your build script is the only one I’ve found for the gui. Getting handbrake installed went without a hitch using a build script from elsewhere. But running your build script is causing my system to reboot.

What the heck? Reboot while building software? There’s something really strange going on. Any ideas? Is your build dependent on multi-lib or something that I’m not providing?

Any insight would be more than welcomed.

BTW, loved the calibre build. Nice work.

Comment from alienbob
Posted: February 8, 2013 at 11:20

Hi OlPhart

My handbrake.SlackBuild does not need multilib or anything else. I run that script on a “virgin” Slackware in order to compile a package.
If your computer reboots during compilation then that might indicate an overheating issue. Software does not make your computer reboot just like that.
Is there anything in the message log right before the reboot occurs? Can you try to monitor the case- and CPU-core temperatures during the compilation?

Cheers, Eric

Comment from OlPhart
Posted: February 8, 2013 at 14:30

Thanks Eric ,

Temps are good. Don’t know what is going on but it’s certainly not temps that are doing it. Very abrupt reboot, no warning. Seems to occur at some point during ffmpeg build.

At the time I was getting the reboots I had been exec’ing the build script rather than sourcing.

When I try to source the script I get a rather cryptic kernel crash that freezes the system. Appears to be some sort of cpu related memory segmentation issue.

That said, the thought occured to me that a “virgin” build may be the answer. When I get the chance I’ll try a clean build and see how it goes.

When I get the chance to try a “clean” build I’ll get back to you and let you know how things go.

In the meantime, I’m off to shovel 6″ of fresh heavy wet snow.

Thanks,
Drew.

Comment from Cultist
Posted: February 9, 2013 at 07:02

I brought this up in #slackbuilds a while back but thought I’d post it here because I wasn’t able to catch you online at the same time I was.

I wanted to suggest that –enable-libvorbis be added to your restricted ffmpeg slackbuild. While ffmpeg does use libvorbis internally, certain applications which rely on ffmpeg to transcode (Amarok’s transcoding dialog that it gives you when you put music on a portable player being the first one that comes to mind) appear to require –enable-libvorbis to have been passed during compilation in order to transcode to ogg.

I manually add it myself when I compile ffmpeg and it does not appear to cause any problems, and does not require any additional work for the user since libvorbis is included in a stock Slackware installation.

Anyway, just my suggestion. Thanks!

Comment from alienbob
Posted: February 9, 2013 at 17:45

Cultist,

I will use “–enable-libvorbis” in future builds of my ffmpeg package. No problem at all.

Eric

Pingback from Steam – Titans Attack – Slackware 14 64bit – no sound
Posted: March 2, 2013 at 13:08

[...] Attacks game. Contact me in private (my "@slackware.com" email address or by posting to http://alien.slackbook.org/blog/your-feedback/) if you have issues with getting Minecraft going because I think that is off-topic for this thread. [...]

Comment from slodki
Posted: March 11, 2013 at 23:00

Upgrading KDE to 4.10.x removed some important plasmoid SDK tools, not packaged into kde-workspace anymore (plasmaengineexplorer, plasmoidviewer etc.). Now they are included into Plasmate (http://dot.kde.org/2013/03/05/plasmate-10-plasma-workspaces-sdk). Could you try to build Plasmate slackware package?

Thank you for all your work
Tom

Comment from jen johnson
Posted: March 19, 2013 at 05:02

thank you.
Mr. slack_dragon

Comment from guilleg
Posted: March 24, 2013 at 20:06

no requests. thank you for all!!

or maybe…..more tutorials to know the same as you know

Comment from Michelino Chionchio
Posted: March 29, 2013 at 18:08

Just one question: You have to replay mysql with mariadb in compat32 stuff, have you?
Best regards

Comment from alienbob
Posted: March 29, 2013 at 22:44

Hi Michelino

Yes, I should have done that earlier.
Fixed and uploaded.

Cheers, Eric

Comment from mickski
Posted: April 1, 2013 at 09:15

Just found your modified inet1 files for bridging. Once again AB does the hard work so I don’t have to. Thank you, your a star.

Comment from alienbob
Posted: April 1, 2013 at 12:12

Hi mickski

Those bridge modifications for rc.inet1 were merged into Slackware 14. Are you running an older version still?

Eric

Comment from mickski
Posted: April 2, 2013 at 21:49

Hey Bob
yeah still on 13.37, running kde 4.10.1 + lo 4 thanks to some slackbuilds I found somewhere :-). It really would be easier to just upgrade.
Couldn’t agree more about the awful weather.
Cheers :-)

Comment from P431i7o
Posted: April 17, 2013 at 13:39

Hi Eric, I wonder if you have reached to compile wvdial and wvstreams on your arm port. Because now I’m having problems on my raspberry-pi trying tu use wvdial.
An error about:
getcontext open parenthesis &get_stack_return closes parenthesis == 0.

The error is not in the compile time, is in execution time. I didn’t have any problems compiling from the sources provide by slackbuilds.

Searching in google point out that this is and old problem,since 2009 and so on, but I have not read anything about some that fixed the problem.

Comment from alienbob
Posted: April 17, 2013 at 14:17

Hi P431i7o

I have not yet compiled any slackbuilds.org package… just sticking to the official Slackware packages for now.
Perhaps this is your solution: http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-February/030055.html

Eric

Eric

Comment from Mário
Posted: May 3, 2013 at 16:58

Hi, Is there any easy way to make VLC link to libva installed in the system?

What do I need to change in the slackbuild?

Comment from alienbob
Posted: May 3, 2013 at 22:16

If you want to link to the system libva, then do not let the vlc.SlackBuild script enter the routine that builds an internal static copy of libva.

Eric

Comment from JKWood
Posted: May 3, 2013 at 23:33

Hi Eric,

It appears there’s something weird going on with your Slackware mirror (taper). Whenever I try to check for updates in the patches directory with slackpkg, it reports no packages to be upgraded. However, switching to the slackbuilds.org mirror fixed the problem.

Also see: http://www.linuxquestions.org/questions/slackware-14/slackpkg-says-no-pkgs-to-update-after-installing-14-0-but-there-are-pkgs-in-patches-4175451800/

Comment from alienbob
Posted: May 4, 2013 at 19:54

Hi JKWood

There was a small omission in my rsync_slackware_patches.sh script, some additional files were not being synced (FILELIST.TXT and CHECKSUMS.md5* in the main Slackware directory are updated whenever there are new patches).
I uploaded a fixed script and also ran that script on taper, so that the Slackware repositories there should work with slackpkg again.

Thanks for mentioning,

Eric

Comment from Q5sys
Posted: May 7, 2013 at 03:05

I just wanted to send you a small note to let you know how much I appreciate everything you do for the slackware community, and your continual efforts to make Slackware the most amazing distro available.
Your work is always impeccable, and I hope to someday be able to give back to the community as much as you have generously given over and over again.

Comment from raymundo augusto filho
Posted: May 13, 2013 at 21:52

Hi Bob.

I need help. I want to install Cairo Dock in slackware 12.0 and not locate binary packages. you know where I can find them?

Thank you.

Comment from alienbob
Posted: May 14, 2013 at 09:58

Hi raymundo

I do not think you will find many binary 3rd party packages for Slackware 12.0 on the Internet. Most people only release for Slackware 14.0.
A SlackBuild for ciro-dock was added to http://slackbuilds.org/ for Slackware version 13.1. I have no idea if cairo-dock will work on an old Slackware like 12.0.

Eric

Comment from raymundo augusto filho
Posted: May 15, 2013 at 02:46

Thank you Bob.

Comment from dolphin77
Posted: May 16, 2013 at 10:14

Hi, Eric.

Appreciate all your hard work on Slackware and your repositories for that. Not sure if you use SSD disks. But for those who uses SSD disks and running encrypted LVM setup, there is a need to add option –allow-discards for the cryptsetup lusOpen commad in the init file for initrd.

Would appreciate if you update that.

Thank you in advance.

Comment from alienbob
Posted: May 16, 2013 at 10:53

Hi dolphin77

Using “–allow-discards” has a potential negative security impact (see the cryptsetup man page). I guess that if you want to use this parameter because you installed Slackware on an encrypted SSD, you will have to add that parameter yourself to the init script inside the initrd. Slackware’s mkinitrd command won’t overwrite /boot/initrd-tree-init unless you specidy “-c” to (re)create the initrd from scratch.

Or you can submit a patch to introduce a variable which can be used to specify additional non-default cryptsetup parameters.

Eric

Comment from dolphin77
Posted: May 16, 2013 at 11:28

Eric, thank you for prompt reply.

You are right, I didn’t think of possible security impact. Probably it is better to leave as is system wide. Anyway on-line trimming (mounting with discard option) is not a good choice. Thus it is better to boot up from external flash disk from time to time and manually mount encrypted partitions and to run fstrim manually.

Thanks.

Comment from Alek
Posted: May 18, 2013 at 14:39

Hello, Eric
both 32-bit and 64-bit packages of kajongg-4.10.3 game are broken – there’s no executables in them.
greetz, Alek

Comment from alienbob
Posted: May 18, 2013 at 15:31

Hi Alek

You are right. I checked the build logfile and it appears that Kajongg requires pyhon-twisted (a networking library) which again depends on zope-interface.
I do not think that zope will ever be integrated into Slackware, so I left a note for Pat to decide what to do about this.
Basically there are two options:
1) remove the kajongg package entirely from Slackware’s KDE package set
2) Force the installation of the kajongg binaries (after all they are only python scripts) and leave it to the Slackware user to install python-twisted and zope-interface from SlackBuilds.org (they are both present there already).

Eric

Comment from Antonio Spinelli
Posted: May 21, 2013 at 20:24

Thanks Eric, I’ll follow you forever!

Comment from William Park
Posted: May 25, 2013 at 03:46

Hi Eric,

I know that you’re concentrating on Samsung Chromebook. But, would your Arm port of Slackware run on BeagleBone Black ?
–William

Comment from alienbob
Posted: May 25, 2013 at 13:30

Hi William

Unfortunately I can only test on hardware that I actually own. However, my ARM packages will work on any armv7 hardware. It’s usually just the kernel which you have to create for a new piece of hardware, and that will at least give you a bootable Slackware system. After that, there will usually be tweaks to get X.Org and sound fully functional but that will straighten out itself in time.

You could try what I initially did for my ChromeBook: find a bootable SD card image for another distro, write that to an empty SD card, and then wipe the other distro’s filesystem. Then copy my mini root filesystem into the empty partition and see if that will boot your BeagleBone…
A mini rootfs is here: http://taper.alienbase.nl/mirrors/alienarm/rootfs/armv7hl/chromebook/ . That rootfs does not contain a kernel or kernel modules, try copying those from a working BeagleBone distro image.

Eric

Comment from Alexandre Jobin
Posted: May 30, 2013 at 02:16

hi alienbob!

any chance to see an update of your handbrake package to v0.9.9?

alex

Comment from dolphin77
Posted: June 7, 2013 at 14:37

Hi, Eric.

Want to report that something is wrong with your slackware64-current mirror. Looks like new files were added during sync, the old ones were not deleted.
See for example http://taper.alienbase.nl/mirrors/slackware/slackware64-current/slackware64/kde/, where both kde-4.10.3 and kde-4.10.4 files are present.

Comment from alienbob
Posted: June 8, 2013 at 10:24

Hi dolphin77

Yeah, I guess that Pat uploaded his KDE packages around the time that I run my mirror script. Usually those two events are far apart.
I re-ran my mirror script and all is well again.

Cheers, Eric

Comment from alienbob
Posted: June 8, 2013 at 10:25

Hi Alexandre Jobin

Handbrake has been upgraded last week. It took some time to create a patch to make the compilation succeed.

Eric

Comment from César
Posted: June 18, 2013 at 21:43

Hi Erik, just installed calibre in slack 14.0 x86_64 multilib with all dependencies get this error.

$ calibre
Traceback (most recent call last):
File “/usr/bin/calibre”, line 20, in
sys.exit(main())
File “/usr/lib64/calibre/calibre/gui2/main.py”, line 415, in main
app, opts, args, actions = init_qt(args)
File “/usr/lib64/calibre/calibre/gui2/main.py”, line 85, in init_qt
from calibre.gui2.ui import Main
File “/usr/lib64/calibre/calibre/gui2/ui.py”, line 31, in
from calibre.gui2.widgets import ProgressIndicator
File “/usr/lib64/calibre/calibre/gui2/widgets.py”, line 21, in
from calibre.gui2.progress_indicator import ProgressIndicator as _ProgressIndicator
File “/usr/lib64/calibre/calibre/gui2/progress_indicator/__init__.py”, line 15, in
pi_error)
RuntimeError: Failed to load the Progress Indicator plugin: the sip module implements API v9.0 to v9.1 but the progress_indicator module requires API v8.1

Do I need to recompile in 14.0 or is something missing?

Thanx

Comment from alienbob
Posted: June 19, 2013 at 08:30

Hi César

I thik you are not running Slackware 14. It seems that you added some newer software on top which replaced original Slackware packages. Are you running my KDE 4.10 for Slackware 14? Part of that is an upgrade to the Slackware ‘sip’ package which is incompatible with calibre’s Slackware 14 package.

You have to recompile calibre to fix the sip error.

Eric

Comment from César
Posted: June 19, 2013 at 16:12

Eric, yes I’m using your KDE 4.10.4. I’ll recompile calibre and try to make it work. Gracias

Comment from thenktor
Posted: June 27, 2013 at 17:31

Hi Eric,
I’ve tried your alienarm miniroot fs on a device with NAND flash. I’ve created an ubifs image for rootfs and booted it. It always stops at the fsck check. ubifs does not support fsck at all, so I have patched rc.S to skip fsck for certain file systems: http://pastebin.com/AEJyy8qE

Thorsten

Comment from mick
Posted: June 30, 2013 at 20:31

Hey Bob
Did you forget to update the libreoffice slackbuild on http://taper.alienbase.nl or do I just need some patience.

Thanks :-)

Comment from alienbob
Posted: June 30, 2013 at 22:01

mick, you looked at the “14.0″ directories, right? I am not updating LibreOffice for Slackware 13.37, only for 14.0.

Eric

Comment from alienbob
Posted: June 30, 2013 at 22:08

Hi Thenktor, interesting patch. In case your pastebin entry does not have eternal life, I copied its content to http://slackware.com/~alien/rc_scripts/other_rc_scripts/rc.S_selective_fsck.diff .

Was this a Nokia device you tried the mini rootfs on? What were your findings?

Cheers, Eric

Comment from mick
Posted: June 30, 2013 at 22:20

Hey Bob
I mean the build script – http://taper.alienbase.nl/mirrors/people/alien/slackbuilds/libreoffice/build/libreoffice.SlackBuild it’s dated 18-may-2013.
last entry in the changes comments is :-4.0.3-1: 09/may/2013 by Eric Hameleers
# * New 4.0.3 release built for Slackware 14 and newer
The sources dir is up to date 30/6/13.

Once again many thanks :-)

Comment from mick
Posted: June 30, 2013 at 22:33

Lightening speed on the update Bob.
Thanks :-)

ps
Don’t know where you find the time, but very much appreciated.

Comment from thenktor
Posted: July 2, 2013 at 08:42

Hi Bob,
it was a Atmel devkit, based on a Cortex A5: http://www.atmel.com/devices/SAMA5D33.aspx
Except for the fsck thing I had no other problems. I’m using a kernel compiled from the Atmel source tree: https://github.com/linux4sam/linux-at91
Here is a picture: http://imageshack.us/photo/my-images/221/sy0l.jpg/?sa=0

Comment from Frederico Lemos dos Santos
Posted: July 3, 2013 at 18:11

I love slackware because I saw the birth of computer science. I’m sixty years and appreciates your work. It makes me very happy. I am Brazilian. Sorry my english. Congratulations!.
Frederico

Comment from jaycee
Posted: July 19, 2013 at 13:39

Hey Eric! I couldn’t help but notice this – http://blog.documentfoundation.org/2013/07/18/the-document-foundation-announces-libreoffice-3-6-7/. Are you considering creating packages for Slackware 13.37, for old time’s sake? Either way, thank you for your continuous efforts to provide timely updates for all the extra software packages you offer to us fellow Slackers! :)

Comment from alienbob
Posted: July 19, 2013 at 14:57

Jaycee, good idea. I will find some time for new LibreOffice 3.6.7 packages.

Eric

Comment from p431i7o
Posted: July 21, 2013 at 01:39

Hi Eric!.
I recently installed slackware64 (for the first time) on a Dell inspiron 14z, the thing is that it came with a hibryd video system, ati radeon plus intel graphics.
I proceeded to install it’s driver, but in some way that is described in many tutorials (download the driver, run sh amd-ati-installer.sh –buildpkg, that generated a tgz file). The thing is that it didn’t work, I tried with the beta release and the stable one, but not success, after that I looked forward into the Xorg logs, because the message was ‘no screen founds’ and something related to libgl not found.
So I started looking for that library and the result was that it was installed on /var/lib64 instead of /var/lib where it was looked for.
So the the thing is, who I have to report this? To Patrick or to the people of ATI?
I solved the problem just creating a link with ln -s of the folder fgl between the /var/lib and /var/lib64

Comment from alienbob
Posted: July 21, 2013 at 11:38

Hi p431i7o

That sounds strange, the ATI driver looking for a file in /usr/lib on a 64-bit system which uses the lib64 convention for its library locations.
I would guess that this is an issue you should report to ATI.

Also, if you feel that this issue should be mentioned on http://docs.slackware.com/howtos:hardware:proprietary_graphics_drivers?s=ati#amd_ati_catalyst_driver_installation_and_configuration then you could use that article’s “Talk” page to document your findings and hope that a WIki editor picks it up.

Cheers, Eric

Comment from Skinnable
Posted: July 23, 2013 at 13:16

This isn’t a post to inform, complain, or anything like that.

It’s fairly simple.

Thanks, alienbob for all you do in the Slackware community. You are very appreciated by this guy —> Skinnable

Although the only Slackware installation currently running in my household is on a server, I would have been completely lost without all the posts provided by you on the many pages floating around the internet.

So, thanks so much for your help – and, I appreciate all you do.

Skinnable

Comment from jaycee
Posted: July 26, 2013 at 16:26

Hey Eric! Another week, another LibreOffice release – http://blog.documentfoundation.org/2013/07/25/libreoffice-4-1-interoperability/. I was just wondering if you plan to create packages for Slackware 14.0, or wanted to wait for the release of Slackware 14.1. Considering that interoperability was a large focus of the release, it’d be handy for 14.0 users to have LO 4.1 packages available. Either way is fine though, I trust your judgement. :)

Comment from Speek
Posted: July 31, 2013 at 18:30

Hi Eric!
Here you can find a patch for building libtorrent-rasterbar 0.16.10 with boost 1.54 (as in current): https://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/libtorrent-rasterbar

Comment from Charles
Posted: August 15, 2013 at 04:45

With respect to your desire to have a tablet with Slackware on it, have you heard of the PengPod. I would love to have tablet with Linux on it but as I am not up to date on the politics of computer freedom, I find myself bouncing back and forth between the pengpod site and some of your articles on a port to the Arm architecture. Just Curious what your thoughts may be on the topic. Thanks.

Comment from Austin
Posted: September 3, 2013 at 04:17

I’ve followed your work for quite awhile, and as a last resort as not to waste your time I’ve come to you. Somewhere down the line slackpkg has been corrupt on a newly installed Slack 14 system. I’ve reinstalled the system as well as slackpkg to no avail, I’m more then willing to open a SSH tunnel for you if you would be willing to assist in either assisting me to resolve this mattery or I’m more then willing to follow any and all direction.
Thanks

Comment from alienbob
Posted: September 3, 2013 at 07:47

Hi Austin

This blog is no replacement for the user forum at linuxquestions.org … problems like the one you describe are hard to diagnose without more than “slackpkg has been corrupt”.
What I suggest you do, is open a thread on http://www.linuxquestions.org/questions/slackware-14/ and describe your problem there. Please try to give more information than what you wrote here, because I can not even start diagnosing it. Error messages? Weird behaviour? How do you experience this corruptness? Did stuff stop working? Etc…

I do not perform one-on-one support, so the ssh tunnel offer is nice but I am not going to follow up on it. I hope you understand that.

Cheers, Eric

Comment from alienbob
Posted: September 3, 2013 at 07:49

Hi Charles

I looked at the PengPod but I think its hardware is a generation too old for the price tag. Nice initiative though and I wish there were more like this. Tablet computer is not going away but the closed hardware / closed driver approach of most vendors _really_ annoys me.

Cheers, Eric

Comment from onebuck
Posted: September 3, 2013 at 12:59

Hi,

Eric, condolences for the lose of your dear friend ‘Sox’. I too lost a friend a few weeks back who would be at my side when working on the farm. ‘Mo’ will be remembered and loved for her unconditional love. Best dog!
-Gary

Comment from Charles
Posted: September 10, 2013 at 06:04

Thanks for your response. Yes, I just wish there was a tablet that had a basic linux os like slackware so I could practice writing scripts or programs. In some ways this closed hardware fight reminds of the early 90′s but from a different standpoint. The drivers didn’t exist, at least not the interconnectivity of machines. I still have my Macintosh Quadra 605 with 4 mb of ram 80 Mb HD, that I programmed in assembly, and pascal and c but that was a a long while back. I used a modem to connect to the university and did my work on a Unix mainframe. Those were the days. Appreciate greatly your response. Cheers.

Comment from Marius A. E. Beck
Posted: September 14, 2013 at 00:21

Hi Eric.

Would it be possible to add support for OpenConnect VPN to the networkmanagement package in KDE?

I successfully built the latest openconnect (5.01) and NetworkManager-openconnect (0.9.8.4) using the slackbuilds from slackbuilds.org (just had to bump version numbers). Unfortunately OpenConnect did not appear in the VPN list in the NetworkManager configuration. It seems the networkmanagent package depends on openconnect to be installed to build support for it. After installing openconnect I manually built the networkmanagent package using the KDE.SlackBuild and sources from the slackware64-current repo (4.10.5). Now it’s working like a charm. I guess this would add OpenConnect as a dependency to the KDE build.

I need openconnect because my college uses Cisco AnyConnect VPN and it failed to install via the browser. Earlier I got OpenVPN working after installing NetworkManager-openvpn using Robby Workman’s slackbuild so I was led to believe the same would apply to NetworkManager-openconnect. Googling around only confused me but in the end I found the answer in the sources (networkmanagent-0.9.0.8/vpnplugins/openconnect/CMakeLists.txt).

Cheers, Marius.

Comment from alienbob
Posted: September 14, 2013 at 11:34

Hi Marius

I think the best course of action for you would be to write to Pat Volkerding (volkerdi at slackware dot com) asking for the inclusion of openconnect and NetworkManager-openconnect into Slackware.

I am carefully aiming my KDE stuff at slackware-current and therefore not introducing new packages unless absolutely required for KDE. Openconnect is a bit of a grey area.

The build-time dependency of networkmanagement on the presence of openconnect is unfortunate.

Eric

Comment from Marius A. E. Beck
Posted: September 14, 2013 at 21:02

Thanks for your reply.

I followed your advice and asked Pat Volkerdi to include openconnect into Slackware. I also wrote to Robby Workman because he is the maintainer of the openconnect and NetworkManager-openconnect packages at slackbuilds.org and there is no mention of this issue there.

Cheers, Marius.

Comment from donrich39
Posted: September 16, 2013 at 23:37

Hi Eric,
I was wondering what happened to the URL
http://www.slackware.com/~alien/samba4/
I get an error 404. Did it move or get abandoned?
– dr -

Comment from ck
Posted: September 17, 2013 at 05:35

Hi Eric,

I’m a recent Slackware convert. Thanks for setting up this blog and putting up so much valuable information for sharing.

Recently, I wanted to learn how to compile my own kernel and I followed your post here:
http://alien.slackbook.org/dokuwiki/doku.php?id=linux:kernelbuilding&s=kernel&s=build

unfortunately, I made a very silly mistake when creating the linux symlink. Instead of running:
#ln -s /usr/src/ linux
I did this:
#ln -s /usr/src// linux
with an additional “/”
hence, my symlink linux -> /usr/src///
notice the double “//” at the end.

Upon boot up, I get a whole series of version magic error:
version magic ’3.2.29-custom SMP mod_unload PENTIUMIII ‘ should be ’3.2.29-custom SMP mod_unload 486 ‘

upon realising my mistake, I rm the symlink and source dir and start everything from scratch. However, the error persisted even though I select and rebuild all my modules with Pentium III settings.

Could I have corrupted my entire system with the wrong linux symlink?
Is there a big difference between
linux -> /usr/src// and
linux -> /usr/src///?

Appreciate if you can provide some insights to this puzzle.

Thanks in advance for your generousity!

ck

Comment from ck
Posted: September 17, 2013 at 05:38

Hi Eric,

Sorry that I had to repost this as I realised all my comments within “” were somehow truncated.

I’m a recent Slackware convert. Thanks for setting up this blog and putting up so much valuable information for sharing.

Recently, I wanted to learn how to compile my own kernel and I followed your post here:
http://alien.slackbook.org/dokuwiki/doku.php?id=linux:kernelbuilding&s=kernel&s=build

unfortunately, I made a very silly mistake when creating the linux symlink. Instead of running:
#ln -s /usr/src/linux-3.2.29-custom linux
I did this:
#ln -s /usr/src/linux-3.2.29-custom/ linux
with an additional “/”
hence, my symlink linux -> /usr/src/linux-3.2.29-custom//
notice the double “//” at the end.

Upon boot up, I get a whole series of version magic error:
version magic ’3.2.29-custom SMP mod_unload PENTIUMIII ‘ should be ’3.2.29-custom SMP mod_unload 486 ‘

upon realising my mistake, I rm the symlink and source dir and start everything from scratch. However, the error persisted even though I select and rebuild all my modules with Pentium III settings.

Could I have corrupted my entire system with the wrong linux symlink?
Is there a big difference between
linux -> /usr/src/linux-3.2.29-custom/ and
linux -> /usr/src/linux-3.2.29-custom//?

Appreciate if you can provide some insights to this puzzle.

Thanks in advance for your generousity!

ck

Comment from alienbob
Posted: September 17, 2013 at 08:13

Hi donrich39 -

Samba4 was eventually added to Slackware-current and therefor my own samba4 packages were no longer needed. But I keep a copy at http://taper.alienbase.nl/mirrors/people/alien/samba4/

Eric

Comment from alienbob
Posted: September 17, 2013 at 13:02

Hi ck

Apparently, the kernel you boot and the modules you are trying to load are not built from the same sources.
The error you posted tells you that the modules which are being loaded are compiled for “PENTIUMIII” CPU architecture, while the kernel has been compiled for “486″

The extra slash in the symlink should not have any effect on this.

You need to recompile your kernel plus modules and install them all. Perhaps you forgot to install the new kernel which you built for PENTIUMIII ?

Eric

Comment from ck
Posted: September 19, 2013 at 04:48

Hi Eric,

Thanks for your advice.
I double checked to confirm that the kernel was build for pentium III under the processor config. Still same error.

So I rm and cp new source for the build using config seed from kernel-seeds.org.

It works now. Thanks again!

cheers
ck

Comment from inman
Posted: September 23, 2013 at 14:39

hi eric,
just had a question since i use your build of ffmpeg, is that includes the libavcodec also? ( I’m not sure but i would say it was in your ffmpeg, since after upgrade to 12-Jun-2013, i get the error that it is missing.)
thank you,
cheers,
inman.

Comment from alienbob
Posted: September 23, 2013 at 22:01

Hi inman, what program is giving you issues? It’s most likely not FFmpeg but a progranm which uses FFmpeg.
Check the exact error. It will probably say something like “libavcodec.so.53: not found”.
My latest FFmpeg package contains “libavcodec.so.54″. Any program which you have compiled against an older version of FFmpeg will stop working because the SONAME of that library has changed. FFmpeg does that a lot.
This is the reason why I bundle an internal copy of FFmpeg with the VLC package for instance… to avoid this kind of breakage.

Eric

Comment from donrich39
Posted: September 24, 2013 at 00:03

Hi Eric,
Thanks for referring me to slack-current and the samba 4 pkg. Upgraded to current, installed samba 4, needed kerberos5 so got the slackbuild from slackbuilds.org and the build failed. The reason is the tcl package has been upgraded to v.8.6 in slack-current
and some test code in the kerberos5 package uses (Tcl_Interp *) interp->result, which is deprecated in Tcl 8.6
and only defined when USE_INTERP_RESULT is defined.
The fix is to breakout the offending file (tcl_kadmin5.c) and add the line:
#define USE_INTERP_RESULT
before the #include declaration. I.E.:

/* -*- mode: c; c-basic-offset: 4; indent-tabs-mode: nil -*- */
#include “autoconf.h”
#include
#include
#if HAVE_TCL_H
#define USE_INTERP_RESULT
#include
#elif HAVE_TCL_TCL_H
#include
#endif
#define USE_KADM5_API_VERSION 2
#include
#include
#include
#include
#include
#include “tcl_kadm5.h”
then replace the file in the archives and rerun the slackbuild.
I can give the commands if anyone else has the problem and is interested.
Thanks, – dr -

Comment from donrich39
Posted: September 24, 2013 at 00:35

For some reason in my above post, all the include statements had the greater-than “filename” less-than info removed.
the #define statement had to be before the #include tcl.h statement.

Comment from Austin
Posted: November 4, 2013 at 15:36

Mr. Hameleers, I wanted to thank you for all the documentation and support you provide for Slackware. I am writing today to see if I might be of some assistance. I discovered something neat while trying to install Slack on Apple products that might help others who encounter similar issues as myself.

A while back, I was offered a chance to purchase an Apple Mac Pro for a crazy-reasonable price. I have never been a fan of over-priced, last-years hardware; however, this machine had really great specs and a very attractive price. I have quite a few systems in my home, for various purposes; however, I have always wanted a true dual CPU machine. So, I went ahead and bought the Mac. As expected, I wasn’t too enthralled with Mac OS. It had some really nice features; but overall, it seemed lacking in some features that now seem basic. I began to experiment with the Mac and noticed that I couldn’t boot most install disks on it. After working with, and learning, the ups and downs of the “Mac” EFI implementation, I discovered something.

Out of all the distro’s I tried, the Ubuntu disk was the only one that started up and ran normally. It ran well, even in live mode. I did a little digging and started looking at the version of Grub on the Ubuntu boot disk, and it was unique. I tried many versions of Linux looking for one that gave me choice and also had a simple interface at boot. I found that Slackware was the best choice. Unfortunately, I couldn’t get the system to boot with the Slackware64-14 disk. I believe I read somewhere that the Linux Kernel 3.2.29 in that version wasn’t yet compatible with EFI. So I cloned Slack64 current from a mirror, built an ISO and tried to boot. No joy. So then I started playing around with the images. After much trial and error, I was able to extract both images to a folder and make a working installer. I found that the Grub.cfg for the Ubuntu version loaded additional add-ons that the Slackware version did not. Some are realted specifically to EFI and Apple products. So I took the Slack, Grub.cfg and then the Ubuntu, Grub.cfg and made a hybrid. The only difference is that the new one includes the additional add-ons that the Ubuntu installer used. I replaced the version of grub (from the Slack disk) with the one included with Ubuntu and it worked. I was able to install from DVD as well as USB. I have pretty much perfected this method. I know that many would ask why would someone want to run Slackware on a Mac. Well, because it’s awesome, and because you can. Also, older Macs get no love or support from Apple. Ultimately, my main goal was to compare features and the usage of system resources. I also wanted to test what compiling with Dual Quad-Core Xeons with 16GB DDR3 ECC would be like. I have to say, very nice. Both CPU’s support hyper-threading. If I specify 16 threads, I can compile a kernel in about 3 minutes. Anyways, sorry for the long email. I just wanted to get this information to you. If you think this method could be helpful, please let me know and I will make a tut showing what I did so others can do the same. Also, I noticed this method worked with my other UEFI systems as well. Might help some other folks having issues.

I was looking for an experience with Linux that I was unable to find other places. I want to learn the details of the OS and what makes it tick. Slackware forced me to learn in order to get what I wanted, and ultimately, that is exactly I needed.

Thanks,

Austin

Comment from alienbob
Posted: November 4, 2013 at 16:00

Hi Austin

I do not think that this information you are able to supply will find its way into Slackware 14.1 (the doors are pretty much closed on that) but why don’t you request an account at http://docs.slackware.com/ and write a nice tutorial about what you had to do to Slackware’s grub in order to boot a Mac Pro?

The Slackware Documentation Project would be the ideal location for hosting such information.

Cheers, Eric

Comment from Mr.X
Posted: November 10, 2013 at 18:18

I kinly like to ask for a Slackware Mini 14.1 build. Thank you!

Comment from alienbob
Posted: November 11, 2013 at 01:25

Hi Mr.X

Uploading mini ISO images now.

Eric

Comment from Boris
Posted: November 11, 2013 at 07:22

I believe there is a general problem with vlc 2.1 tearing with x264 videos. Do you still have a 2.0 build somewhere until they fix it?.

Comment from alienbob
Posted: November 11, 2013 at 13:03

Hi Boris,

I keep a copy of old VLC 2.0.8 packages here: http://slackware.com/~alien/vlc20/

Eric

Comment from Chu_Set
Posted: November 12, 2013 at 10:10

Hello. I would like to install latest transmission 2.82 n my current 64 box. Somehow it fails to compile when it comes to qt- part of compiling. If i comment qt-part on sb.script it goes well, but I would like to have qt as well. It fits nice to kde. Thanks.

Comment from alienbob
Posted: November 12, 2013 at 10:19

Hi Chu_Set

I do not like Transmission myself, I use qbittorrent which is also Qt-based and is a much cleaner program: http://slackware.com/~alien/slackbuilds/qbittorrent/ .

But if you want to compile transmission, give this SlackBuild script a try, it is checked on Slackware 141:
https://github.com/Ponce/slackbuilds/blob/current/network/transmission/transmission.SlackBuild

Eric

Comment from dmitri
Posted: November 16, 2013 at 21:56

Are you going to rename current/ to 14.1/ at http://alien.slackbook.org/ktown/?

Comment from Ferdi
Posted: November 19, 2013 at 05:00

hey, how much do I have to click on the ads? cheers..

Comment from francois.e
Posted: November 19, 2013 at 07:11

I saw that you packed a screen videocapture program called xvidcap a while ago. Is there any reason why xvidcap-1.1.7-i486-1alien.tgz would not work on a 14.0 installation: http://www.slackware.com/~alien/slackbuilds/xvidcap/pkg/12.1/

Sorry, I really love that package. I used to work with it before. It just made the job. I work on porteus 2.1.

Thanks.

Comment from alienbob
Posted: November 19, 2013 at 19:25

Hi dmitri,

Next KDE is going to go into a “14.1″ directory instead of current.

Eric

Comment from alienbob
Posted: November 19, 2013 at 19:26

Hi Ferdi

Don’t stress yourself :-)
Just click from time to time. Google’s adwords program recognizes abnormal click behaviour and discards those click-through actions…

Eric

Comment from alienbob
Posted: November 19, 2013 at 19:28

Hi francois.e,

Perhaps I should just build a new xvidcap package for Slackware 14.0 / 14.1.

Eric

Comment from cwizardone
Posted: November 20, 2013 at 18:33

Just FYI, dconf-0.18.0-x86_64-1.txz, is included in -current.
:-)

Comment from alienbob
Posted: November 21, 2013 at 23:18

Hi cwizardone

Yeah you’re right. I have removed the redundant package from the repository.
I also patched gecko-mediaplayer so that it works with the Chromium & Chrome browsers

Eric

Comment from john connolly
Posted: November 28, 2013 at 18:44

Eric,
I have used your multilib packages for some time. THANK YOU! However I recently installed MesaLib-9.2.3 on slackware 14.1 (graphics issues) and I am now ‘in between’ the 64 bit mesa library for 9.2.3 and the 32 bit library for the compat32-9.1.7 library. Is there a way that I can get both these libraries in sync?
Thanks, jwc

Comment from alienbob
Posted: November 28, 2013 at 22:57

Hi john,

What you can do is compile a 32-bit package for that MesaLib-9.2.3 (should be doable on your multilib computer or else ask someone with a 32-bit Slackware installation) and then use ‘convertpkg-compat32′ on the 32-bit package.

Eric

Comment from john connolly
Posted: November 29, 2013 at 03:31

Eric, What command do I use to get a 32 bit compile? The plain vanilla configure and make commands give the the 64 bit version. Incidentally the resulting installation has gone into /usr/local/lib instead of /usr/lib. I don’t know if that is a problem or not, but is there a simple way to change it?
Thanks, John

Comment from alienbob
Posted: November 29, 2013 at 10:28

Hi John

The best way forward would be to remove the Mesa stuff in /usr/local (you can probably just run “make uninstall” in the source directory) afrter creating a proper new 64-bit mesa package.
How to do that:
* grab the mesa source directory from Slackware-current, edit the mesa.SlackBuild and change the VERSION number, and place the new MesaLib source tarball inside that same directory.
* Then, run ./mesa.SlackBuild in that directory which will compile a mesa-9.2.3 package that will be placed in /tmp/
* Use the command “upgradepkg –install-new /tmp/mesa-9.2.3-*.t?z” to install your new mesa package (upgrading anything that remains from the original Slackware mesa package)
* Then proceed building a 32-bit package for mesa. Follow the guidelines here to accomplish that: http://docs.slackware.com/slackware:multilib#compiling_32-bit_programs
* Finally, convert the 32-bit package to a “compat32″ package and upgrade your computer with the result. Something like:

# convertpkg-compat32 -i /tmp//mesa-9.2.3-i486-1.txz
# upgradepkg –install-new /tmp//mesa-compat32-9.2.3-x86_64-1compat32.txz

And do not forget to re-install your binary (Nvidia or Ati) graphics driver every time you upgrade the mesa package!!

Eric

Comment from john connolly
Posted: November 30, 2013 at 02:42

“grab the mesa source directory from Slackware-current, edit the mesa.SlackBuild and change the VERSION number, and place the new MesaLib source tarball inside that same directory.
* Then, run ./mesa.SlackBuild in that directory which will compile a mesa-9.2.3 package that will be placed in /tmp/”

The mesa package that I get when I do that has all the lib files in /usr/local/lib and the header files in /usr/local/include. I don’t know how to change the slackBuild file so the files go to the right place.

Comment from q5sys
Posted: November 30, 2013 at 06:48

Do you know if anyone has written a more recent slackbuild script for rng-tools? The only one I find is from Slackware 12

Comment from alienbob
Posted: November 30, 2013 at 17:19

Hi q5sys

This is a question about the rng-tools entry on slackbuilds.org , right? You should really be asking that on the slackbuilds-users mailing list or visit the #slackbuilds IRC channel on Freenode to get an answer.
Nobody seemed to care about maintaining the SlackBuild script, why don’t you volunteer?

Eric

Comment from Alex
Posted: December 6, 2013 at 21:20

Hi Eric,
I was introduced to Slackware and Linux on general when I built my unRAID server, and I firstly want to say a huge thank you for all your packages and scripts I’ve used the last couple of years!!

I am a complete noob however when it comes to writing a slackbuild… I usually rely on botching together someone’s old script and thats what I ahve done for Makemkv(con).. until now! Theres a new dependency (libavcodec) required from ffmpeg, and I’m at a complete loss how to get that to compile for Slackware 13.1 (unRAID) to get the latest MakeMKV to compile with my (botched) slackbuild script. Any pointers would be massively appreciated!!

Alex

Comment from alienbob
Posted: December 7, 2013 at 00:09

Alex, libavcodec is part of ffmpeg. Have you tried compiling my ffmpeg.SlackBuild on your Slackware 13.1 system?

Btw – any reason why you are sticking with a relatively old Slackware version? Chances get bigger with every release that older releases no longer support compilation of newer software.

When the ffmpeg package is installed, other software should be able to pick up libavcodec.

Eric

Comment from Alex
Posted: December 7, 2013 at 00:35

Thanks for your reply Eric!

unRAID is built on Slackware 13.1 ( or possibly 13.37) so unfortunately I’m stuck with it!

I tried your ffmpeg.Slackbuild tonight and it failed unfortunately :/. My laptop is busy running chkdsk so can’t tell you exactly what it failed on other than I remember it failed in line 1557!

I’ll check what the actual failure was in the morning! If you ever fancy making a MakeMKV package in the meantime, I’d never complain! Haha. In all honesty tho I wouldn’t mind getting my head around it all a bit better!

Alex

Comment from Bill
Posted: December 9, 2013 at 02:57

Eric,
Is there some reason why http://taper.alienbase.nl/mirrors/slackware/slackware64-current/ is not being updated? I’ve had my mirror-slackware-current.sh pointed there for a while, but since the upgrade, it hasn’t shown any movement.
Regards & thanks for all the effort,
Bill

Comment from alienbob
Posted: December 9, 2013 at 10:53

Oops!
Looks like after the crash on 5 november, a lock file was not removed and therefore the mirror process was stuck. I have deleted the lockfile and manually started the mirror script. It should be OK in a short while.
Thanks for reporting this.

Eric

Comment from Alex
Posted: December 13, 2013 at 17:22

Hi Eric,
Sorry for the late reply! Still having issues and any help would be greatly appreciated!

I’ve installed your latest FFmpeg pkg ( 13.37 version) and I’m running the slackbuild script from here:http://slackbuilds.org/repository/13.37/multimedia/makemkv/ (Version Number changed).

I keep getting the error “checking LIBAVCODEC_VERSION_MAJOR… failed
configure: error: in /tmp/SBo/makemkv-oss-1.8.7′:
configure: error: LIBAVCODEC_VERSION_MAJOR is not known at compile time in libavcodec.h
See config.log’ for more details”

There is a libavcodec.pc file in /usr/lib/pkgconfig so unsure what the problem is?! For info the build instructions for MakeMKV is here: http://www.makemkv.com/forum2/viewtopic.php?f=3&t=224

Comment from Rysio
Posted: December 15, 2013 at 01:26

“convertpkg-compat32″ converts incorrectly “lesstif-0.95.2-i486-1.txz” package. “installpkg” throws message:
“install/doinst.sh: line 23: syntax error: unexpected end of file”.
Keyword “fi” is missing (line 5) in doinst.sh script…

Comment from alienbob
Posted: December 15, 2013 at 14:33

Hi Rysio

Yes I am aware of that, it has always been there since the first multilib packages.
But I did not care to write a shell script parser just for the converting… and the error is harmless.

Eric

Comment from moonstroller
Posted: December 19, 2013 at 09:08

Hi Eric. It has been a long time since I visit your site. I feel I should spend more time here and with you. How do you join the blog? I can’t find a register button anywhere. I’m getting old (62 tomorrow).

Thank you.

Comment from alienbob
Posted: December 19, 2013 at 10:36

Hi moonstroller.

There is no need to register to this site, posting comments is always allowed.
If you want to be kept informed of new posts you can use a RSS feed reader (thunderbird will do the job) and subscribe to the RSS feeds for my posts and/or comments (the links are at the bottom of every page).
Happy birthday!

Cheers, Eric

Comment from lbs
Posted: December 24, 2013 at 17:45

Hello, Eric!

First off, THANK YOU for all of your hard work. I’ve been using Slackware Linux for over 12 years now, and what you’ve done for Slack makes the overall Slackware experience that much quicker, easier, and enjoyable.

THANK YOU.

So, I’m writing to let you know that a problem seems to exist in your new LibreOffice 4.1 packages when attempting to start/play a slide show in Impress (Pressing F5 to start the show to present the slides in full screen mode). The screen freezes and will not present the slides. Pressing ESC will get you out of the freeze, but you still cannot present.

Happy Holidays.

Comment from alienbob
Posted: December 24, 2013 at 23:43

lbs, that is actually not a new problem.
See here, google will show more hits: http://www.linuxquestions.org/questions/slackware-14/impress-libreoffice-4-1-2-f5-freeze-on-slackware-current-4175480364/#post5043725

Basically:
- Go to “Tools > Options > LibreOffice (View)”
- Untick “Use Hardware Acceleration”
- Restart LibreOffice Impress

Eric

Comment from Sam
Posted: December 28, 2013 at 14:06

Hi Alien Bob I just wanted to take some time out to say a big thank you to you I have used slackware now since about 1998/9 and built lots of my own pkgs over the years, then children arrived and my time diminished your packages and fixes have saved me so many hours of work time I have used well. I just found your cure for dropbox now I can make real use of it from my linux systems. I run your firewall to jolly nice and secure BT my isp said we cant see any thing you have connected to our system thats good I said Alien Bobs firewall’s working a treat gob smacked they were lol. any way have a great 2014 when the kids are a bit bigger I will be back in the circles time I gave back to slackware. Sam

Comment from alienbob
Posted: December 28, 2013 at 15:01

Hi Sam

Good to see a Slacker who is into audio equipment servicing & repairs. Perhaps the Studioware guys should check you out (and vice versa)…

Cheers, Eric

Comment from Dennis
Posted: January 2, 2014 at 17:10

How about infinality fonts patch for Slackware 14.1?

Comment from alienbob
Posted: January 2, 2014 at 17:14

I am not interested in those Infinality font patches since they are mostly targeting MS WIndows font usage. If you use the default Slackware open source fonts you should not have a need for these patches IMHO.

Eric

Comment from Dennis
Posted: January 2, 2014 at 19:44

Actually you can target Linux too or even Mac OS X fonts (bash /etc/fonts/infinality/infctl.sh setstyle). Anyway keep up the good work.

Comment from kukukk
Posted: January 6, 2014 at 12:40

Hi,

Are you using Slackware in virtualised environment (most precisely in Citrix XenServer)?
I’m trying to install XenServer Tools in Slackware 14.1, but unfortunately Slackware is not officially supported.
If you have any experiences with this, or if you know anybody running Slackware on XenServer, please let me know. (I already tried to ask for help on linuxquestions.org, but I got no response.)

Thanks,
kukukk

Comment from alienbob
Posted: January 6, 2014 at 13:58

Hi kukukk

I only use Slackware in VirtualBox and in QEMU. I have never tried Citrix Xenserver.
I found your post: http://www.linuxquestions.org/questions/slackware-14/installing-xenserver-tools-on-slackware-14-1-a-4175488000/ but I thik there was no response because of the lack of detail. Without a copy/paste of the commands you used and the responses/errors you got there is nothing sensible to answer.

Eric

Comment from kukukk
Posted: January 6, 2014 at 15:00

Hi, and thanks for the quick reply.

I was almost sure that when you are creating/testing packages for different Slackware versions, you use them in a virtualised environment, and I hoped that it’s XenServer.

I did not added any other details because I don’t have :}. Converting and installing the Red Hat package went without any error message, but after restarting the guest XenServer still complained about missing XenServer Tools. Probably it’s because the different internal structures of the systems (something is not started, is not the right folder, etc). I don’t know, unfortunately I’m not a Linux expert. I hoped that somebody already went trough this and knows the steps required for installing XenServer Tools.

Anyway, Slackware is working fine as guest in Citrix XenServer, I just don’t have some information in the Management Console, like memory and cpu usage.

Comment from alienbob
Posted: January 6, 2014 at 16:58

Alternatively, try installing that RPM directly in Slackware, not converting it to a Slackware package first. That way, the RPM pre- and post-install scripts will be executed.

Use the command “rpm –nodeps” to avoid getting a ton of missing dependency errors.

Eric

Comment from Duodecimo Fernandes
Posted: January 7, 2014 at 12:46

Hi Eric,

I hope you can help me to find out what is wrong with my installation of pipelight.

I have followed the instructions from http://alien.slackbook.org/blog/pipelight-using-silverlight-in-linux-browsers/.

when I run Pipelight diagnostic page, I get:

Pipelight diagnostic:
Please select the Plugin you want to test:

User agent (Javascript)
Checking for Windows user agent …okay
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0
Please note: not every user agent works on every site, try multiple ones if something doesn’t work!

Silverlight (as seen by a website)
Checking for Silverlight …failed

Pipelight
Checking for Pipelight …okay

Configuration of Pipelight
Checking if config exists …okay
/usr/share/pipelight/pipelight-silverlight5.1
Checking if pluginLoaderPath is set and exists …okay
/usr/share/pipelight/pluginloader.exe
Checking if winePath is set and exists …okay
/usr/libexec/wine-pipelight/bin/wine
Checking if wine exists …okay
/usr/libexec/wine-pipelight/bin/wine
Checking if winePrefix is set and exists …okay
/home/duo/.wine-pipelight/
Checking if dllPath/dllname is set and exists …failed
You need to define either a valid dllPath/dllName or regKey
Unable to verify if the DLL exists, please check this manually!
(dllPath = c:\Program Files\Silverlight\5.1.20913.0\)
(dllName = npctrl.dll)
Checking if dependencyInstaller is set and exists …okay
/usr/share/pipelight/install-dependency
Checking if dependencies are defined …okay

Distribution
Loading file /etc/issue …okay

Welcome to \s \r (\l)

Content of file: /usr/share/pipelight/pipelight-silverlight5.1
Loading file /usr/share/pipelight/pipelight-silverlight5.1 …okay
#
# Enables a diagnostic mode which might be helpful to find an
# error in the configuration or installation.
# To get the error messages go to: http://fds-team.de/pipelight
#
# Information for advanced users: The diagnostic page embeds the plugin
# of type “application/x-pipelight-error” to trigger the output of some
# debug information. The plugin cannot be triggered if everything is
# working, so this only affects users with a broken installation.
# The debug output will include paths on the local filesystem and the
# linux distribution used. If you don’t want to leak this information
# accidentially in case of a broken installation please either uninstall
# Pipelight or disable the diagnosticMode. [default: false]
#
diagnosticMode = true

#
# Path to the wine directory or the wine executable. When you
# specify a directory it should contain /bin/wine.
#
winePath = /usr/libexec/wine-pipelight

#
# Path to the wine prefix containing Silverlight
#
winePrefix = $HOME/.wine-pipelight/

#
# The wine architecture for the wine prefix containing Silverlight
#
wineArch = win32

#
# DLLs to overwrite in Wine
# (prevents Wine from asking for Gecko, Mono or winegstreamer)
#
wineDLLOverrides = mscoree,mshtml,winegstreamer,winemenubuilder.exe=

#
# Path to the plugin loader executable
# (Should be set correctly by the make script)
#
pluginLoaderPath = /usr/share/pipelight/pluginloader.exe

#
# Path to the runtime DLLs (libgcc_s_sjlj-1.dll, libspp-0.dll,
# libstdc++-6.dll). Only necessary when these DLLs are not in the same
# directory as the pluginloader executable.
#
gccRuntimeDlls =

#
# Path and name to the Silverlight directory
# You should prefer using regKey to make it easier to switch between
# different versions.
#
dllPath = c:\Program Files\Silverlight\5.1.20913.0\
dllName = npctrl.dll

#
# Name of the registry key at HKCU\Software\MozillaPlugins\ or
# HKLM\Software\MozillaPlugins\ where to search for the plugin path.
#
# You should use this option instead of dllPath/dllName in most cases
# since you do not need to alter dllPath on a program update.
#
# regKey = @Microsoft.com/NpCtrl,version=1.0

#
# fakeVersion allows to fake the version string of Silverlight
# Allows to get around some version checks done by some websites
# when using an old version of Silverlight.
#
# fakeVersion = 5.1.20913.0

#
# overwriteArg allows to overwrite/add initialization arguments
# passed by websites to Silverlight applications. You can
# use this option as often as you want to overwrite multiple
# parameters. The GPU acceleration state of Silverlight can be controlled
# by setting:
#
# enableGPUAcceleration=false # disable GPU acceleration
# comment out # let the application decide (default)
# enableGPUAcceleration=true # force GPU acceleration
#
# You may need to overwrite the minimum runtime version if
# you use an old Silverlight version as some websites set
# an artificial limit for the version number although it
# would work with older versions.
#
# overwriteArg = minRuntimeVersion=5.0.61118.0
# overwriteArg = enableGPUAcceleration=false
# overwriteArg = enableGPUAcceleration=true
#

#
# windowlessmode refers to a term of the Netscape Plugin API and
# defines a different mode of drawing and handling events.
# On some desktop enviroments you may have problems using the
# keyboard in windowless mode, on the other hand the drawing is
# more efficient when this mode is enabled. Just choose what works
# best for you. [default: false]
#
windowlessMode = false

#
# embed defines whether the Silverlight plugin should be shown
# inside the browser (true) or an external window (false).
# [default: true]
#
embed = true

#
# Path to the dependency installer script provided by the compholio
# package. (optional)
#
dependencyInstaller = /usr/share/pipelight/install-dependency

#
# Dependencies which should be installed for this plugin via the
# dependencyInstaller, can be used multiple times. (optional)
#
# Useful values for Silverlight are:
#
# -> Silverlight versions (you need to adjust dllPath):
# wine-silverlight5.1-installer
# wine-silverlight5.0-installer
# wine-silverlight4-installer
#
# -> optional depependencies (required by some streaming sites)
# wine-mpg2splt-installer
#
dependency = wine-silverlight5.1-installer
dependency = wine-mpg2splt-installer
dependency = wine-wininet-installer

#
# Doesn’t show any dialogs which require manual confirmation during
# the installation process, like EULA or DRM dialogs.
# [default: true]
#
quietInstallation = true

#
# In order to support browsers without NPAPI timer support
# (like Midori) we’ve implemented a fallback to
# NPN_PluginThreadAsyncCall. In the default configuration
# a timer based approach is preferred over async calls and the
# plugin decides by itself which method to use depending on the
# browser capabilities. Setting the following option to true
# forces the plugin to use async calls. This might be mainly
# useful for testing the difference between both event handling
# approaches. [default: false]
#
# eventAsyncCall = true

#
# The opera browser claims to provide timer functions, but they
# don’t seem to work properly. When the opera detection is
# enabled Pipelight will switch to eventAsyncCall automatically
# based on the user agent string. [default: true]
#
operaDetection = true

#
# Minimal JavaScript user agent switcher. If your page doesn’t check
# the user agent before loading a Silverlight instance, you can use
# this trick to overwrite the useragent or execute any other Java-
# Script you want. You can use this command multiple times.
# Uncomment the following 4 lines for FF15 spoofing.
#
# executejavascript = var __originalNavigator = navigator;
# executejavascript = navigator = new Object();
# executejavascript = navigator.__proto__ = __originalNavigator;
# executejavascript = navigator.__defineGetter__(‘userAgent’, function () { return ‘Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120427 Firefox/15.0a1′; });

#
# We are currently implementing hardware acceleration support, which
# can cause problems on some systems as especially specific open source
# drivers render only garbage when hardware acceleration is enabled.
# To prevent breaking any working solutions, we are currently
# implementing a whitelist system, which will enable hardware
# acceleration by default if the specified shell scripts returns 0.
# Otherwise we will disable it. You can still use
#
# overwriteArg = enableGPUAcceleration=false/true
#
# to overwrite the check results. If you really want to skip this test
# you can use: silverlightGraphicDriverCheck = /bin/true
#
silverlightGraphicDriverCheck = /usr/share/pipelight/hw-accel-default

#————————- EXPERIMENTAL ————————-
# Watch out: The following section contains highly experimental
# stuff! These functions are likely not working properly yet and
# might be removed at any time.

#
# Silverlight uses a lot of timer stuff do to the window redrawing
# . In order to speed this up a bit the following switch enables
# some API hooks to do most of timer stuff in user mode (without
# having to call wine-server each time). It is still unclear
# if this option has any significant effect on the performance.
# [default: false]
#
# experimental-userModeTimer = true

#
# In order to make it possible to let a window stay opened in fullscreen, even
# if the user clicks somewhere else it is necessary to install a window class
# hook. With some plugins this could lead to other problems! [default: false]
experimental-windowClassHook = true

#
# A sandbox is a method to isolate an untrusted program from the rest of
# the system to prevent damage in case of a virus, program errors or
# similar issues. We’ve been developing the ability to use a (self-created)
# sandbox, but this feature still has to be considered experimental.
# The feature will only be used when the sandbox path exists.
#
sandboxPath = /usr/share/pipelight/sandbox

On the terminal window running firefox I get:
[PIPELIGHT:LIN:unknown] attached to process.
[PIPELIGHT:LIN:unknown] checking environment variable PIPELIGHT_SILVERLIGHT5_1_CONFIG.
[PIPELIGHT:LIN:unknown] searching for config file pipelight-silverlight5.1.
[PIPELIGHT:LIN:unknown] trying to load config file from ‘/home/duo/.config/pipelight-silverlight5.1′.
[PIPELIGHT:LIN:unknown] trying to load config file from ‘/etc/pipelight-silverlight5.1′.
[PIPELIGHT:LIN:unknown] trying to load config file from ‘/usr/share/pipelight/pipelight-silverlight5.1′.
[PIPELIGHT:LIN:silverlight5.1] GPU driver check – Your driver is supported, hardware acceleration enabled.
[PIPELIGHT:LIN:silverlight5.1] using wine prefix directory /home/duo/.wine-pipelight/.
[PIPELIGHT:LIN:silverlight5.1] checking plugin installation – this might take some time.
[PIPELIGHT:LIN:silverlight5.1] basicplugin.c:373:checkPluginInstallation(): error in execvp command – probably dependencyInstaller/sandbox not found or missing execute permission.
[PIPELIGHT:LIN:silverlight5.1] basicplugin.c:383:checkPluginInstallation(): Plugin installer did not run correctly (exitcode = 1).
[PIPELIGHT:LIN:silverlight5.1] basicplugin.c:142:attach(): plugin not correctly installed – aborting

Same problem happens when I change silverlight plugin version.

Cheers, Duodecimo.

Comment from Duodecimo Fernandes
Posted: January 7, 2014 at 13:12

Hi Eric,

Oops, I forgot to mention on the previous message that I use Slackware 14.0 64 bits multilib.

Cheers, Duodecimo.

Comment from alienbob
Posted: January 7, 2014 at 13:12

Hi Duodecimo

Did you execute the command (under your own user account):

pipelight-plugin –enable silverlight

Also, you should check the enabled plugins by running:

pipelight-plugin –list-enabled

Do you see Silverlight mentioned there?

The very first time that the pipelight plugin loads you should see a Wine dialog mentioning that SilverLight is being downloaded and installed.

Eric

Comment from Duodecimo Fernandes
Posted: January 7, 2014 at 13:24

Hi Eric,

yes, the pipelight-plugin commands runs ok, and I checked on my user home that .mozilla/plugin gets the correct link to silverlight library.
As with wine dialog mentionning that silverlight is being downloaded, well, I remember it showing up the first time I installed pipelight. As I had got problems, I did try to reinstall all over again, as I foun out I had to versions of the Alsa package, the converted one that I installed following your pipelight page instructions, and a previous one (an alien version, maybe from slackpkg+ with multilib settings). In fact I thought about cleaning out stuff in order to have wine downloading silverlight again to see if it fixes my problem, but I didnt know what I should erase.

thanks, Duodecimo.

Comment from JesusM
Posted: January 10, 2014 at 20:25

Hi Eric,

Are you aware that your avidemux 2.6.x package creates a bin named ‘avidemux3′ but the avidemux.desktop entry still calls ‘avidemux2′? It’s not a big thing, but just in case you didn’t realized that.

And about your RSS. It’s great and I’ve subribed and use lots of your packages. Are you thoght on adding the link to the specific package in each RSS entry instead of linking to the whole repository? Just and idea.

Anyway, thanks for your work and happy New Year!

Comment from alienbob
Posted: January 10, 2014 at 23:20

Hi, yes I am aware of that bug in avidemux which I did not spot at first (someone else pointed it out in another comment). I have a fixed SlackBuild but that won’t be used until there is a new version of avidemux probably.

I’ll give your RSS request some consideration.

Eric

Comment from Bill Kirkpatrick
Posted: January 26, 2014 at 18:50

Eric,
I have been spending the post couple of days recovering from something (that I probably did!) that erased the partition table from sda on my desktop machine. (At least it didn’t get my data drive. Anyway, when reloading calibre & all of its deps, I noticed that you have a “python-imaging” package & Slackware-current already has “pil”. Both seem to package the same digital libraries. I did not install your package, just to see what would happen. Calibre starts & performs simple tasks properly. Will I miss out on something more obscure by not having your package? If I do install your package, should I upgrade Slackwares package or put them in side by side?
Regards,
Bill

Comment from alienbob
Posted: January 26, 2014 at 22:09

Yeah Slackware’s pil and my python-imaging packages are the same. I should remove it from the external dependency list.

Eric

Comment from Björn R.
Posted: January 27, 2014 at 22:22

Hi Eric,
i have installed the current slacky 14.1 and build a handbrake package with your script.
With the “Video Encoder” = x264 i get the error message “Segmentation fault”. So other encoder goes.
I read something about “Miscompilation with gcc 4.8″
Have you an idea for patch/workaround ?
Thanks, Björn

Comment from alienbob
Posted: January 27, 2014 at 23:06

What if you use my package for handbrake instead of compiling it yourself? I can create H.264 videos on Slackware64-current without any segfault.

And what is “the current slacky”? The name of the distro is Slackware.

Eric

Comment from Björn R.
Posted: January 29, 2014 at 10:42

I compiling it self with your build files and get the error.
Now i found your package and have no problems with H.264. Thanks, Björn

Comment from Bill Kirkpatrick
Posted: February 15, 2014 at 20:19

Are you going to upload the 64 bit version of fbreader for -current? The folder is empty on both slackware.com & taper.alienbase.nl.
Regards,
Bill

Comment from alienbob
Posted: February 15, 2014 at 23:11

Hi Bill

The package did not get uploaded for unknown reasons, but I will set that right tonight. Thanks for the notification.

Eric

Comment from kukukk
Posted: February 22, 2014 at 09:22

Hi,

Just a small update regarding to XenServer Tools on Slackware. Finally I managed to get it working. I had to make the following changes:
– recompile the kernel with Xen guest support enabled in Linux guest support (it was a bit tricky to add it to lilo, because my device changed from /dev/sda to /dev/xvda)
– modify the distribution detection script in XenServer Tools to support detecting Slackware
– modify the guest parameters updater script, because “ifconfig” seems to have different output format on Slackware.

A future request for Slackware: Xen guest support enabled by default :}

Best regards,
kukukk

Comment from Igor
Posted: March 21, 2014 at 17:51

Hi Eric,
i am a brazilian user of slackware since longe time ago.
This days i try to figure out a way to start a diskless Slackware 14.1 client from a PXE + DHCP + NFS, without success. I can do this using a specific old 2.6 kernel, but in Slackware 14.1, i can’t figure out a way.

My PXE config sounds like:
DEFAULT pxelinux.cfg/vmlinuz-2.6 ip=dhcp root=/dev/nfs nfsroot=192.168.0.80:/tftpboot/nova-distro vga=791 init=/etc/rc.d/rc.S quiet rw

So if i change the old specific kernel (vmlinuz-2.6) to the new one Slackware 14.1 kernel (vmlinuz-huge-3.10.17) on PXE server, clients cant start due to a kernel panic error.

In Slackware 14.1 i will need a initrd?

Using the old “vmlinuz-2.6″ i dont need any extra ramdisk, just the kernel.

Can you help me to solve this?

Thanks to you attention and sorry to my bad english.

Comment from JKWood
Posted: March 30, 2014 at 16:07

Hey Eric,

Lookups like the slackware-current and slackware64-current directories on taper aren’t being updated.

Comment from alienbob
Posted: March 30, 2014 at 22:16

Hi JKWood

Yes, a lock file was left (perhaps after a crashed mirror action) and it prevented further mirror actions.
I deleted the lockfile and the mirrors are syncing again.
Thanks for spotting and reporting!

Eric

Comment from Mike H.
Posted: April 5, 2014 at 14:22

Hello Eric,

is there a reason why your KDE packages don’t come with Kolab libraries anymore? I’ve tried and created build-scripts based on SlackBuilds-templates and your last build-scripts from 4.8 (or was it 4.9?) and got Kolab support for Kontact after compiling your KDE 4.12.3 packages. Additional dependencies are xerces-c (available on slackbuilds.org) and xsd (just created my own slackbuilds-script).
If you are interested in adding Kolab support again I could help if needed, otherwise I would simply submit my scripts to SlackBuilds. Personally I think it would be better if KDE would come with all needed dependencies, though.

Mike

Comment from alienbob
Posted: April 6, 2014 at 12:47

Hi Mike

I wrote about how to re-add Kolab support here:
http://alien.slackbook.org/blog/kde-4-9-5-was-released-next-should-be-4-10/ which was well before Slackware adopted KDE 4.10. At that time, I discussed it with Patrick and we decided not to add the Kolab support packages to the distro.

You can still find the sources for libkolab and libkolabxml here: http://taper.alienbase.nl/mirrors/alien-kde/source/4.10.5/deps/ . A package for xerces-c is in my mail repository: http://www.slackware.com/~alien/slackbuilds/xerces-c/

Unless new dependencies have been added in the meantime, these three packages should allow you to add Kolab support by recompiling kdepim-runtime.

Eric

Comment from raffaele
Posted: April 9, 2014 at 18:33

Hello! In multilib, I noticed that two packages have to be updated! openssl-1.0.1f and openssl-solibs-1.0.1f are vulnerables to Heartbleed. Many thanks for you excellent job.
Best regards,raffaele

Comment from alienbob
Posted: April 9, 2014 at 20:10

Hi raffaele

Yes that was on the agenda for after work. By now, the updates should be in the multilib repository.

Eric

Comment from Mohammad Etemaddar
Posted: April 9, 2014 at 20:43

I liked Slackware to have requirements for Inkscape by default.
They are too much to install :)

Comment from Regnad Kcin
Posted: April 20, 2014 at 19:59

I know it ain’t your fault but there is a error in LibreImpress that prevents the slides from showing unless hardware acceleration is turned off. It was quite alarming and I installed slackware on another machine and found the same problem with the latest update.

Appreciate all your work.

I am going to build a new machine and upgrade to the 64 bit Slackware. I suppose I should go with 14.1?

Comment from Regnad Kcin
Posted: April 20, 2014 at 20:03

Ah, I live in Beijing so Chinese language support is useful for me. I got SCIM running about halfway- not very acceptable.

I fiddled with ibus for awhile some time back and finally couldnt make it perk. fcitx i got going for awhile but it was very unstable.

Any further thoughts? I am not going to try another Linux version. I am committed to being a slacker.

Comment from alienbob
Posted: April 20, 2014 at 22:14

Hi Regnad

Yes, the issue with Impress has been known for sometime (http://www.linuxquestions.org/questions/slackware-14/impress-libreoffice-4-1-2-f5-freeze-on-slackware-current-4175480364/ for instance), nobody has fixed it yet unfortunately. Takes you by surprise.

Eric

Comment from alienbob
Posted: April 20, 2014 at 22:17

Regnad, what are your issues with SCIM? I did not play around with ibus yet, so I can not talk about how (un)stable it is.

Eric

Comment from Regnad Kcin
Posted: April 21, 2014 at 06:35

scim doesnt seem to work with some software like firefox. havent tried it with chromium though.

Comment from Regnad Kcin
Posted: April 21, 2014 at 08:54

When I used scim it only seemed to be able to input chinese pinyin for qt4 applications. I then tried fcitx but it wasnt much better because it was erratic. I finally did a clean install to start over.

I am going to tear into the chinese thing full bore when I get time. Will probably go to Slackware 64 bit first though because I am wanting to build a i7 machine in a small portable itx size box for a project I am working on.

Any advice on Chinese input would be appreciated.

Comment from Regnad Kcin
Posted: April 24, 2014 at 08:48

I installed the new KDE update, but now find that my audio does not work. Slackware finds the card and tests are ok but audio applications dont find the audio device.

Comment from Hubert Phava
Posted: April 24, 2014 at 13:41

Hi Eric. First of all, thanks for your *great* jobs for Slackware.
I’ running –current (64bit) with your multilib packages and last kde-4.13.0. On kde i’ve found that “baloo” ( the new semantic-indexing tool) eats lots of resources and eats lot of disk space ( for example, before i killed it, 7,9G of my homedir were filled by its stuff).
Removepkg-ed it, no chance to have dolpin so reinstallet baloo package but “chmod -x” its binaries.
Is there a chance to have dolpin not linked to baloo libraries?

Ah: my machine has a Amd-8core, 32G of ram and 5 hardisk ( my /home is on a raid-1 two 1G disks).

Thankyou again for your works…

HP

Comment from alienbob
Posted: April 25, 2014 at 12:28

Hi Hubert,

Baloo libraries will remain linked to KDE binaries, but you can disable the indexing preocess in two ways: by removing the binaries “baloo_file_extractor” and “baloo_file_cleaner”.
OR, add your homedirectory to the list of excluded directories for indexing. If Baloo finds that you have excluded your $HOME, then it will disable itself. In “System Settings -> Desktop Search” add your home to the blacklist.

If you do not want the index-based search menu in dolphin, you can do the following:
$ cp /usr/share/autostart/baloo_file.desktop ~/.kde4/share/autostart/
$ echo “Hidden=True” >> ~/.kde4/share/autostart/baloo_file.desktop

There was a heated discussion on the KDE packagers mailing list about the bright idea of the developer, *not* to add a “disable indexing” button in the System Settings. I guess such a button will appear at some point in the future.

Eric

Comment from alienbob
Posted: April 25, 2014 at 12:29

Hi Regnad

The updates to KDE should not have an influence on your audio… is there something else you have changed or updated recently?

Eric

Comment from alienbob
Posted: April 25, 2014 at 12:30

Regnad, I would have to check using SCIM with pinyin input methods, to see how it affects Firefox. It used to work in the past, I have not paid attention to it recently.

Eric

Comment from Huber Phava
Posted: April 25, 2014 at 12:41

TY alienbob…
Putting $HOME in the blacklist didn’t have effects on my machine, i dont’ know why.
And there is a bug ( as the developer writes in his blog) regarding Maildir directories ( i’ve such a dir, of course …) that can bring to a loop in indexing.
Anyway, “chmod -x” the binaries is good for me and i hope developers will put ASAP that damn button to stop their crappy software and that they will stop to think like Gnome’s developers do.

Have a funny WE
;-)

HP

Comment from alienbob
Posted: April 25, 2014 at 12:54

Hi Huber

I very much agree with your observation “stop to think like Gnome’s developers do”. The lack of the “disable indexing” button because the developer wanted to decide for the user that indexing is a “good thing” and therefore must be enabled always, strikes me as a worrisome example of how KDE software should _not_ work.
While the GNOME paradigm is “dumb down the interface, let the developer / UI designer make the decisions for the user” I have always though that the KDE philosophy was “if it can be tweaked, show a tweak button in the UI and leave the choice to the user”.

Eric

Comment from Mickski56
Posted: May 2, 2014 at 16:19

For anyone else experiencing failures to login to non kde sessions with kde-4.12.5 there’s a patch here http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/kde-base/kdm/files/kdm-4.11.9-desktopnamescrash.patch?revision=1.1 .It works for me.

Big thanks to alienbob for the latest kde releases amongst many other things.

Comment from alienbob
Posted: May 2, 2014 at 23:04

Hi Mickski56,

Well, the patch I used is https://projects.kde.org/projects/kde/kde-workspace/repository/revisions/e1724800ecf3c6a7035dfa7bcaa50b2a8f48688f/diff but it is the same issue that it fixes (the KDE patch is better than the Gentoo patch).

I was already compiling a new kde-worlspace package after this patch was announced on the kde-packagers mailing list and I am taking the opportunity to fulfill a request from Willy Sudiarto Raharjo to move the KDE sessions files to /usr/share/xsessions/ where XFCE installs its own session definition file already, so that other login managers can see these desktop session choices too.

Thanks for being alert.

Eric

Comment from eric spiering
Posted: May 13, 2014 at 18:15

hi – i am a longtime slack user. i was running 14.0 and using the ftdi_sio to talk to a printer and it was working fine, then i upgraded to 14.1 and the ftdi_sio now goes into an infinite connect/disconnect loop on the device. did 14.1 add something that is competing with ftdi_sio for the device? i can’t figure it out. the ftdi_sio source code hasn’t changed…

Comment from alienbob
Posted: May 13, 2014 at 20:42

Hi eric spiering,

I have no idea – I do not use printers myself, perhaps it is wiser to open a thread on http://www.linuxquestions.org/questions/slackware-14/ and get a wider audience for your driver issue…

Eric

Comment from eric spiering
Posted: May 14, 2014 at 12:03

hello again, i have had this posted in LQ for several days now, but nobody has replied to it. i am thinking there is some configuration change in 14.1 that is now fighting for the ttyUSB0 connection, but i don’t know where to look to find it. do you see anything in these logs that might identify the culprit? This device connects fine to putty, so the device is good, but i need to use my minicom!

http://www.linuxquestions.org/questions/linux-software-2/ftdi_sio-connects-and-disconnects-forever-4175504613/

Comment from alienbob
Posted: May 14, 2014 at 13:01

Hi eric

If this is a Slackware-specific issue, then you should request that the moderators move your post to the Slackware forum (http://www.linuxquestions.org/questions/slackware-14/) where there will be more knowledgeable people than in the generic forums.

The first line I read in your post, “I have slack 14.1, kernel 3.14.3″ means that you are not running a stock Slackware 14.1 (which contains kernel 3.10.17 instead).

Eric

Comment from Alberto
Posted: May 22, 2014 at 11:52

Hi Eric,
I just install your new chromium package and I have issues with the keyboard.
More details: I’m using a QWERTY keyboard with an IT layout and it’s impossible to type every accented letter:
à is ‘
è is [
ì is =
ò is ;
ù is nothing.
It’s a chromium issue because everywhere in the system typing is good and I tested this on two 64bit slackware one with kernel 3.10.17 and one with 3.14.1.
With the previous version of chromium all was good.
What would suggest to do?

Comment from alienbob
Posted: May 22, 2014 at 13:20

Hi Alberto

Are you perhaps using SCIM or Ibus as text input methods? There is a bug in Chromium 35 apparently with XIM, as found here: https://code.google.com/p/chromium/issues/detail?id=360388

Eric

Comment from Alberto
Posted: May 22, 2014 at 14:34

Nope.
But I found a similar issue (probably the same, but explained better than mine) and setting the LANG variable before starting chromiu seems to help:
$ LANG=it_IT.UTF-8 chromium

In other words, browser keyboard layout is “locked” to en_US.
https://code.google.com/p/chromium/issues/list/detail?id=376246

Comment from Alberto
Posted: May 22, 2014 at 14:36

Sorry: https://code.google.com/p/chromium/issues/detail?id=376246

Comment from Hubert Phava
Posted: May 22, 2014 at 14:57

Upgraded just know: no problems at all with “italian” letters ( or keyboard).
I’m on 64–current with the entire Aliens’ stuff (multilib, kde, eccecc).
I have:

export LOCALE=it_IT.UTF-8
export LANG=it_IT.UTF-8

in /etc/profile.d/lang.sh

italian keyboard in Kde and:

Option “XkbLayout” “it”

in the InputDevice section of my /etc/X11/xorg.conf

HP

Comment from Alberto
Posted: May 22, 2014 at 18:38

It doesn’t work for me.

Comment from Hubert Phava
Posted: May 22, 2014 at 19:03

Alberto: what family of fonts are set in chromium?

Comment from Alberto
Posted: May 23, 2014 at 09:00

I guess standard ones. Anyway, after rebooting everything works fine. Thanks for your suggestion =)
Sadly there’s another problem: after updating, chromium doesn’t see java.
Worst release ever =(

P.S. In firefox everything works fine.

Comment from Phil
Posted: May 25, 2014 at 15:05

Hi Eric
Tried updating weekly version of calibre, but according to slackpkg+ there are no updates. Checked around various mirror sites and it seems that only the master has been updated.

Comment from alienbob
Posted: May 25, 2014 at 20:27

Hi Alberto

Starting with chrome and chromium 35, Google has removed support for NPAPI plugins (Netscape Plugin API i.e. the mozilla browser compatible plugins). This means that things like the icedtea-web Java plugin stopped being supported, but also the Pipelight plugin and several others that do not “talk” Google’s own PPAPI (Pepper Plugin API).
It sucks.

Eric

Comment from alienbob
Posted: May 25, 2014 at 20:28

Hi Phil

If everybody mirrors from my “taper” mirror then nobody will have had new packages. It looks like the mirror cron job had become stuck.
It’s been repaired now.

Eric

Comment from Alberto
Posted: May 26, 2014 at 09:38

Hi Eric,
thanks for your reply.
I don’t use openJDK, but Oracle’s official jdk (repackaged with the slackbuild included in Slackware).
Does it make any difference?

Comment from Phil
Posted: May 26, 2014 at 10:18

Cheers Eric
My mirror now up to date :-)

Comment from alienbob
Posted: May 26, 2014 at 15:51

Hi Alberto

The closed-source Oracle Java browser plugin uses the same NPAPI protocol as the opensource icedtea-web browser plugin. Both are incompatible with Chrome and Chromium 35 and higher.

Eric

Comment from Alberto
Posted: May 26, 2014 at 18:48

I see =/
The worst part is that also google talk plugin is blocked now.

Comment from alienbob
Posted: May 26, 2014 at 21:43

Alberto, the newest version of the HangoutPlugin should be a PPAPI version and work in Chrome/Chromium 35.

Eric

Comment from Alberto
Posted: May 28, 2014 at 14:24

I tried with the last one (version 5.4.1.0 – according to what the SBo slackbuild extracted) and it is not visible among plugins =(
If you succeed in making it work, let me know =)
Thanks again!

Comment from alienbob
Posted: May 28, 2014 at 15:17

Hi Alberto

The google-talkplugin 5.4.1.0 installs both the NPAPI and the PPAPI libraries. It takes a small change to make the PPAPI library available in chromium if you are using the SBo script to create a package.
Below is the patch I applied to the google-talkplugin.SlackBuild :

Eric

# —–8< ----------------------------------
26c26
< VERSION=${VERSION:-4.9.1.0}
---
> VERSION=${VERSION:-5.4.1.0}
37a38
>
42a44
> # Just in case:
65,66c67,75
< chmod 0755 $PKG # Put this back.
< rm -rf etc/ # The cron job is debian/ubuntu only.
---
> # Put this back.
> chmod 0755 $PKG
>
> # change /usr/lib/chromium-browser to /usr/lib/chromium
> mv ${PKG}/usr/lib/chromium-browser ${PKG}/usr/lib/chromium
>
> # Remove cron update script:
> rm -rf ${PKG}/opt/google/talkplugin/cron
> rm -rf ${PKG}/etc
# —–8< ———————————-

Comment from Alberto
Posted: May 28, 2014 at 20:26

It works!
Thanks a lot, Eric.

Comment from JesusM
Posted: May 31, 2014 at 20:09

Hi Eric,

since Chromium 35 doesn’t support NPAPI plugins any more, could you make available again your last Chromium 34 package?

Thanks a lot!!

Comment from Brad R.
Posted: May 31, 2014 at 21:44

I get an error when I try ann open a book on the command line with fbreader 0.99.4.

Gentoo had the following patch that works for me:

— fbreader-0.99.4-pristine/zlibrary/ui/src/qt4/filesystem/ZLQtFSManager.cpp
+++ fbreader-0.99.4/zlibrary/ui/src/qt4/filesystem/ZLQtFSManager.cpp
@@ -49,3 +49,4 @@
path = replacement + path.substr(1);
- }
+ }
+ ZLUnixFSManager::normalizeRealPath(path);

Comment from alienbob
Posted: June 1, 2014 at 12:22

Hi Brad

Ah, weird! I see the same crash, and indeed only happens when you try to open a book on the commandline.
I am going to look at that patch, thanks.

Eric

Comment from alienbob
Posted: June 1, 2014 at 16:10

Hi JesusM

Chromium 35 is a security release, so it is not advisable to keep running 34.
If you need Java or Netflix, then Firefox will be your only option.

If you want to know how hard it is to switch pipelight to a PPAPI plugin because of the sandboxing of Chrome plugins, read https://bugs.launchpad.net/pipelight/+bug/1321505

Eric

Comment from Eduardo
Posted: June 5, 2014 at 17:15

Hi Eric! I’d like to thank you for your build of Chromium 35. It feels much lighter and faster than the previous versions.

However, there is a problem and I’d like to troubleshoot it in order to know whether the issue lies in the build, or the software itself, or my own configuration.

My keyboard layout is US International, which has dead keys. Now, starting from Chromium 35 I cannot produce some characters with dead keys, but I can produce others. Among the characters that I can write are: á é ñ, and among the characters that I cannot produce are: « » ¿ ç. Some of them (like ¿) are essential to write proper Spanish.

Thus: Is this due to some ./configure parameter? Is this because the software itself (I understand they’re using a new toolkit).

My own configuration may also be the culprit, but I doubt it because I had no problems until Chromium 34.

Thanks again,

Eduardo

Comment from Regnad Kcin
Posted: June 15, 2014 at 16:02

Some comments:
1. I got SCIM to work in chinese and it works very well indeed and I have a fully functional bilingual (for me) system.

2. The latest version of Libre Office is quite good and I am transitioning completely away from microsoft office except for shared edits with stored changes (just because I dont feel completely comfortable with this feature in microsoft office.)

I still have to disable hardware acceleration manually otherwise Libre Impress hangs on slide shows.

3. I recently had a horrid experience with adding a 3rd hard drive to my machine which has to be added to an SATA slot number smaller than the boot drive. Finally i got it going using UUID and mkinitrd and lilo.conf editing. This really was a pain and took a lot of time to figure out and I almost despaired of adding the 3rd hdd. The documentation on this was not so clear and I had to dig. Others might not be so determined as me.

Comment from Michelino
Posted: June 17, 2014 at 09:07

Just to notice you the new release of mirall
;-)))
Thanks in advance!!!

Comment from Max
Posted: July 8, 2014 at 03:05

Hi Eric
Please I need chromium-33.0.1750.152-i486.txz you have this package? Please post link!

Comment from Eduardo
Posted: July 21, 2014 at 00:08

Hi Eric, I noticed you upgraded chromium to 36. I use Slack64-current multilib. I’m thinking about switching to firefox because since the latest X.org upgrade in current, chromium in Slack64-current began to be really sluggish when typing text. This began to be apparent in chromium 35 (after the X.org upgrade) and continued in chromium 36. To this add the known issue with dead keys and foreign languages.

I’ll continue to upgrade chromium as you provides releases, but for now it will become my second browser, not the default. The typing issue makes it very uncomfortable to use it.

Thanks again for all your effort. I hope this gets solved soon.

Regards,

Eduardo

Comment from Alberto
Posted: July 22, 2014 at 09:34

Hi Eric,
as always great work with the new chromium release.
I’d like to report a bug that wasn’t there in previous releases: it is not possible to set it as default browser.
I don’t know if it is due to the build process or to chromium itself.

Comment from alienbob
Posted: July 24, 2014 at 02:20

Hi Alberto,

Works here with Chromium 36.0.1985.125 and running Slackware (almost-)current and KDE 4.13.1.

Note that setting it as the default browser changes the xdg-open behaviour.

Comment from Regnad Kcin
Posted: July 26, 2014 at 05:24

How -current does -current need to be? I am running multilib -current but havent updated to the most recent -current. I notice that you are also not-quite-current. The latest KDE and chromium are up and working ok. I find some problem with KDE occasionally (kwin blows up and gives and error message but I can keep working) and LibreCalc does weird stuff sometimes but it’s all tolerable.

Actually I am a bit leery of the latest -current with the display problems.

Comment from Eduardo
Posted: August 7, 2014 at 00:07

Hi Eric, I’m happy to say that Chromium behaved itself again after the latest X.org update (I use Intel chips). The issue with international characters continue, though. Thanks for everything!

Comment from Fred
Posted: August 22, 2014 at 14:25

Hi,

Thank you for providing this site and your slackware packages.

My apologies if this should be posted to the LibreOffice dev group. I searched for a ticket on this but couldn’t find one.

I have been using LibreOffice from your slackbuilds (slackware64-14.1) and have had no issues until the 4.3.0 release. Just recently, I tried saving in MS *.xls and *.xlsx formats and received an error from LibreOffice stating that saving failed. The export works with OpenOffice 4 and previous versions of LibreOffice.

Just wondered if you or anyone else has had this issue.

Cheers,

Fred

Comment from Regnad Kcin
Posted: August 22, 2014 at 14:48

i regularly save in those formats .xls .xlsx from libreoffice calc and dont have any trouble.

i am running slackware 64 -current (linux 3.14.16) and the latest libre office. i had some issues with calc blowing up after font changes a couple versions back but it works fine now.

Write a comment