Main menu:

Sponsoring

Please consider a small donation:

 

 

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%5B%5D=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%5B%5D=kernel&s%5B%5D=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.

Comment from Alberto
Posted: September 10, 2014 at 15:31

Hi Eric,
I just installed the last version of your pepperflash package (15.0.0.152) and I noticed a weird thing.
In chrome://plugins page I have the following flash version (but the path is the pepper’s one): http://imgur.com/lXLPNzk
I’m using chromium 37.0.2062.94.
Is this normal?

Comment from alienbob
Posted: September 10, 2014 at 23:19

There is nothing wrong with the way the plugin reports its version to web sites. Just check http://www.adobe.com/software/flash/about/
The problem is in the /etc/default/chromium file where I try to determine the flash version. The string in the binary changed so it’s reporting nothing now, and in chroime://plugins that translates to this weird 11..2.999.999 version.

Make sure the version determination string in /etc/default/chromium is changed to:

flashversion=$(strings $flashso|grep “LNX “|sed -e “s/.*LNX //”|sed -e “s/,/./g”)

It’s really only cosmetics, but I refreshed my package anyway to fix this.

Comment from Jerónimo Navarro
Posted: September 15, 2014 at 04:57

Hi Eric, just wanted to ask you if you could update your scripts regarding SimpleScreenRecording. The changes are quite important imo.
Building from git works pretty well, the “simple-build-and-install”+”postinstall” scripts do all the magic (just needed to disable pulseaudio).
Sorry I couldn’t send you proper patches for such an easy task to save you the minutes, I lack knowledge on the topic.

Comment from alienbob
Posted: September 15, 2014 at 10:30

Hi Jerónimo – what scripts should I update and why? And with what/

Eric

Comment from Jerónimo Navarro
Posted: September 15, 2014 at 12:38

The slackbuild from here: http://www.slackware.com/~alien/slackbuilds/simplescreenrecorder/build/
Because it does everything flawless but I get no exec file (notice that it download latest git master when it check the current date). Can’t find the program itself anywhere.
I guess with the “simple-build-and-install” script (diff).
Sorry If it’s me and I’m doing something wrong.

Comment from jr
Posted: September 22, 2014 at 10:47

hi Eric, three (four?) years ago I downloaded a package of yours — Shisen — built without all the (KDE) cruft. I used to love playing it and, having a new 2nd-hand computer, looked to download the game again. alas, cannot find it onsite, search returned no useful results. can you help? thank you.

Comment from alienbob
Posted: September 22, 2014 at 13:10

Hi jr

I never had a “shisen” package separately in my repository. Shisen is part of KDE, can not be shipped separately.
Perhaps you are thinking about another Mahjongg game? In my repository I have xmahjongg (quite old, just a 32-bit Slackware 12.1 package).

Comment from jr
Posted: September 22, 2014 at 13:23

hi Eric, thanks. I played kShisen a few days ago (love these tile matching games) and must have got mixed-up. I’d appreciate an url for the mahjonng game, it’s the one with the flowery(?) background image, right? thank you in advance.

regards, jr.

Comment from JesusM
Posted: October 5, 2014 at 11:52

Hi Eric,

few week ago you talked about the 2.x release of Calibre and the doubts you had about embedding Qt5 libraries or keep them separate. In the meanwhile your Calibre package would remain un-updated. Have you made a choice?

Thanks!

Comment from alienbob
Posted: October 5, 2014 at 11:58

Hi JesusM

I am too busy with work (the kind that earns money) to spend a lot of time on Slackware at this moment. I have decided not to try and build a calibre 2 package for the moment because it needs research time which I do not have right now.

Comment from Joe
Posted: October 11, 2014 at 16:04

Hi Eric,
Thanks for your packages.
I’ve tried your Chromium package on my Slackware-14.0 (release: 37.0.2062.94).

But I noticed the omnibox doesn’t work as usual: if I put there, for example “hello world”… well nothing happens!
I expected to be redirect to:
“w w w . g o o g l e . c o m/search?q=hello world”.

I’ve tried to change search engine and noticed that the matter is in “%s” variabile not expanded regularly.
For example if I create a new serch engine called with following string:

myengineaddress/search?q=%s

Then if I put something in omnibox and press enter, appears the address:
“myengineaddress/search?q=”
…without “%s” expanded.

Now, default search engine string (related to google engine) is made of just variabiles:
“{google:baseURL}search?q=%s{google:originalQueryForSuggestion}{google:assistedQueryStats}{google:searchFieldtrialParameter}{google:bookmarkBarPinned}{google:searchClient}{google:sourceId}{google:instantExtendedEnabledParameter}{google:omniboxStartMarginParameter}ie={inputEncoding}”

So here the answer to why nothing happened when I tried to search something using omnibox.

Can you confirm this release behavior?
Or pheraps could be a my local system matter?

Are you going to update chromium package also for slackware 14.0?

Thanks in advance! 🙂

Comment from 2-tokes over-the-line
Posted: October 29, 2014 at 19:38

Since I recently bought a new laptop I had to upgrade to Slackware current just to get it to boot. Since I did that I thought I’d try your kde upgrade to 4.14.2. Worked fine except for Okular which could no longer read mobipocket format. I had to back out to Slack 14.1 to get it working.

Just to not only complain here… I really really really find your multi-libraries handy. Thank you for that hard work and saving me from the aggravation. 🙂

Comment from alienbob
Posted: October 30, 2014 at 20:19

I looked at your remark about Okular and I have found the culprit.
There is an issue with the order in which some packages are built.
I have fixed that order and the next KDE 4.14 release will have an Okular with mobipocket support.

In the meantime, you could install calibre or FBreader which both support .mobi.

Comment from Paulo Wildson
Posted: October 30, 2014 at 22:18

Hi,
installed package wireshark on my slackware but after installation when I try to run the following error occurs:

bash-4.2 # wireshark
wireshark: error while loading shared libraries: libgnutls.so.26: can not open shared object file: No such file or directory

Can you help me?

Thank you

Comment from alienbob
Posted: October 30, 2014 at 22:47

You probably installed my wireshark package on Slackware 14.1 which I built for Slackware 13.37. The glutls package was updated since Slackware 13.37 and the package needs a recompilation.
You can download the wireshark “build” directory and run the wireshark.SlackBuild script. The package should be available in /tmp when the compilation finished.

Comment from fabio
Posted: November 13, 2014 at 13:54

A request. In a future update of ffmpeg package would it be possible to add libfdk_aac to the encoders? And thank you very much for your hard work. Obrigado!!

Comment from alienbob
Posted: November 13, 2014 at 16:35

Hi fabio, I can do that.

Comment from Inman
Posted: November 15, 2014 at 16:29

hi eric,
i wanted to ask u this question quiet longtime. I have a lenovo t400 and i can recall u use to have the same! … i have always run SC on it, and everything was quiet fine, minor problems but they could be easily fixed … since pat updated “x/*” on July 15, which messed up almost everything. Despite all my efforts i couldn’t get the issue with graphic fixed … openGL got massive problems, the lcd is partially colored with blue or black till refreshing opened windows, VSync cusses freezing and etc … i just wanna know if u have had also the same problem on ur t400? any solution to this? (of course if u still have ur t400!) … and do u know any way to upgrade Slackware Current to the version before July 15? (Just to mentioned i don’t have any of those problem on S14.1)
thank u in advance,
bests

Comment from alienbob
Posted: November 15, 2014 at 23:13

Hi Inman

I still have that T400 and use it daily – it is my main workstation for work and home.
I am running Slackware64-current on it and have never experienced the problems you are describing. Could it be that you missed some new packages that you forgot to install, or else have not deleted some package that was removed in Slackware-current? A properly configured slackpkg will offer to install all missing packages when you run “slackpkg update ; slackpkg install-new”.

By the way, “slackware-current” does not have backup versions. You either have what’s available today, or you have to go back to Slackware 14.1 which is the most recent stable release available.

Comment from R.H.
Posted: November 26, 2014 at 21:16

Thanks for the chromium src scripts. Just a small thing to say. I don’t use printing and so cups is not installed. The chromium build fails when it tries to do the gyp stuff and after a lot of digging I found that I needed to add -Duse_cups=0 and then all worked. I don’t enable NaCL (sodium chloride I use) and I don’t even know what advantage there is using NaCL (other than food tastes better with it, but might be cooks fault and not food’s fault).

Comment from alienbob
Posted: November 26, 2014 at 21:46

When you use one of my scripts to compile a package, I only guarantee its working on a full installation of Slackware, since that is how I build them myself.
NaCl is Google’s Native Client. See https://developer.chrome.com/native-client so you can decide for yourself if this is useful for you.

Comment from R.H.
Posted: November 26, 2014 at 23:57

I understand the full-installation aspect of Slackware and it is a key thing for anyone using Slackware to understand, especially newcomers. I mentioned the cups config in case someone else might stumble into it. Thanks again.
(FWIW I don’t need the NaCL)

Comment from fabio
Posted: November 27, 2014 at 06:39

Just noticed the update on ffmpeg. Thank for the new decoders/encoders. I know you have a real life, and taking the time to include requests was very kind of you.

Comment from Mike Toh
Posted: December 5, 2014 at 15:20

Hi Eric,

RE; ip-address proxying

This was posted from the Mistress of the house’s computer
and if this got through, your explanation of my ISP proxying traffic from my computer through somewhere else, is verified.

Will expand further off-line from your feedback-of-blog.

Regards,

mike.

Comment from Ed
Posted: January 7, 2015 at 19:09

Thanks so much for the great works that you have done. I have been redirected countless times from searches to your works and every time they work!

Thanks again!
Ed

Comment from Gilcio
Posted: January 11, 2015 at 14:48

Hi Eric,
First of all I have to say that you’re one of the main forces that help me to stay and develop using Slackware. I’m running current-64, multilib and a lot of alien packages absolutely updated. I start using qemu and vde networking from your first packages. My present issue is on vde. For some reason rc.vdenetwork (nat option) could not start dnsmasq and serve my qemu VMs. The error message is: “dnsmasq: failed to create listening socket for 10.111.111.254: address already in use”. Could you give me some hint ?
Cheers
Gilcio

Comment from alienbob
Posted: January 11, 2015 at 15:26

Hi Gilcio

It sounds as if you already have a DHCP/DNS server running on your computer.

Comment from Gilcio
Posted: January 11, 2015 at 21:19

You’re right. I did a ps ax | grep dhcp and results: “6476 ? S 0:00 /sbin/dhcpcd -B -K -L -G -c /usr/libexec/nm-dhcp-client.action -h orion eth1” but I have no idea of what program could have started it?. I will look at it in more detail. As always thanks for the fast answer in a sunday afternoon.

Comment from R.H.
Posted: January 11, 2015 at 23:27

How do I make these stop? I get emails but there’s no info on how to make them stop. If I subscribed I made a mistake.

Comment from alienbob
Posted: January 12, 2015 at 12:10

Gilcio – the dhcpcd is the “DHCP client daemon” which manages your computer’s IP address. It is not a DHCP server.
If there is a DHCP server, it will be listening on port 67 and you should find its process with the command (as root): “netstat -panel | grep :67”

Comment from alienbob
Posted: January 12, 2015 at 13:08

R.H. – all the emails you receive from this blog are because you checked a subscription checkbox below one or more articles. I do not send them myself.

The emails you are getting should contain a link that allows you to manage your subscriptions.

Comment from R.H.
Posted: January 13, 2015 at 17:26

I figured out what’s happening. Some emails from your blog show the unsubscribe and some do not.

emails with subject [New comment] do not show the unsubscribe and those with [New post] do.

Comment from JesusM
Posted: January 13, 2015 at 17:31

I can see the unsubscribe link always:

http://i993.photobucket.com/albums/af60/erpopo/AlienPost_zpsc252602b.jpg

Comment from Gilcio
Posted: January 28, 2015 at 04:21

Eric, sorry for a late acknowledge of your answer. I did a fresh reinstall of slack64 current and all my problems disappear. Thanks for your time

Comment from Alex
Posted: January 29, 2015 at 18:23

Eric,
When are you planning to upload patched (CVE-2015-0235) glibc-multilib?

Comment from fabio
Posted: January 29, 2015 at 23:22

Will the updates on glibc (both stable and current) trigger an update in the multilib set? yes, it is a request. thanks Eric.

Comment from MajorLunaC
Posted: January 30, 2015 at 02:08

Yes, please update multilib glibc as soon as you can. It’s a pretty dangerous vulnerability. More details on this and other up-to-date computer vulnerability news:

http://threatpost.com/of-ghost-glibc-vulnerability-patching-and-exploits/110719

Thanks for making multilib! I couldn’t use more than half of what’s out there, if there weren’t this easy multilib setup! 🙂

Comment from alienbob
Posted: January 30, 2015 at 13:57

You guys don’t seem to realize that I do all this Slackware stuff in my spare time. If you start demanding that I must do things I will start demanding money in return.
The updates will arrive as soon as I have time at home to build them.

Comment from fabio
Posted: January 30, 2015 at 14:17

in my defense: 1 – You created the space for requests and 2 i asked politely, not demanded. 3 if i had money you wouldn’t have to demand. It would be my pleasure due to the great work you do for us all. sorry to bother man, but you are always so fast that we grew spoiled hehe.

Comment from alienbob
Posted: January 30, 2015 at 14:49

Requets for new stuff is one thing. Requests to work faster is not acceptible to me. Yes, you were polite about it, fabio, and it was on the planning list anyway. My comment was more directed at Alex and MajorLunaC – I am well aware of glibc updates. This GHOST vulnerability is hard to exploit, actually there are no real-life exploits yet (apart from one for Exim which Slackware does not ship). You should try not to be so paranoid. And if you are, you know where the source code is.

Comment from MajorLunaC
Posted: January 31, 2015 at 04:05

Wow. So the words “please”, “as soon as you can”, and “Thanks” now mean “Work faster slave! Right now, damit!” in modern internet lingo? Let me interpret for those who think everyone is demanding instant results for a completely free repository made in spare time, and that everyone is ready to take a bite out of you. Maybe we use different dictionaries:

“please” = “I beg of you”. “I ask of you kindly”. Even “I seek your help”.

“as soon as you can” = “Whenever you are willing and able”. “I now you work hard, and you do in your spare luxury time in which you could be having fun, so if you happen to find the time, anytime in the distant future”. “Whenever you see fit”.

“Thanks” = “I am in your debt”. “I really appreciate it”. “I don’t think I could have done it without you”.

**As for your comments:

“I am well aware of glibc updates”: First I’ve heard you mention it.

“it was on the planning list anyway”: I would love to see that list. If I had known you knew of it and it was set to be updated, I would never have posted except a “Thank You for such a quick fix! Nice Work! You work too hard! Take it easy!”

“actually there are no real-life exploits yet”: A vulnerability is a vulnerability, no matter how small it is. In my opinion, vulnerabilities get their own level of priority far above anything else. Disclosure of the vulnerability increases the chance that someone will try to exploit it 10 fold or more, which is why vulnerabilities are usually disclosed privately, quite some time before the public disclosure, to those who can and do fix them. Once the vulnerability is publicly popularized, new ways to exploit it are often explored.

I need to come up with something to say to those who consider me paranoid, like “Wait till you see what I got off your computer …”

Comment from fabio
Posted: January 31, 2015 at 09:14

now that i saw the guy before me had asked the same, i fell quite stupid for posting before reading everything. As for the vulnerability itself, my primary concern was about getting the applications that rely on multilib working again, since few mortals have the solid knowledge in programming to really exploit it. Thanks for the updates and as for me, will wait quietly next time.

Comment from alienbob
Posted: January 31, 2015 at 13:13

MajorLunaC, and a good day to you too.

Actually, no one gets to see my TODO list. And if you would go looking at historical data of the multilib ChangeLog.txt you would notice that I am usually only hours or a day behind on Slackware proper. However, these were glib updates for 13.37, 14.0 and 14.1 combined with the KDE5 which cost me six weeks of multile hours per day work. At some point there is a decision to make about the balance of hobby work (which this is) and tending to family. The multilib glibc updates would come, if you were doubting that, you are quite new to Slackware and this community.

As for vulnerabilities: they are real but overrated. A vulnerability must be exploitable to be a vulnerability. And exploitable does not mean that it is exploitable _on Slackware_

Nevertheless, if it bothers you (and I respect your point of view) there is always the option to go back to Slackware’s patched glibc – temporarily – until the time that I release new multilib versions. All you lose is the capability to run 32-bit programs. You gain peace of mind by knowing your system is patched against a vulnerability.

Finally: you do not get so say what I have to do, unless you are my employer. And when you do, even if accompanied with please and thank you – you can rub me the wrong way if I just came home from a bad day at work and don’t need more people on my back.
End of statement.

Comment from fabio
Posted: March 1, 2015 at 11:18

Quick suggestion for when you get the time (if you feel like doing it, of course). A bump on LXQT to the 0.9 version. And thanks for the 0.7 version. Excellent for “reviving” old machines with slackware.

Comment from alienbob
Posted: March 1, 2015 at 12:38

Hi fabio

Building LxQt 0.9 is somewhere on my TODO. Their migration to Qt 5 and (some) KDE Frameworks made the update non-trivial and I wanted a stable KDE 5 before looking closer at LxQt.

Comment from KG
Posted: April 10, 2015 at 08:43

First of all a heartfelt thanks for your sterling work producing reliable slackware packages 🙂

However, your latest vlc package (2.2.0) doesn’t handle HD (720p and above) as well as the older 2.1.5 version: video stutters or freezes.
I downgraded to your 2.1.4 package (in the slackware-14.0 repo) and everything was back to normal.
I know that building vlc packages is a PITA. It could also be that my slightly outdated hardware could cause the malfunctioning. Still, if you can find the time to look into it, it would be highly appreciated.

Comment from alienbob
Posted: April 10, 2015 at 12:54

Hi KG

Start “vlc -vv” (or with one v, or with three, depending on the amount of debug info you need) and see if there are any hardware acceleration related errors when you play a video.
I have no problems with playback of HD video here.

Comment from KG
Posted: April 10, 2015 at 15:02

Hi Eric and thanks for a swift reply!

Embarrasing: after a new upgrade, the videoclip that caused trouble yesterday ran OK…

vlc -vv creates a huge amount of info, and repeated entries like this:
“[b5487e98] avcodec decoder warning: More than 4 late frames, dropping frame
[h264 @ 0xb549cf40] Frame num gap 19 17”

Maybe it should be put down to hardware. I’m on an old netbook with a Celeron processor, and when playing the HD clip in question the CPU load is as high as 80%. No wonder if there’s a bit of stuttering.

So for now I’ll stick to the latest version 🙂

Comment from Bryan Glunt
Posted: April 17, 2015 at 18:08

diff for new version of google-chrome.SlackBuild

77c77
ar p $CWD/google-chrome-${RELEASE}_current_${DEBARCH}.deb data.tar.lzma | lzma -d | tar xv || exit 1

Comment from alienbob
Posted: April 17, 2015 at 20:59

Hi Bryan

The recent debian packages are using xz compresson instead of lzma compression. The file is now called data.tar.xz.
The google-chrome.SlackBuild in slackware-current was updated for this, early March 2015.

Comment from Brian
Posted: April 18, 2015 at 08:07

Is there any chance that the latest “slackware-current” might no longer work with the files you have in the “current” directory of the multilib feed? I have been doing multilib upgrades with your packages for quite a while, but now when I run everything–with a fresh download and the same commands as before, glibc seems to get hosed, and the system is then unusable. I’ve tried twice, both times with the same result–can’t get at any commands and have to start the install over.

Comment from alienbob
Posted: April 18, 2015 at 14:27

Hi Brian

The multilib packages in the “current” directory of my repository are the ones for slackware-current as you can download it from any Slackware mirror. Check the package versions and BUILD numbers, they should match the versions of Slackware64-current (except my packages have the “alien” tag added to the BUILD number).
Can you double-check that you are indeed downloading the right packages, and that they have not been corrupted?
If you can’t find what’s wrong perhaps you can share:
– where you are downloading those packages
– what their md5sums are
– whether the gpg check is OK
– what commands you are using to upgrade glibc and in which order you issue these commands.

Comment from David
Posted: April 22, 2015 at 14:58

Hi
Mirror contain “deleted” package after huge update (20150421)
eg:
http://taper.alienbase.nl/mirrors/slackware/slackware64-current/slackware64/k/
contain kernel source 4.14.33 and 4.18.11
same kde 4.10.5 amd 4.14.x

same type of thing in the iso
http://taper.alienbase.nl/mirrors/slackware/slackware64-current-iso/

Comment from alienbob
Posted: April 22, 2015 at 15:59

Hi David

The primary mirror which I use is http://slackware.osuosl.org/slackware64-current/source and its contents are correct.
However the rsync URI which is rsync.osuosl.org::slackware/slackware64-current/ does not offer the same content: it still shows the old packages which should have been removed.
I use the rsync URI which is why my taper mirror shows all these redundant packages.

I am sure that this is an initial sync issue and that the primary mirror will be sanitized soon. Then taper’s contents will go back to normal too.

Comment from cwizardone
Posted: April 22, 2015 at 17:55

Good Afternoon,
Early this morning, my time, I went to download your latest -current iso and noticed it was 4.3 gigs in size.
Is that correct? I had thought the size of the iso had been reduced to somewhere over 2 gigs?
Thanks.

Comment from alienbob
Posted: April 22, 2015 at 19:48

cwizardone, it takes time to properly sync the mirrors. And if you sync at the same time it’s possible to get the old AND the new packages all together…
My taoer mirror had that issue, and as a result that ISO image also contained all the original as well as the updated and new packages, causing the filesize to explode
The mirror has been re-synced and the ISO re-created. It is now a proper 2.6 GB in size.

Comment from R.H.
Posted: April 23, 2015 at 20:26

1st off, thanks alienbob.

Since we’re on the topic of multilib is there an https location for multilib files? I did look around and try some urls but none worked. I wonder if osuosl or kernel.org would or could do that hosting.

hey also I see you’re a sci-fi reader & collector, I have some and would be willing to donate one to you if interested. I have pohl, poul, lem, asimov, et.al. I could ship it whatever’s cheapest i can find to anywhere that usps goes I guess.

Comment from alienbob
Posted: April 23, 2015 at 22:35

Hi R.H.

Currently there is no https:// URL for download of multilib files that I am aware of. Downloading packages over HTTPS only adds strain to the server because it has to encrypt all the data. It adds no security… if you want to have security you can use the GPG signature files to verify your downloads.
Thanks for your offer to donate a Sci-Fi book but I think it will cost you too much in shipping. I have a wall full of books and no room anymore 😉 I switched to reading e-books because that is space-saving.

Comment from fabio
Posted: April 24, 2015 at 00:19

Just to inform, Libreoffice won’t start after the last batch upgrades on -current.
symbol lookup error: /usr/lib64/libreoffice/program/libi18nutil.so: undefined symbol

as well as other libs missing. Thanks for your work on the updates!

Comment from alienbob
Posted: April 24, 2015 at 09:35

Hi fabio, I know. I have new (and working!) 64-bit LibreOffice packages ready and the 32-bit package is still compiling (will take the rest of the day while I am at work).

Comment from fabio
Posted: April 27, 2015 at 06:03

Your speed is amazing man!!! libreoffice working perfectly. I know it’s minor and the focus now is kde5 but just to inform, in kde settings on -current it’s impossible to get new themes and window decorations, by clicking the option an API error occurs. Thanks again for the lightning fast libreoffice packages.

Comment from Brian
Posted: April 27, 2015 at 06:10

Note on my email of April 18:

I just fetched a new slackware-current ISO over the weekend, and using your guide’s lftp URL things worked perfectly. So it must have been some kind of hysteresis in the two feeds at the time I was doing my previous work.

Thanks for your wonderful work!

Comment from fabio
Posted: April 29, 2015 at 03:13

about kde themes not working, if someone got the same. Just delete .kde folder in your home. worked for me. sorry about the noise early.

Comment from Xylemon
Posted: May 4, 2015 at 09:35

Dear Alien,

Thank you for all your great packages and work on Slackware. I have two questions about some of the packages you host:

First one is regarding Chromium. I use Chromium mainly for Netflix and some other small audio related things (works very well with ALSA emulation), but I’ve been unable to use it for a month or two now due to an unexplained “Segmentation Fault” on any webpage load. I’ve tried several different new versions, deleted all Chromium config files, and even with an upgraded kernel (I’m now on 3.18.11) it still segfaults. Any idea what could be the cause?

Second question I have is regarding the multilib versions of Mesa. I recently have been trying out the nouveau drivers because they bring a lot of nice features that the nVidia drivers don’t and in combination with the new kernel, they now work great with my laptop. However, the problem is that despite the 64 bit versions of Mesa packages for Slackware are OpenGL 3.0, the 32-bit packages spit out OpenGL 1.4. This is very annoying considering that Source games can’t even run with such an old version, and Wine always uses the 32 bit version of Mesa even in 64 bit prefixes. Is there anyway to get the 32 bit libraries to utilize OpenGL 3.0?

Appreciate any help or response. Thanks.

Comment from alienbob
Posted: May 4, 2015 at 12:17

Hi Xylemon

You don’t tell what version of Slackware you are running, and on what type of hardware. If Chromium segfaults for you, perhaps you are able to attach a debugger to the session to get a backttrace? Or else, try adding the commandline parameter “–bwsi” to Chromium (“browse without sign in” which is Guest Mode with disabled extensions). If that makes Chromium run again, it may be one of your extensions which is causing the crash.

About your OpenGL question – you do not provide any example commands that you’ve tried inclusing literal copy/paste of the command output. I can not start guessing at what’s happening.

Comment from Xylemon
Posted: May 5, 2015 at 17:12

Thanks for the reply,

I am on Slackware 14.1 64-bit with Kernel 3.18.11 and I generally use the current packages with your multilib repo. I have a GT 755M card, and this is the rest of my system specs: http://shop.lenovo.com/us/en/laptops/lenovo/y-series/y510p/#tab-tech_specs

Regarding Chromium, I have tried removing any type of configuration file and install. Trying it with “-bwsi” has no effect. I’ll look into a backtrace or debugging soon. If it’s worth anything, I think the problem started when that version released which supposedly did not work on 3.10 kernels or something of the sort.

On the Mesa/OpenGL topic, the info I get regarding the 32 bit version of Mesa is this:

/usr/bin/32/glxinfo | grep “OpenGL”

Which in return spits out:

libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL version string: 1.4 (3.0 Mesa 10.5.3)
OpenGL extensions:

From what I understand, I should see 3.0 for the OpenGL version just like what the 64 bit version of glxinfo spits out:

OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.5.3
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.5.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.5.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

Hope this is more insightful than my last comment.

Comment from JesusM
Posted: June 6, 2015 at 07:38

Hi Eric,

surely it is my mistake, but I dont’ see where …

you have announced Calibre 2x for both Slackware 14.1 and -current. Indeed, today I saw at the RSS channel the notice for Calibre 2.30.

But when I try to update using ‘slackpkg update’ I still see Calibre 1.48.

I did update to Calibre 2.28 by downloading directly your pack from the repository, not using ‘slackpkg’.

What am I doing wrong?

Thanks once mor time for your job!

Comment from alienbob
Posted: June 6, 2015 at 11:08

Hi JesusM,

I guess it is an issue with slackpkg, because the newer calibre package is there in the 14.1 repository, next to the 1.x version of the package.

To end the confusion, I will rename the calibre-1 package for Slackware 14.1 to “calibre1” like I did in the slackware-current repository.

Comment from senecum
Posted: June 7, 2015 at 04:59

Howdy AlienBob

Sorry for posting my question on “Parental control on the Linux desktop”…I misunderstood you statement above(“This is not meant to be a replacement for…). I stand corrected.

To the point. I often worry about the timeliness of many articles seen on the web with the fast pace of change that we live in. Your post on creating a safety net for our children is wonderful and meets my expectations quite well. Wishing to avoid a false sense of security, however, before implementing your suggestions I was wondering if there is anything you would change or add six years later, if that is in fact when you wrote the post.

So, any comments, changes, suggestions?

Comment from alienbob
Posted: June 7, 2015 at 14:38

Hi senecum,

My son grew up in those six years so I am no longer using parental control, but the concept is unchanged and the software you can use is also still the same.
The most recent release of tinyproxy is four years ago, but a lack of new releases does not mean that the sofware has become unusable or unfit. Some programs work well enough, especially if they are small and focused on one task, that they do not require a continuation of upgrades. Just comple the most recent version of tinyproxy for your computer and try it out.
Squid is the bigger brother of tinyproxy and of course you can consider that as an alternive – it’s just a bit more complex to setup.
Dansguardian or squidguard are the programs that do the actual content checking and filtering, those are still current.
If you implement this solution yourself and find that the article needs a refresher or requires fixing, please let me know so we can discuss it; or leave your comments in the “talk” section of the Wiki page. Credit where credit is due of course.

Comment from senecum
Posted: June 8, 2015 at 05:35

Thank you, AlienBob – I would say Eric but I like AlienBob too much… every time I see the name the tune from Sponge Bob invades my senses, I get “happy feet” and brings a smile to my face, a side effect of having small kids :⁾)

I will let you know if I come across any issues that need your attention.

Best

Comment from senecum
Posted: June 8, 2015 at 11:02

Howdy, again AlienBob

In the spirit of trying to give something back, unable to offer anything else of value, I want to share this great little gem I came across today (the performance, not the song itself, which is well known already). I hope it will be of your liking and that it will shed some sunlight on those “rainy days”, or after one of those “wonderful” days at work…

https://www.youtube.com/watch?v=rEi9dscAOm8

Best
P.S. the blog includes “life and everything” so I hope this post is not terribly inappropriate…delete at your discretion if it is.

Comment from Chris
Posted: June 18, 2015 at 19:49

Hi Eric,
I am very impressed, that you have mastered integrating the WideVine-Plugin into the Open-Source Chromium browser, and even to playback Netflix videos!!
So, I am trying to do the same for my Raspberry Pi (with Raspbian OS). The official Chrome browser does not work there, because it is not built for ARM architecture.
Chromium does work, but without the EME extensions.
So, do you have any tipps for me how to get it working on the Raspi, or even could provide a ARM build of your WideVine plugin?
Would be greatly appreciated 😉
Cheers, Chris

Comment from alienbob
Posted: June 19, 2015 at 11:00

Hi Chris

I do not think that’s going to work. I do not compile the Widevine CDM library, becuuse that is a piece of closed-source technology. What I do is compile the “adapter library” which interfaces Chromium with the Widevine Content Decryption Module. The Widevine CDM itself is then extracted from the official Google Chrome RPM binary.
For an ARM platform, you will require a binary Widevine CDM library which is made available by Google.
ChromeOS is available for ARM (my Samsung Chromebook runs it) so there *is* a version of Chrome that works on ARM. I have no idea (never tested) if Netflix works on the Chromebook, but if it works it might be possible to extract the Widevine libraries from the ARM archive of Chrome.

Comment from Chris
Posted: June 19, 2015 at 16:27

Thanks for your help!
I found some useful information on how to extract the Widevine plugin for ARM architecture here:
https://stackoverflow.com/questions/30732428/extract-files-from-chrome-os-chromebook-recovery-image

But what to do next??
– Which binary files are needed exactly?
– How to include them into the Chromium ARM build? (Therefore I would need your “adapter library”, right?

Comment from Eduardo
Posted: June 23, 2015 at 14:41

Hi Eric,
I would like to report that something went wrong with your latest Chromium release (the one without the OK Google binary blob, v. 43.0.2357.125-x86_64-2alien)

Chromium suddenly appeared big and blurry, as if I were using a 800×600 screen. Totally ugly.

Only after launching Chromium with the ‘–force-device-scale-factor=1’ gives me a normal appearance.

For the record, I am not enlarging or forcing any scaling on the display at all. All previous Chromium versions looked fine.

Thank you again for all your efforts.

Comment from alienbob
Posted: June 23, 2015 at 20:12

Eduardo, the only change to the package is the patch to remove the hotwording feature. No other changes were introduced to the SlackBuild, the source code remained the same.
It’s weird that for this release, the Key Fix was:
“[498426] Resolved browser font magnification/scaling issue.”

It appears that this bug was not properly fixed. If you read recent comments (of some hours ago) in https://code.google.com/p/chromium/issues/detail?id=498426 you’ll notice that even the newest stable release which I am still compiling (will take until tomorrow) still has this scaling bug.

Comment from Eduardo
Posted: June 23, 2015 at 23:16

It’s weird indeed Eric. Thanks for your help.

Comment from websafe
Posted: June 26, 2015 at 01:52

@alienbob Please check here https://github.com/dslackw/slpkg/issues/22 is the chromium package listed twice in http://www.slackware.com/~alien/slackbuilds/PACKAGES.TXT

Comment from alienbob
Posted: June 26, 2015 at 08:54

Hi websafe. I do not see any issue on my side. I updated that bug report with a comment.

Comment from Ed
Posted: July 1, 2015 at 08:05

Hey Eric,

I just wanted to drop you a note that I am having problems accessing your slackbuild repository at http://www.slackware.com/~alien/slackbuilds/.

*Edit
Sorry I guess that is all of slackware.com.

Comment from alienbob
Posted: July 1, 2015 at 09:54

Hi Ed

Yes, there was an issue with the interaction between the slackware.com server and the Akamai contentserving front-end. We had to reboot the server in order to fix that. Should be OK now.

Comment from Ed
Posted: July 1, 2015 at 17:55

Yes, perfect. Thank you!

Ed

Comment from tard eo
Posted: July 1, 2015 at 22:55

alienbob,
thank you for all your great work….

Comment from Ed
Posted: July 13, 2015 at 00:54

Hi again Eric,

What is the possibility of getting you to look at building VeraCrypt for Slackware-current?

Comment from alienbob
Posted: July 13, 2015 at 23:07

Hi Ed.

I can do that.
In fact, I have just done so… veracrypt packages uploaded to the repository. Please tell me if they work.
Note that I added not just the veracrypt binary (the combined gui/console program which links against a lot of X libraries) but also a pure console binary “veracrypt-nox” which does not link against any X libraries at all and therefore can be used on headless servers that have no X installed.

Comment from Ed
Posted: July 14, 2015 at 01:12

Wow, thanks a lot!

I have installed it on -current/MATE and it works great! (Using GUI)

I have never experienced support like that which you give for Slackware. I am going to be making a donation to you and PV soon!

Comment from cwizardone
Posted: July 14, 2015 at 14:35

@ Alien Bob,
Many Thanks for the Veracrypt package!!!
Greatly appreciated.

Comment from Darren Drapkin
Posted: July 17, 2015 at 16:45

I am writing to report a bug in konqueror 4.14.6 in slackware64 current. I go to my wordpress.com admin page, then to the “freshly pressed” page, and soon after the browser crashes.

Comment from alienbob
Posted: July 17, 2015 at 21:19

Hi Darren

You should create a bug report in the KDE bug tracker instead. I do not solve application crashes.

Comment from Alex
Posted: July 19, 2015 at 23:05

Hello! The multilib openssl and openssl-solibs were not upgraded to correspond 64-bit versions.
Best regards and many thanks!

Comment from cwizardone
Posted: July 20, 2015 at 20:49

@Alex,
That is one of the easier things to do yourself, Download the 486, actually, I think they are labeled, 586, and follow the instructions here,
http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib

The information is about 1/2 way down the page.

Comment from Alex
Posted: July 21, 2015 at 11:23

@cwizardone, thank you for the link. In any case, alienbob already upgraded multilib.

Comment from antuan
Posted: July 24, 2015 at 16:10

Question about qemu

I installed Slack current from your repository, and it works very fine. thanks for that.
I would like to have virtualization env, and for that i installed latest qemu and virt-manager packages from Slackbuild. that works, but seems a more complicated and i have some problems with networking.
I read your wiki pages about qemu and Hardware virtualization with QEMU, but there’s some dead links to your packages. So can you tell me if theses howto are applicables for current Slackware.

Thanks in advance

Comment from alienbob
Posted: July 24, 2015 at 20:50

Hi antuan –

Years ago I changed the package name in my repository from qemu to qem-kvm to indicate that this fork of qemu was the one to be used instead of qemu itself. Looking back at my archive, I had packaged qemu-1.3.0 in December 2012 because that was the first release of QEMU that incorporates all the improvements of qemu-kvm. And then apparently I never released that qemu-1.3.0 package. I cannot remember why… and I am still using qemu-kvm-1.2.0 here at home.

Essentially I am still using QEMU (read: qemu-kvm) as explained on that Wiki page. The server running the virtual machines is Slackware 13.37 however – not slackware-current.

This blog is not the best medium for troubleshooting sessions. I think it may be better to open a thread on http://www.linuxquestions.org/questions/slackware-14/

Comment from antuan
Posted: July 26, 2015 at 19:44

Hi Alienbob

I resolve all with Slackbuilds from repository and every thing works perfect. I just have one Question. Do you know how to do for getting updated queues file for sbopkg. Link to Gitorious don’t work at all.
And just one word to say to you that appreciate very well your work. Just Fine.

Regards

Comment from alienbob
Posted: July 26, 2015 at 22:52

Hi antuna

The gitorious repository for queue files is no longer available, but you can use a script which is part of sbopkg (youy can find it in the contribs directory): sqg or “sbopkg queuefile generator”.
More information about how to use sqg to generate queuefiles is here: http://slackblogs.blogspot.nl/2014/01/managing-sbo-dependencies-easily.html

Comment from antuan
Posted: July 26, 2015 at 23:40

It was under my eyes and i don’t seen it, thanks

Comment from antuan
Posted: August 7, 2015 at 13:40

Hi Eric,

can you tell me if your article on qemu is of actuality. if yes, I don’t understood which packets must be installed due to dead links. I already have intalled qemu and virt-manager since slackbuilds, but I would like to try your resolution with vde. this seems more less complicated to set up. Nowadays my install works but with some problemes as for the resolutions of addresses with dnsmask and avahi which I which i cannot resolve..
Could you just to say to me quickly how you would be taken you there?

Regards

Comment from alienbob
Posted: August 7, 2015 at 22:02

antuan, the combination of qemu and vde is what I still use, every day, when I compile a package in one of my virtual machines.
I do not use a version of qemu which needs libvirt or even avahi (how would qemu require avahi??).

Comment from antuan
Posted: August 8, 2015 at 12:39

Yes, concerning avahi, i quickly deleted it. I realized by consulting my syslog. Dnsmask done the job rather well, i had incorrectly configured it at the outset. Therefore everything is back in order. But I come back to my first question; if I want to go by your solution, what do I need to install? And then, why don’t you do you serve not libvirt?

Comment from gauchao
Posted: August 18, 2015 at 11:22

HI Eric. Regarding the last packages for qbittorrent and libtorrentrasterbar (Aug 17th 2015) I have noticed that the column with FILENAMES has disappeared on qbittorrent. Would it be a bug? I have Qt5 as recommended and didn’t have this problem with the previous versions of qbittorrent. Thank you for your time.

Comment from alienbob
Posted: August 18, 2015 at 12:15

the “Name” column disappeared from the default view indeed. Right-click the column headers and place a checkmark in the box next to Name”, that will make the “Name” column re-appear.
You might want to open a bug report to ask the developer to restore the old default.

Comment from gauchao
Posted: August 18, 2015 at 13:01

Thank you, Eric. I will do it.

Comment from orbea
Posted: September 1, 2015 at 20:31

Using slackyd -d installed from SBo I noticed a possible problem with one of your current mulitlib packages.

libssl.so.0 required by:
–> Package: aaa_elflibs-compat32-14.2-x86_64-1compat32 (/usr/lib/libcurl.so.2.0.2)
–> Package: aaa_elflibs-compat32-14.2-x86_64-1compat32 (/usr/lib/libcurl.so.3.0.0)
libcrypto.so.0 required by:
–> Package: aaa_elflibs-compat32-14.2-x86_64-1compat32 (/usr/lib/libcurl.so.2.0.2)
–> Package: aaa_elflibs-compat32-14.2-x86_64-1compat32 (/usr/lib/libcurl.so.3.0.0)

What are the implications of this?

-d does “-d: Search missing shared libraries of installed packages.”, more info about slackyd can be found in the link below:
http://old.slax.org/forum.php?action=view&parentID=75894

Comment from alienbob
Posted: September 2, 2015 at 10:23

Hi orbea

Your question has been addressed in yesterday’s -current update:

Tue Sep 1 23:29:22 UTC 2015
a/aaa_elflibs-14.2-x86_64-2.txz: Rebuilt.

Please read the remarks about the reasons why you should not always update your aaa_elflibs if you are running slackware-current:

http://www.slackware.com/~mozes/docs/aaa_elflibs.txt

Comment from orbea
Posted: September 2, 2015 at 15:06

Thanks for the reply and helpful link, I have read it before and have been only updating aaa_elflibs during the bigger updates when Pat updates it.

Comment from Geremia
Posted: September 6, 2015 at 01:36

The KWalletManager5 doesn’t show any of my wallets.

Comment from alienbob
Posted: September 6, 2015 at 10:22

Geremia, I have several blog posts specifically about KDE5. Please discuss anything related to KDE5 in the comments section of a KDE5 post and not in the general feedback.
By the way, my kwalletmanager5 shows (and uses) my single wallet. Never used more than one.

Comment from fabio
Posted: September 18, 2015 at 09:23

Hi Eric. Looking at the packages i noticed -current ships with fluxbox 1.3.7 (the latest) and 14.1 ships with 1.3.5 (two releases behind). would it be possible a slackbuild of 1.3.7 for 14.1? thanks for your time and efforts.

Comment from alienbob
Posted: September 18, 2015 at 09:51

Hi fabio.

Slackware releases only get critical security updates in their /patches directory. A newer version of fluxbox for Slackware 14.1 is something you’ll have to compile yourself.

Comment from carlosmoura
Posted: September 19, 2015 at 15:24

Hello Eric, I have been reading the post “feedback” of your blog and I have learned that there are difficulties in communication when using translators of languages for the comments.I also use these translators because they don’t know English writing,read until I can but to speak and write I have no security or training good. However I see that I am using now is of good quality and I will continue to comment on using the translations but if it is difficult to understand let me know that I will try another solution

Comment from luca
Posted: September 21, 2015 at 13:57

Hello Eric,
your ffmpeg package is just awesome.
The only thing it misses, IMHO, is ssl support. For example, mpv cannot play youtube videos if ffmpeg doesn’t support ssl (and, in general, all https urls). I always need to compile ffmpeg for this very reason.

Have you ever considered building it with ssl enabled? I know openssl is not feasible due to licensing problem, but what about using gnutls instead (like Arch does, for example)?

Thanks!

Comment from alienbob
Posted: September 22, 2015 at 14:50

Hi luca

What would be needed in the SlackBuild script to add SSL support to the ffmpeg package? I have not consciously left this out, I just had not realized that this was something people could need.
Don’t worry about licensing issues, I will take openssl or gnutls, whatever is most useful.

Comment from luca
Posted: September 22, 2015 at 16:46

Hello Eric,
thanks for the quick response.

it just takes to pass “–enable-gnutls” to configure to enable gnutls and “–enable-openssl” and “–enable-nonfree” for openssl.
So I think it will be forced to stay in the restricted repository if openssl is used.

I think the two are equivalent in term of functionality.

Comment from alienbob
Posted: September 22, 2015 at 20:32

Hi luca

That will indeed be easy to add, and it also allows to compare openssl with gnutls if I add openssl only to the restricted build.
Good idea.

Comment from Alex Kempshall
Posted: October 19, 2015 at 09:02

Hello Eric

I’ve noticed that your SlackBuild for Libreoffice 5.0.2.2 in Slackware Current includes a patch to exclude the test CppunitTest_sc_ucalc.

The failure of this test can also be replicated in calc from the GUI by following these steps –

1.
Start Calc

2.
Select a range of cells from G4 to G10

3.
Edit -> Fill -> Series

4.
Push the radio button

5.
Start Value: 5

6.
Increment: 2

7.
Expected results 5, 10, 20, 40, 80, 160, 320 in cells G4 thru G10

8.
Edit -> Undo:Fill

9.
All cells in G4 thru G10 range should now empty

I have observed the following –

A.
In LO 4.4.5 in Slackware 14.1 the above test passes

B.
In your version of LO 5.0.2.2 in Slackware Current the test fails.

C.
Using the SBO version of LO 5.0.2.2 in Slackware Current the test passes.

D.
If I compile from GIT in Slackware Current the test fails.

E.
If I compile from GIT In Lubuntu 14:04 the test passes.

Any thoughts on what might me missing in Slackware Current that might be causing this problem.

Alex

Comment from alienbob
Posted: October 19, 2015 at 11:44

Alex, interesting issue. Indeed I could not make the compilation finish unless I disabled the unittest for sc_ucalc.
I noticed that the Fedora SPEC file for libreoffice (http://pkgs.fedoraproject.org/cgit/libreoffice.git/tree/libreoffice.spec) mentions “system mdds 0.10.3 causes a crash in sc_ucalc unit test” but Slackware does not have mdds and my build uses the mdds tarball which libreoffice downloads.
Perhaps you find the cause yourself, in that case let me know. Otherwise I will re-visit this issue when LO 5.0.3 gets released.

Comment from Alex Kempshall
Posted: October 21, 2015 at 16:25

Eric

OK, I’ll bisect the code.

Firstly, I was wrong about stating that LO 4.4.5 in Slackware 14.1 passes it in fact fails!

What does pass is 4.3.0.3 whereas 4.4.0.3 fails.

As you can appreciate, if I do find an answer it will take some time to discover as at each bisect point I have to recompile. Can’t think of any shortcuts.

Alex

Comment from Alex Kempshall
Posted: October 24, 2015 at 06:11

The results of the bisect, which appears to be in the right ballpark, are –

8e4dc1d760d85e09bbc3f3bbb5b8be2947db1b63 is the first bad commit
commit 8e4dc1d760d85e09bbc3f3bbb5b8be2947db1b63
Author: Noel Grandin
Date: Fri Aug 22 15:15:17 2014 +0200

create type-safe bitfield for sc insert/delete flags

The most important part of the change is in sc/inc/global.hxx

It creates a type-safe struct that prevents the accidental interaction
between regular integer types and the flags struct.
It also provides utility methods that make combining and testing the
flags type-safe.

Change-Id: Ibc5b20058b1655df913490682b679afd1297b36d
Reviewed-on: https://gerrit.libreoffice.org/11071
Reviewed-by: Eike Rathke
Tested-by: Eike Rathke

:040000 040000 f9f6a67e9269712bb1997ee6ba9fb49d21e4455e 494c585ff088b7980af64f28e556a58b2afcc35b M sc

Comment from Alex Kempshall
Posted: October 27, 2015 at 10:39

Eric

I posted a message reporting my findings to the Libreoffice developers list on 24/10/2015 regarding the patch “create type-safe bitfield for sc insert/delete flags” not working on Slackware but was working on Lubuntu.

Low and behold a complete rewrite of the patch appeared 2 days later 26/10/2015 called “convert InsertDeleteFlags to use o3tl::typed_flags”.

I’ve compiled and tested in master. Now all tests pass in Slackware. Can’t find a bug report for it so don’t know what version of LO will end up with the patch.

Alex

Comment from alienbob
Posted: October 27, 2015 at 12:04

Hi Alex,
That was a fast fix!
I will check the next release to see if this patch has been applied or else I can apply it myself.
LO 5.0.3 should be released very soon according to https://wiki.documentfoundation.org/ReleasePlan/5.0#5.0.3_release

Comment from Alex Kempshall
Posted: October 27, 2015 at 15:27

Hi Eric

Not quite out of the woods yet.

Tracked down 2 regressions in LO 5.0.2 still got two more to go before I can move off of LO 4.4.5.

The one here was quite trivial, the other three are show stoppers for me.

One I’ve raised a bug for and that’s been fixed – 93618.

One of the unreported bugs locks up my virtual machine in virtual box. Have to go to tty1 to kill it.

Every time they bring out a major release my base application stops working. The bugs get fixed by about x.0.4, If I report them that is.

Alex

Comment from Renars
Posted: October 29, 2015 at 06:22

Hello Eric.

Yesturday I had odd stoper when tryed to update slackware 14.1 x86_64. After both apr*txz packages in xterm shows somthing was gine wrong and there is no /bin/sh. After that system just become dead. I reinstalled compleatly system and trayed agayn update and got same result. 🙁 So for now I instaled slackware64-current.

I wonders is this issue just striked me?

P.S but anyway thanks for grate and stable distro. 🙂

Comment from alienbob
Posted: October 29, 2015 at 10:10

Hi Renars
What was the Slackware mirror where you got your slackware64-14.1 packages from? This issue should not occur with the packages in the slackware64-14.1 tree unless the package tree got corrupted.
Unless you mistakenly used a 32-bit package repository when installing these updates, instead of the required 64-bit repository.

Comment from Renars
Posted: October 29, 2015 at 18:14

Shame on me!!! 🙁 I really mistakenly used 32bit packages. Well than tahnx for Your time and effort to answer for so fullish mistakes 🙂

Comment from Jeffrey
Posted: November 5, 2015 at 21:03

KDE 5 is running fine here, thank you for this much of work!

Comment from Thomas Jett
Posted: November 7, 2015 at 08:42

Hello, I just finished trying to build your SlackBuild for ffmpeg. It seems like it’s got some problems. I’ll paste in the last part of the terminal output so perhaps that will be of some help. I think this is the first one of your SlackBuilds that hasn’t compiled for me. Hope this helps.

Oh, btw, I downloaded everything in the build directory and kept the directory structure exactly the same as you have it on the site.

make[1]: Leaving directory `/tmp/build/tmp-ffmpeg/zvbi-0.2.35/po’
Making install in doc
make[1]: Entering directory `/tmp/build/tmp-ffmpeg/zvbi-0.2.35/doc’
make[2]: Entering directory `/tmp/build/tmp-ffmpeg/zvbi-0.2.35/doc’
make[2]: Nothing to be done for `install-exec-am’.
make[2]: Nothing to be done for `install-data-am’.
make[2]: Leaving directory `/tmp/build/tmp-ffmpeg/zvbi-0.2.35/doc’
make[1]: Leaving directory `/tmp/build/tmp-ffmpeg/zvbi-0.2.35/doc’
make[1]: Entering directory `/tmp/build/tmp-ffmpeg/zvbi-0.2.35′
make[2]: Entering directory `/tmp/build/tmp-ffmpeg/zvbi-0.2.35′
make[2]: Nothing to be done for `install-exec-am’.
test -z “/tmp/build/tmp-ffmpeg/ffmpegdeps/usr/lib64/pkgconfig” || mkdir -p — “/tmp/build/tmp-ffmpeg/ffmpegdeps/usr/lib64/pkgconfig”
/usr/bin/ginstall -c -m 644 ‘zvbi-0.2.pc’ ‘/tmp/build/tmp-ffmpeg/ffmpegdeps/usr/lib64/pkgconfig/zvbi-0.2.pc’
make[2]: Leaving directory `/tmp/build/tmp-ffmpeg/zvbi-0.2.35′
make[1]: Leaving directory `/tmp/build/tmp-ffmpeg/zvbi-0.2.35′
/tmp/build/tmp-ffmpeg
**
** ffmpeg …
**
ERROR: libass not found using pkg-config

If you think configure made a mistake, make sure you are using the latest
version from Git. If the latest version fails, report the problem to the
ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
Include the log file “config.log” produced by configure as this will help
solve the problem.
Makefile:2: config.mak: No such file or directory
Makefile:62: /common.mak: No such file or directory
Makefile:104: /libavutil/Makefile: No such file or directory
Makefile:104: /library.mak: No such file or directory
Makefile:106: /doc/Makefile: No such file or directory
Makefile:189: /tests/Makefile: No such file or directory
make: *** No rule to make target `/tests/Makefile’. Stop.
Makefile:2: config.mak: No such file or directory
Makefile:62: /common.mak: No such file or directory
Makefile:104: /libavutil/Makefile: No such file or directory
Makefile:104: /library.mak: No such file or directory
Makefile:106: /doc/Makefile: No such file or directory
Makefile:189: /tests/Makefile: No such file or directory
make: *** No rule to make target `/tests/Makefile’. Stop.
** Adding ffmpeg presets:
** Fixing up pkgconfig files:
ls: cannot access /tmp/build/package-ffmpeg/usr/lib64/pkgconfig/*.pc: No such file or directory
cp: cannot stat ‘doc/TODO’: No such file or directory
cp: cannot stat ‘doc/*.html’: No such file or directory
./ffmpeg.SlackBuild FAILED at line 1765!
bash-4.2$

Comment from alienbob
Posted: November 7, 2015 at 16:13

The only relevant message shown in that bit of text is “ERROR: libass not found using pkg-config”. This means something was not well, a lot earlier in the compilation process. Try finding out what happened when libass was being compiled.

Comment from Brian Capouch
Posted: November 7, 2015 at 23:43

Build ffmpeg from the Github repo; it builds flawlessly, and has the advantage that it is compatible with the GH repo for vlc, too, and it was the only way I could get the latter to build successfuly.

Comment from alienbob
Posted: November 17, 2015 at 14:11

Alex Kempshall,

In LibreOffice 5.0.3 the patch http://cgit.freedesktop.org/libreoffice/core/commit/?id=eaa34b4e29478770c4707d56aa102491bc8e058a still has not been applied, and I am unable to apply it cleany against the 5.0.3.2 tarball. Subsequently the compilation fails because of the partly failed patch.
Unless you are able to create a rebased patch for me, I am afraid I have to build LO 5.0.3 without this fix.

Comment from alienbob
Posted: November 17, 2015 at 16:28

Actually Alex, I will try to come up with the patch myself. Most of the failed stuff is a simple s/IDF_/InsertDeleteFlags::/g

Comment from Alex Kempshall
Posted: November 17, 2015 at 17:02

Hi

Before raising it with you I posted a message to the developers list. Didn’t get anything useful back.

Then bisected the code got it down to a specific patch. Raised it again on the developers’ list and another patch was raised, a couple of days later, against master which fixed the problem.

I’ve never managed to find a bug report so don’t know which branch/release the patch was aimed at.

I’ve asked on the Developer’s list.

Alex

Comment from alienbob
Posted: November 17, 2015 at 17:03

I have a patch now, and I am compiling.

Comment from alienbob
Posted: November 17, 2015 at 22:00

Either I missed parts of the patch in git or something else is not compatible. This is the error I get:

414461 :/tmp/build/tmp-libreoffice/libreoffice-5.0.3.2/sc/inc/global.hxx:152:11:
error: 'fromInt' is not a member of 'InsertDeleteFlags'
414464 :/tmp/build/tmp-libreoffice/libreoffice-5.0.3.2/sc/inc/global.hxx:152:38:
error: 'lhs' was not declared in this scope
414467 :/tmp/build/tmp-libreoffice/libreoffice-5.0.3.2/sc/inc/global.hxx:152:50:
error: 'rhs' was not declared in this scope

The patch I used is here: https://dl.dropboxusercontent.com/u/2329942/libreoffice5.failing_unittest.patch

Comment from Alex Kempshall
Posted: November 18, 2015 at 09:21

Hi Eric

the response from the developers is

“as it was pushed to master only recently, it will only appear in the next release spawned off master, i.e., LO 5.1 ”

So I suppose we should leave it to spawn out in the way the developers intended.

Maybe if I’d raised a bug report immediately I encountered the problem the developer may have back ported.

Alex

Comment from Mohammad Etemaddar
Posted: November 19, 2015 at 07:57

Dear Alien Bob,
Would you mind update Qt on stable repo?
It’s a long time that Qt is updated to 5.5 on slackbuilds.

Also Qt has been updated to 5.5.1 about 30 days ago, If it’s possible, would you mind udpate to this version?

Thanks a lot,

Comment from Daniel
Posted: November 22, 2015 at 13:15

Hi Eric! It will be nice if you will also make a persistent Slackware Live edition.
People like the idea of having a stable and powerfull live operating system stored on an usb stick.

Comment from alienbob
Posted: November 22, 2015 at 14:43

Daniel, did you not read my article about my Live edition? Probably not, since you are posting this in the generic Feedback section.

Comment from Chris
Posted: November 25, 2015 at 22:57

Hi! After some years of being away from Slackware (I got seduced away by Debian and the lazy ease of apt-get update) I find myself not loving the news of systemd and looking to return to Slack.
BUT! The question is how long can systemd be held at bay? Estimates? My current laptop is nearly dead and I’d hate to buy a new one and find myself hamstrung by systemd issues. If I must be punished for using a computer I’ll give in and go Apple. But if you figure systemd can be held off 3-5 years I can hold off on such decisions.

Comment from orbea
Posted: November 25, 2015 at 23:06

Systemd will never be a requirement to run a computer. Slackware current recently replaced its old udev with eudev, so its seems like slackware will not have systemd in the near future if ever.

Comment from alienbob
Posted: November 25, 2015 at 23:11

Chris, honestly.
I can not look 5 years into the future of Slackware. Make up your mind about what you _want_ to use and then stick with that decision.

Comment from Chris
Posted: November 26, 2015 at 02:15

Fair enough, then Mr Hamleers! I over-reached with that phrasing. I was more after seeing what someone like yourself with more insight into the development side of things felt about the potential down the road. I am comforted seeing the work being done by Slackware, XFCE, Gentoo and (I think) Funtoo.

@orbea – Originally I wasn’t particularly afraid of systemd – I figured it was one init system amongst many and linux tends to allow multiple choices. But it seems like (looking at KDE and GNOME) that some of the DEs are hooking too much into systemd and every other distro has jumped on the bandwagon shouting “Newer and shinier!”
And sytemd has long since shot past being a simple init system and taking over other functionality. So it started to feel a bit inevitable.

Comment from orbea
Posted: November 27, 2015 at 08:32

Hey alienbob, maybe you can consider adding lzo and libaio to your multilib repo? I was investigating /usr/lib with ldd and found that libcairo-script-interpreter.so.2.11400.4 owned by cairo and libmysqld.so.18 owned by mariadb link against liblzo2.so.2 and and libaio.so.1 respectively owned by lzo and libaio. Using convertpkg-compat32 on both and then installing them fixed the issue as far as ldd can see.

Comment from alienbob
Posted: November 27, 2015 at 10:16

Hi orbea,

Sure. I added the two to my script, and I wanted to do an update before the weekend anyway. So hopefully these two new compat32 packages will be available for download by the end of the day.

Comment from orbea
Posted: November 28, 2015 at 23:15

So I was investigating with ldd more, then I found this old script to find missing libraries.
https://bbs.archlinux.org/viewtopic.php?id=6460

Which I then touched up slightly for slackware.
http://pastebin.com/kWYVT0cu

So in short, these compat32 packages in your repo have missing libraries which you might want to consider fixing.

alsa-lib
cups-filters
flac
gnome-keyring
gnutls
gst-plugins-base
gst-plugins-base0
gst-plugins-good
gst-plugins-good0
libgphoto
libxml2
libxslt
mariadb
qt
util-linux

So I then used convertpkg-compat32 to create packages containing all the missing libraries listed and then repeated a few times to make sure I had them all. In the end installing these compat32 packages resolve all missing multilib libraries.

GConf
aalib
at-spi2-atk
at-spi2-core
cdparanoia
db48
gc
gcr
gd
glib
gtk+
gtk+3
guile
judy
libcaca
libiodbc
libsoup
libtheora
libunistring
libvisual
libvpx
poppler
python
qpdf
taglib
tcl
tk
wavpack
xmms

And here are more notes for this which might help.
http://pastebin.com/skq3urqp

Comment from alienbob
Posted: November 29, 2015 at 00:57

Hi orbea,

The compat32 packages are not meant to be satisfying all possible library dependencies. They are meant to get your proprietary 32bit programs running, and those programs will not tap into all the functionality. Whenever someone asks to add a package to the list because some 32bit program refuses to run otherwise, I do that. By following the path you entered above, you will eventually end up with a huge list of packages to install, to a point where you might consider just installing full 32bit Slackware in a chroot and be done with it.

Comment from orbea
Posted: November 29, 2015 at 01:37

Fair enough, I thought I’d mention it regardless. 🙂

Comment from Phantom
Posted: December 8, 2015 at 19:35

Hello alienbob,

I think this article is about slackware.

I think the guys are very happy with slackware in Enterprise, and give some advises, good ones.

Slack won\’t — and shouldn\’t — play IT\’s game

http://www.infoworld.com/article/3012118/saas/slack-wont-and-shouldnt-play-it-game.html

I think he is just carrying about business and enterprise, as Slackware is growing in a new land (that is awesome).

I think Pat and you will be happy with this article.

If is not about Slackware, feel at it was.

Only knows that, everybody root for Slackware, and I hope back to use it soon.

Comment from alienbob
Posted: December 8, 2015 at 21:01

Phantom, you should read better. That article is NOT about Slackware Linux.

Comment from Richard Herbert
Posted: December 9, 2015 at 02:29

Hi, Eric. I wrote a few months ago about problems I’d been having running Chromium after version … uhm, it’s been so long, I forgot. Anyway, after installing your latest Chromium (47.0.2526.73), here I am, writing you in Chromium! No more “Aw, snap!”, and no more having to resort to “chromium –disable-seccomp-filter-sandbox &”. As a Bugs Bunny character once siad, “I don’t know what yuz done, but I know yuz done it.” 🙂 Thanks, man!

Comment from orbea
Posted: December 19, 2015 at 00:15

Hi alienbob,

Have you ever thought about supplying an extra multilib repo for packages on SBo that might be needed as a multilib version? One example is pcsx2 (Playstation 2 emulator) requires multilib versions of wxGTK/wxPython, nvidia-cg-toolkit, portaudio and soundtouch which I suspect is the main reason that its not on SBo yet.

I could just make a 32-bit chroot to either run pcsx2 in or make the required multlib packages myself, but you might be in a better position to do this for a greater number of people?

Comment from alienbob
Posted: December 19, 2015 at 00:23

Hi orbea

Thanks but no… I am busy enough with just my own stuff. People will have to build their own “compat32” versions of SBo packages if they need that – it is not difficult.

Comment from Capouch
Posted: December 21, 2015 at 04:49

I downloaded the 64bit slackware-current ISO on 12/13, and there has been a big change for me: I can’t get it to boot, either on my laptop or as virtual machine instances, unless I add the line “maxcpus=1” to the LILO append options. I haven’t been able to find any documentation as to why this is, whether it’s a worry, or if it is what to do about it. Once I do that all else seems to be just fine.

Comment from alienbob
Posted: December 21, 2015 at 13:45

Hi Capouch; I never heard that before. There has not been a change in how the ISO is being generated, but it is of course using a newer kernel to boot than in the past. Perhaps this is a kernel issue? What kind of errors did you get when booting from the ISO without the “maxcpus=1” parameter?
Also curious about how the installed system is behaving. Is the “maxcpus=1” parameter not required there?
The ISO boots a “huge” kernel, is this the same kernel you are using on the installed computer, or did you switch to a generic kernel plus initrd?

Comment from Capouch
Posted: December 21, 2015 at 20:07

It is the default kernel to boot (huge) and whatever kernel is installed in a full install, I suspect the same one.

I can send a screenshot via URL of the screen as it boots? Although I’ll have to take a picture of it–it is something about detecting CPUS then a new line then #1 some spaces #2 and a freeze. I can see no ill effects of the maxcpus. We refresh our current pretty often. The late October one was just fine, but the mid-December one, as I said, requires that append for both the original install and the same ISO installed under VirtualBox.

Comment from orbea
Posted: December 22, 2015 at 11:30

Hi again alienbob,

In short: Any chance you could add libnotify and xz to your compat32 repo?

Explanation: Pcsx2’s last stable tarball is ~1,500 commits behind and does not work well, so I made a git version of the slackbuild which does work. However it requires two Slackware compat32 packages you do not already include in your repo. Pcsx2 requires xz and wxGTK3 builds against libnotify which will result in pcsx2 failing to compile on a multilib environment without it.

They are both easy to make by the user, so I just included them in the slackbuild’s README. The slackbuild is available in my small notabug SlackBuilds-git repo in the following link.

https://notabug.org/orbea/SlackBuilds-git/src/master/pcsx2

Comment from allend
Posted: January 3, 2016 at 11:38

Hi Eric,

I just wanted to pass on that your vlc-2.2.1 build script failed to complete on Slackware64-current until I added the following patch.
— a/vlc.SlackBuild 2016-01-03 21:16:39.782066543 +1100
+++ b/vlc.SlackBuild 2016-01-03 21:17:02.035064258 +1100
@@ -2924,7 +2924,7 @@
{
echo -e “**\n** dvbpsi …\n**”
cd $TMP/tmp-$PRGNAM/libdvbpsi-${DVBPSI}
-CFLAGS=”$SLKCFLAGS” \
+CFLAGS=”$SLKCFLAGS -Wno-error=bool-compare” \
CXXFLAGS=”$SLKCFLAGS” \
LDFLAGS=”$SLKLDFLAGS” \
./configure \

As always, my grateful thanks for all you do for the Slackware community.

Comment from Svar
Posted: January 5, 2016 at 20:31

Hi Eric,
this is a question on Slack 14.1 Installation with UEFI/secure boot disabled. Is there a link to understand why write fails?

cgdisk 0.8.7
Disk drive /dev/sda
Size …

Partition # Size PartitionType Partition
1007.0KiB free space
1 400MiB Windows RE Basic Data Partition
2 260MiB EFI System EFI System Partition
3 240MiB Microsoft Reserved Microsoft Reserved Partition
4 345.4GiB Microsoft Basic Data Basic Data Partition
7 168.3GiB Linux filesystem Slack14.1
9 736.0KiB Linux swap
8 168.2GiB Linux filesystem (I intend to also use another Linux distribution here)
5 450.0MiB Windows RE
6 15.3GiB Microsoft Basic Data Basic Data Partition
871.5KiB free space

After setting up partition 7, verify was ok and then write says: Problem saving data! Your partition table may be damaged!

Comment from alienbob
Posted: January 6, 2016 at 00:13

Hi Svar

My blog is no extension of LQ.org. You already posted your question as http://www.linuxquestions.org/questions/slackware-installation-40/gpt-issue-on-a-14-1-slack-install-on-laptop-4175563062/ and it has answers from fellow Slackers. That is how it works – and if no further answers are posted that’s probably because no one knows.
Expect nothing here because I am not running a free for all troubleshooting shop. Sorry.

Comment from alienbob
Posted: January 6, 2016 at 00:14

Hi allend,
I will probably need that when I compile vlc 2.2.2… whenever *that* comes out.

Comment from Svar
Posted: January 6, 2016 at 16:04

Eric,
thanks both for your answer and your huge slack work. I’ll post in LQ if I figure it out.

Comment from alienbob
Posted: January 6, 2016 at 17:11

Svar, I may have sounded a bit harsh, which was not my intention. Hope you get your answer on LQ.

Comment from _metic
Posted: January 23, 2016 at 14:20

Dear Eric,
Looking to introduce/unlock children at the community level to computers and what not, etc. of course running Slackware.

This also applies to my children who are yet to ever touch a computer.

I kindly request if your “Parental control on the Linux desktop” from 2008, would be still how you would go about controlling things as such.

http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:parentalcontrol

warm regards

Comment from alienbob
Posted: January 23, 2016 at 23:14

Hi _metic

My son has grown up and we are no longer in need of parental controls here, but if I had to do it again, I would start with my old instructions and see how far I would get. I hope that the old Wiki article is still 100% valid but I cannot give you a guarantee.

What I learnt over the years is that installing parental controls is the start, not the end.
The more important part of acquainting your kids with the Internet and keeping them away from its dangers is to keep the dialogue with your kids open. Talk with them about what they are doing with their computer, be genuinely interested and hope that your interest will keep them informing you of what they do.
Once they start getting the feeling that you are tieing them down they will start exploring without telling you. And smart kids will eventually find their way around the parental controls.
Still, these parental controls helped a lot.

Comment from _metic
Posted: January 25, 2016 at 21:58

thank you for the response.

Comment from Eduardo
Posted: February 2, 2016 at 13:33

Hi Eric, in case you don’t already know, Copy.com will be discontinued on May 1:

https://techlib.barracuda.com/display/COPY/Copy+End-of-Life

Bad news.

Regards,

Eduardo

Comment from alienbob
Posted: February 2, 2016 at 16:12

That’s too bad indeed Eduardo. I had not yet seen this EOL message.

Comment from Alex
Posted: February 4, 2016 at 18:52

http://taper.alienbase.nl is down 🙁

Comment from Anze
Posted: February 9, 2016 at 09:14

Hi alienbob.. i love your contribution to slackware comunity.. but i had a problem installing multilib on my slack64 with your tutorial.. once i completed the installation all of the 32bit programs worked.. but when i restarted my Xorg i couldn’t get back in.. no matter what config i used everytime i run startx all it did was post a list of libraries and thats it.. so i had to reinstall the system all over because had no idea what the problem was. do you know what did i do wrong? using 14.1 slack with kde installed from the latest dvd

Comment from alienbob
Posted: February 9, 2016 at 17:14

Anze – you are running Slackware64 14.1 with the KDE 4.10.5 from that same Slackware?
And after you installed the multilib packages, your X session would no longer start? The most common reason for that is that you installed glibc for the wrong Slackware version. From what exact URL did you download these multilib packages? And again, is it Slackware 14.1 or -current or a mix of the two that you have installed?

Comment from Anze
Posted: February 9, 2016 at 18:30

hi bob.. i was following your tutorial http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib
yes all from same slackware. and was downloading slackware 14.1 packages.

i ran a command:
# SLACKVER=14.1
# mkdir multilib
# cd multilib
# lftp -c “open http://taper.alienbase.nl/mirrors/people/alien/multilib/ ; mirror -c -e ${SLACKVER}”
# cd ${SLACKVER}

and all of the files were downloaded for 14.1 version of slack. i followed exactly your tutorial and xorg failed. now i’m afraid to do it again

Comment from alienbob
Posted: February 9, 2016 at 19:11

Anze, does not sound wrong what you did. But again, what exact version of Slackware are you running? What medium did you use to install? The official Slackware 14.1 DVD ISO image?

Comment from Anze
Posted: February 9, 2016 at 21:24

hi bob. i am running slack 64bit 14.1 installed from official kde dvd downloaded from slackware website.

Comment from cwizardone
Posted: February 11, 2016 at 00:04

Hello.
Your last change log is time stamped about 12 or 13 hours ago, butt none of the packages have hit the mirrors I’ve looked at.
Just FYI.

Comment from alienbob
Posted: February 11, 2016 at 00:24

You’re right. Apparently I did not add the packages to the repository. Attribute that to the spell of flu I am under.

Comment from cwizardone
Posted: February 11, 2016 at 00:31

Understand. I’m in my 5th week of the flu. The doctor said there is a strain going around that has hit the elderly (moi) very hard and there isn’t much that can be done about, but tough it out. The worst is over, but the cough won’t go away….. Getting real tired of it.
🙂

Comment from donrich39
Posted: February 11, 2016 at 01:23

Sorry to hear that Eric.
Hope you get better really soon.
And, thanks for all the hard work you do!

Comment from Mehran
Posted: February 11, 2016 at 09:59

Hi

Icedta 2.6.4 is released; however the repository version of icedtea is stopped at 1.6.1 which is out of date and is not designed to work with opendjdk 7. I would be grateful if you update the iceadtea package.

Thank you for all your effort.

Comment from alienbob
Posted: February 11, 2016 at 11:44

Mehran you should check your facts better before you post here. I do not have an “icedtea-1.6.1” package at all.

I have a package called “icedtea-web” at version 1.6.1 and that contains the browser plugin for Java applets. There was a newer release last week (1.6.2) which is on my TODO but not with a high priority.

I do not have a separate “icedtea” package, that would be useless. I have an “openjdk” package which is currently at version 7u95_b00 and which I compiled using icedtea 2.6.4.

Comment from Mehran
Posted: February 12, 2016 at 02:16

You’re right. I’m sorry for this mistake.

Comment from Anze
Posted: February 12, 2016 at 16:35

Hi bob. i think i found a solution to my problem. Faulty fglrx driver. I tried one more time to make my 64bit multilib and xorg failed yet again.. i had enough of it and installed 32bit slack… i updated the system with slackpkg and when it was done i rebooted the system. when it booted back into slack i started Xorg and bam the same problem allover again.. than just for kicks i rerun the amd video card drivers installation script and xorg started working again..so now everytime a mess with lib files i have to rerun script to make xorg working again.. so thanks for your time trying to find a solution for me.

Comment from Tonus
Posted: February 15, 2016 at 14:18

Hi,
Just wondering if you had my e-mail to alien at slackware dot com about a possible mirror. I haven’t any error but don’t know how often you check it. (it’s from another e-mail address)

Comment from alienbob
Posted: February 15, 2016 at 23:31

Hi Tonus, I think I received your email, and another too with a mirror proposal. Currently busy due to real-life situation but I _will_ respond. Thanks!

Comment from R.H.
Posted: February 18, 2016 at 23:07

I wonder if you know about http://ring.cx I just discovered it recently. It is a secure skype replacement.

With a qt5 dependency how hard would it be to add to slackware?

Comment from alienbob
Posted: February 18, 2016 at 23:23

Adding to Slackware core would be out of the question, looking at the plethora of dependencies that need to be fulfilled first. But it should be feasible to build this and its deps and put it in a 3rd-party repository.
Interesting, because open source voice/video capable peer-to-peer applications are rare in Linux world.

Comment from R.H.
Posted: February 24, 2016 at 00:37

@alienbob, I am looking into nix pkg manager to see if that can be used but so far it has given me a headache. And yes ring.cx is a rare thing and is why I watched the fosdem talk.

Comment from Randy Evans
Posted: February 27, 2016 at 23:15

Eric,

Four years ago I convinced my school to let me teach the 8th graders about computers by doing a 3 week course — 2hours/morning. We had no computers, and no budget for software, so I solicited laptop donations from the community. I was a former IT professional who used Unix (some) at work. I had never used Linux, but I knew I could get it for free (which was perfect for my budget). I wiped the laptops and wanted to laod Slackware 13.37 on them. I received everything from a 1999 IBM ThinkPad to a ASUS EEE netbook. Back then, I was totally stuck how to get slackware installed since I had no disks, had never heard of an iso image, and didn’t have a Linux installation on any computer. Your http://alien.slackbook.org/blog/welcome-windows-user/ link helped me quite a bit. I was able to create a USB stick that loaded my motley collection of PCs. (OK, I had to figure how to burn disks for the Thinkpad). The course was a great success. I taught the kids the basics of programming using only bash and a litle python. The kids loved it, and the course continues even though I am no longer teaching there.

This year I am teaching the course in a new city to more 8th graders. Familiar with the process, a couple of weeks ago, I started collecting old laptops to load them with Slackware. Two days ago my USB stick died. (It was 3 years old.) Reluctantly, I sought to re-create the bootable install stick. I had hot-wired the first one with a universal linux installer and your advice. I was never quite sure how I got it to work, so I was very unhappy about re-creating it. However, I now have several laptops with Linux on them, so I could create bootable USB from that, right?

This led me to your post http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/. I used the information there to create new stick. Note, I got hung up along the way because I specified -o /dev/sdb1 in the usbimg2disk.sh command, but I found my mistake in your response to a comment on May 29th, 2010. I also had to install the rsync package as you suggested on October 7, 2010.

So you never even had to talk to me to help me. I just thought you should know that you, like Richard Stallman and Linux Torvalds, made my work possible. So far, you’ve helped bring progamming to more than 85 middle schoolers that you never even knew about (and who knows how many more in the future).

So, thank you.

Who knows how many people you are helping every day without even knowing about it?

Sincerely,
Randy Evans

PS I don’t actaully have a question or problem. You’ve answered all of them (so far).

Comment from alienbob
Posted: February 27, 2016 at 23:32

Hi Randy

Nice of you to drop a note and tell us about your endeavors. Nice story! I think teaching kids the art of computer programming at a young age will create brilliant people when they grow up. It’s like with the Raspberry Pi which was conceived for exactly the same reason: create an affordable platform where kids can be introduced to computer programming in a playful manner. the world will need these kids sooner or later.
The world is getting dumber by the day and tracks like yours are fighting that awful trend to kill creativity by turning young people into consumers instead of thinkers.

Did you write your course program from scratch or could you use existing coursework?

Comment from Randy Evans
Posted: February 29, 2016 at 04:26

I made it up/make it up as I go a long. It’s very discovery based which, for me, gets the best results. It’s all command line. On day one, for example, they power on the laptop, I give them a username and paswword and ask them to make the computer do something. Every year, I amazed at what they figure out from that. New info is traded up and down the rows, and a few reboots become necessary. Eventually, I have to give them some direction, but once you get hooked on the notion that there are secrets in there that you can master, the computer becomes an interactive trial and error machine.

As a teacher, I can’t resist imposing some structure and having some markers along the way, but the more open-ended it is the more the kids are engaged and the more they learn.

I’ve been thinking that the Rasperry Pi would be the way to go long term. I’d love for the students to see the guts a bit more to help disple the magic box myth, but a laptops is self-contained, less breakable, and so far free. Kids can take them to and from school quite easily. Pi would be hard to handle with all the peripherals.

Thanks again for your help.

Comment from inman
Posted: March 4, 2016 at 00:31

hi eric, do u noticed the last chromium-dev-pepperflash-plugin-20.0.0.248-x86_64-1alien.txz causes noisy and distorted audio on chromium flash video players?

Comment from alienbob
Posted: March 4, 2016 at 10:30

Hi inman; to be honest, I do not use Flash myself so I can not comment on distorted audio. I wonder, are you running it on Slackware 14.1 or on -current? Or alternatively phrased: is your computer using ALSA, or PulseAudio, or perhaps even JackD?

Comment from fabio
Posted: March 5, 2016 at 09:59

Openshot is one of the best free video editors out. unfortunately, the one provided at SBo has a quite extensive list of dependencies and optional dependencies. I really would like, if possible, to see it built in a single txz package. And thanks for the new liveslack, using it as pocket os with full disk encryption.

Comment from inman
Posted: March 9, 2016 at 14:45

hi, tanx for the response here …
I’m using the SC with pulseaudio, so probably the chromium-dev uses alsa playback plugin. The html5 players (eg youtube) are working perfectly.
The noisy and distorted audio ( like audio glitch, sounds like corrupted mp3) is only there if a flash video or audio is being played using chromium-dev. With seamonkey the problem isn’t there at all. So probably it has not to do with pulseaudio but the flash plugins.

The flashplayer-plugin-11.2.202.569-x86_64-1alien and seamonkey doing well, while the chromium-dev-pepperflash-plugin-20.0.0.248-x86_64-1alien and chromium-dev-49.0.2593.0-x86_64-1alien have some problem.
I have some guesses about f_s, but i couldn’t figure out how to check or configure that.

If u do not use the flash-player at all, how to you mange to play the video players of those creepy old fashioned website? … is there anything out there that im not aware of!

thank u as always, for all you do for slackware and its community.
bests

Comment from alienbob
Posted: March 9, 2016 at 14:57

inman, some people do not visit creepy websites with flash video.
And if I visit pages with flash-based advertisements, they usually do not come with audio so I would not notice that something is wrong with the audio…

Comment from inman
Posted: March 9, 2016 at 15:37

Even if it is bbc.co.uk? i mean where can you find unbiased news with html5 player? 🙁 😀

Comment from alienbob
Posted: March 9, 2016 at 15:46

For unbiased news I read a news paper. Real paper.

Comment from ryan
Posted: March 9, 2016 at 18:48

Thanks for all of your hard work on Slackware. Are we going to see LibreSSL enter the main repository, if not replace OpenSSL outright? Also, will the Lumina desktop environment ever make its way into the repositories? Thanks, Ryan.

Comment from alienbob
Posted: March 10, 2016 at 08:05

Hi ryan; no and no…

Comment from blizzack
Posted: March 13, 2016 at 18:09

@alienbob

THANK YOU…to you and all those that make slackware what it is !
Keep up the great work !!

Comment from alienbob
Posted: March 13, 2016 at 21:25

Hi blizzack – thanks for the kind words. Glad you like Slackware, be sure to advocate it among your friends 🙂

Comment from darkstaring
Posted: March 15, 2016 at 21:38

Hello Alien .. you are a legend;)
I would like to ask you how can I make a non-root user login on KDE 5_16.02
Thanks Francesco

Comment from alienbob
Posted: March 15, 2016 at 23:13

darkstaring , that is not limited to KDE, it is a Slackware feature to create a non-root login right after installation of the OS.
Read http://docs.slackware.com/start?id=slackware:beginners_guide#create_a_user_account
Once you have a non-root user it should be able to login to the SDDM session manager, or if you are in runlevel 3 (console login) you first run “xwmconfig” (once) to select xinitrc.plasma as your session type. Then run “startx” everytime you want to start an X session.

Comment from peebee
Posted: March 16, 2016 at 23:02

Hi Eric
Thought you would be interested to know that a member of the Puppy Linux community has found a way to obtain 32-bit pepperflash updates from Google Chrome. How long this will continue to work is of course unknown but its has worked for 21.0.0.182.

The thread describing the process is: http://murga-linux.com/puppy/viewtopic.php?p=894322#894322

BTW – your update process seems to have deleted the 32-bit pepperflash in your repository.

Thanks for all you do to provide software for the Linux community.
Cheers
peebee

Comment from alienbob
Posted: March 16, 2016 at 23:48

peebee – the 32-bit PepperFlash in my repository was vulnerable to attack. That is why I removed it.
Interesting thought that the older 32-bit Chrome still downloads an uptodate PepperFlash library from somewhere.

Comment from paul Genho
Posted: March 25, 2016 at 16:48

Hey Eric, I put up a mirror of slackware live last fall but it stopped syncing last month.

I’m getting: "@ERROR: access denied to mirrors from UNKNOWN " when I try to run sync manually.

Do you need to whitelist my IP (208.91.197.168) or do you have enough mirrors and I should take it down?

(this isn’t really a comment… I just didn’t know how else to reach you)

Cheers,
Paul

Comment from alienbob
Posted: March 25, 2016 at 16:55

Hi paul, this was discussed in several recent blog articles. The server’s rsync has been made unavailable because it was not able to cope with the rise in download requests and my hoster started complaining about the bandwidth cost.
I have brought a new server online in its stead and you should start mirroring from that one: rsync://bear.alienbase.nl/mirrors/

Comment from brianc
Posted: March 25, 2016 at 19:33

I am engaged in some back-and-forth about Slackware’s "inferiority" over the issue that is pitching this error on a build:

** snip **
/usr/bin/ld: this linker was not configured to use sysroots
**
The folks on the mailing list say, "The linkers on all the other distros will do this. Your problem is Slackware. I hope you can comment–I’m not familiar with the concepts that are being discussed. Thanks.

Comment from alienbob
Posted: March 25, 2016 at 21:18

brianc – without any context I can not give you a meaningful answer. I never saw the error, I also do not know what triggers it.

BUt… if you are in a discussion with some developer morons who use phrases like "inferiority" there is little chance that I will have a second look at what their crappy code does.

FYI, please do not post complete build logs in this blog, I will delete your posts. Use a pastebin if you want to share large chunks of text.

Comment from R.H.
Posted: March 25, 2016 at 21:43

alienbob, is it okay to use bear.alienbase.nl for getting multilib?

Comment from alienbob
Posted: March 25, 2016 at 21:48

It’s OK to use bear.alienbase.nl for downloading EVERYTHING it carries. This server has taken over all the repositories from taper.alienbase.nl (except for the historical Slackware releases) and this weekend I also plan on moving docs.slackware.com from taper to bear.

Comment from paul Genho
Posted: March 26, 2016 at 01:50

That did it. Thanks.
http://mirrors.edgeorbis.com/distros/slackware-live/

Comment from brianc
Posted: March 26, 2016 at 20:26

I solved my issue by rebuilding ld from source, version 2.26.20160125. The older version was 2.25.1. I built with vanilla configure, so I wonder if the default has changed to include the sysroots feature? In any event, it looks like it will work itself out in later releases of Slack, and I am now good to go. Thanks.

Comment from fabio
Posted: April 9, 2016 at 02:44

i know there’s a lot of things to do in your real life sr. That said, there is a new version of veracrypt out. no serious bugs for linux found, but there are speed improvements according to the release notes. So, here’s my request for a slackbuild of that.

Comment from tolip
Posted: April 12, 2016 at 10:42

Thx for the pkgs.

After painting myself in and out of dual version Qt hell a couple times I discovered your stuff.
I had heard of your pkg’s but ‘old hunt for dependencies and compile’ habits die hard.

I got so far into the corner that I reblasted 14.1 and re-slackpkg’d myself back to ‘current’.
(tolip hangs head in shame for using default microsoft troubleshooting procedure)

I noticed a difference between your Qt5 and the .run file version that throws everything in /opt.

Symptom:
When starting a Qt5 app it fails with,
This application failed to start because it could not find or load the Qt platform plugin "xcb"

Investigate:
root#> ldd /usr/lib64/qt5/plugins/platforms/libqxcb.so

It listed 4 file not found issues involving
libxkbcommon

Solution:
git and make libxkbcommon
I just copied them to /usr/lib64 manually once built.
root#> ldconfig

Summary:
I have no idea if this is ‘as expected’ or what, but it’s what I did to make it go. I’m moving on but I figured I document what I did, here, just in case it is relevant to your endeavor.

Now I’m off to play with the must have Qt5 app that started this snowball rolling 🙂

Comment from alienbob
Posted: April 12, 2016 at 11:28

My qt5 package picked up an unexpected dependency on my libxkbcommon package… because I guess I forgot to de-install from my build box.
The libxkbcommon package is part of my KDE "ktown" repository: http://bear.alienbase.nl/mirrors/alien-kde/current/testing/x86_64/deps/libxkbcommon-0.5.0-x86_64-1alien.txz and http://bear.alienbase.nl/mirrors/alien-kde/current/testing/x86/deps/libxkbcommon-0.5.0-i486-1alien.txz

Comment from Nitesky
Posted: April 15, 2016 at 04:18

Hi,
Am not new to Slackware as it was my first linux back around 1998 or so. Am running current64. Took the time today to follow your directions to change to KDE 5. For some reason when I used:
# upgradepkg –reinstall –install-new x86_64/ . . .
it ended up bellyaching to me that it can’t find any installed files to upgrade so it skipped them. Not all of them but lots so I just waited until everything was done and then went back to just installpkg all. It worked for me.
Also, just found that dolphin has very few icons in the icon view. Don’t know what to do about that.
Plasma is breathtaking. Thanks for your hard work

Comment from alienbob
Posted: April 15, 2016 at 11:37

Nitesky, "upgradepkg –reinstall –install-new" will install all packages that were not installed before (the "–install-new" parameter takes care of that) so additionally running "installpkg" should not be necessary. Check your /varlog/packages directory for duplicate packages, pretty sure that all of the new Plasma packages will show up.

If you have zero duplicate packages then the following command should have zero output:

ls /var/log/packages/ |rev |cut -d/ -f1 |cut -d- -f4- |rev |sort |uniq -d

Comment from Nitesky
Posted: April 15, 2016 at 16:12

Ya, got zero when using that command.
"upgradepkg –reinstall –install-new" for some reason doesn’t work for me so I just cover after by installpkg with everything. All new packages just install and all previously installed packages install over top again. Just a way to get the result I need.
Found konqueror lacks a menu entry. Had to make one

Comment from Nitesky
Posted: April 16, 2016 at 15:59

The command
ls /var/log/packages/ |rev |cut -d/ -f1 |cut -d- -f4- |rev |sort |uniq -d
produced zero results.
I don’t know why the command
upgradepkg –reinstall –install-new
does not install new programs for me but that is the reality. Been like that for a long time now and through a couple of clean full installs. No biggie. My way works for me

Comment from Nitesky
Posted: April 19, 2016 at 01:48

If there is a better way to report problems just let me know.

Can’t find a launcher for Dolphin

Comment from E. Wayne Johnson
Posted: April 19, 2016 at 09:21

This is a KDE problem so I will ask it here. Since the last upgrade to -current I have a problem that KDE thinks that my time zone is "Troll/Antarctica". My local time zone in Slackware is set to Asia/Chongqing, which is correct (I’m in Beijing). XFCE has the correct time and time zone is "local", but KDE thinks local is Troll, Antarctica, and sets my local time 8 hours ahead, which does interesting things to my email.

Comment from E. Wayne Johnson
Posted: April 19, 2016 at 09:24

I had this time zone problem before but it was easily corrected, but now KDE keeps switching me back to Troll. Humourous it is but now I am ready to have it back to droll normality.

Comment from alienbob
Posted: April 19, 2016 at 10:18

E. Wayne Johnson, I have no idea. You should ask on the LQ forum perhaps, or file a bug on bugs.kde.org.

Comment from E. Wayne Johnson
Posted: April 19, 2016 at 10:40

I seem to have fixed it by a combination of running hwclock –show which said that I was on UTC time although I had just a little while before run pkgtool to set the time. I then ran timeconfig directly from root, then hwclock –systohc –localtime which fixed it. I did timeconfig through pkgtool previously but didnt fix it for me.

Comment from Boris
Posted: April 27, 2016 at 10:14

My question concerns whether it is possible to have a local keyfile for a luks encrypted disk. I have an X200 with libreboot. The advantage of libreboot is that grub is my bootloader and permits full disk encryption including the /boot directory. I was able to follow your guide and have everything working great. The only tiny quirk is I have to enter my luks password twice. Once when grub first boots, and a second time during the kernel boot process. I followed a modified version of the instructions here https://libreboot.org/docs/gnulinux/encrypted_parabola.html to get grub booting. Towards the bottom of the page there is a Bonus section. It shows how to use mkinitcpio to permit a luks keyfile to sit on the local drive and be used to decrypt the drive during boot with the help of grub. The issue of course is Slackware has mkinitrd; which from what I understand requires a separate drive that’s a FAT partition for this to work. Is there a way to place the luks keyfile locally and somehow specify it with mkinitrd; or a way around this?

Comment from alienbob
Posted: April 27, 2016 at 12:59

Boris, anything is possible with the init script in the initrd image. You should be able to add support for a LUKS keyfile on any filesystem that can be read by the init script at boot. If the /boot partition is already unlocked at that time you should be able to mount it and read the keyfile.

Comment from Boris
Posted: April 27, 2016 at 13:16

Eric, how would I change this line to make it work?

mkinitrd -c -k 4.4.8-smp -m ext4 -f ext4 -r /dev/cryptvg/root -C /dev/sdx2 -L -K LABEL=TRAVELSTICK:/keys/alien.luks

Even the instructions of mkinitrd say use a FAT filesystem

Comment from alienbob
Posted: April 27, 2016 at 16:14

You have to work this out yourself.
The mkinitrd command is not what you need to change.
It is the package source. You have to edit the “init” script which is part of the mkinitrd source, add support for a LUKS keyfile on another filesystem than a (v)FAT USB stick, make sure the init script mounts that filesystem and uses your keyfile; and then you have to rebuild the mkinitrd package and install it to your computer,

An exercise I will leave to you.

Comment from Boris
Posted: April 28, 2016 at 06:28

don’t know if I’m misunderstanding, but all the partitions are encrypted including /boot. I can’t mount any devices unless I provide a password or keyfile first. So don’t I have to add the created keyfile into the initrd package? ; because I wouldn’t be able to access it locally.

Comment from alienbob
Posted: April 28, 2016 at 09:35

I do not know how the full disk encryption (including /boot) works with GRUB, but you need to enter your LUKS password to let GRUB access the kernel and initrd on the /boot partition, right? Doesn’t that mean that from that point onwards, /boot is unlocked? Or is /boot only accessible to GRUB during initial boot? If that is the case then indeed you have to add your LUKS keyfile into the initrd because that is the only accessible fileystem after GRUB boots the kernel and tells it to load the initrd into its memory space.

Comment from Boris
Posted: April 28, 2016 at 20:55

Asked in #grub. /boot is only accessible to grub for the initial boot, after that only the files provided within the initrd are available. Any suggestions for the best way to do this? From what I understand I would have to modify the Slackbuild to add a provided lukskey into the package, and the init file so it knows to use the file for cryptsetup luksOpen.

Comment from alienbob
Posted: April 28, 2016 at 21:10

No you do not have to update the SlackBuild and the package.

What you need to do is run the command “mkinitrd -c ” once. Afterwards there will be a directory tree /boot/inintrd-tree .

In that directory tree you make all the modifications you want.

You end with running the command “mkinitrd” (without any additional parameter). The mkinitrd command will compress directory /boot/initrd-tree into a new /boot/initrd.gz file which GRUB will pass to the kernel.

In the /boot/initrd-tree you need to:
– copy your LUKS keyfile to some directory below /boot/initrd-tree/ ; this directory is what you will use in the next step.
– edit the script ./init ; it is the initialization script where you will find the cryptsetup calls that use a keyfile to unlock the root filesystem. You need to make sure you change that call to use the path to your own keyfile (which you stored in /boot/initrd-tree so that it will be embedded in your new initrd.gz image).

This is just thinking out loud. I believe this is how it should work, but it is unproven.

Comment from Boris
Posted: April 28, 2016 at 22:38

Success 🙂 thank you.

Comment from MS
Posted: May 2, 2016 at 07:08

Thanks for everything.

Comment from cwizardone
Posted: May 9, 2016 at 07:54

Happy Birthday!

Comment from cwizardone
Posted: May 17, 2016 at 06:43

> Mon, 16 May 2016 18:53:44 GMT
> veracrypt: updated to 1.17.

Thank you very much!

Comment from Richard
Posted: May 20, 2016 at 03:19

Love your work. I just upgraded to slackware64-current (soon to be 14.2) Do you have the multi-lib package for that? Let me know if you need help building them. I’d love to get my hands in there.

Comment from alienbob
Posted: May 20, 2016 at 10:37

Richard did you really not look at all???

Comment from Nitesky
Posted: May 22, 2016 at 06:23

Hi. Was just looking around the applications on the Plasma 5 KDE. I tried Plasma Media Centre and it takes over the entire desktop. No way to exit so I had to use ctrl, alt, esc to kill it.
Is this normal or have I done something wrong somehow?
Thanks in advance for your answer

Comment from alienbob
Posted: May 22, 2016 at 11:17

Nitesky there’s always Ctrl-Alt-BackSpace to kill a running X session, you do not have to do a complete reboot.
Other than that, I never used Plasma Media Center myself and only provide it as a package. When I started it, I could not see an exit button or configuration menu but simply pressing a keyboard key brought up the krunner dialog and made the task bar visible where I was able to close the window.

Comment from Nitesky
Posted: May 22, 2016 at 15:20

WOW! Ctrl-Alt-BackSpace killed the entire x-session as you said.
Ctrl-Alt-Esc killed only the Plasma Media Center and my x-session kept running.
Thanks for the tip

Comment from Ed LaBonte
Posted: May 31, 2016 at 05:05

Hi, I installed version 1.01 of the xfce version of slackware64 live and it booted. But It’s asking for a user and password which I don’t have, and couldn’t find anything about it in the README. What am I missing.

Comment from alienbob
Posted: May 31, 2016 at 09:08

From the README.txt and it is also mentioned in every article I wrote about liveslak on this blog:

==== Using the ISO image ====

….

Slackware Live Edition knows two user accounts: “root” and “live”. They have passwords, and by default these are… you guessed: “root” and “live”.

Comment from duder
Posted: June 9, 2016 at 23:13

Nice site alienbob.

Just reporting in your wordpress needs some patching. Getting popups from lqibh.com when browsing the site.

Comment from Eric W
Posted: June 10, 2016 at 09:26

Hi Eric, I’m getting error with iso2usb.sh

./iso2usb.sh -i /images/latest/slackware64-live-current.iso -o /dev/sdb
(after about 10-11 minutes of file copying)
–Making the USB drive ‘/dev/sdb’ bootable extlinuz
/sbin/extlinux: cannot find device for path /mnt/alienusb.8zbLiY/boot/extlinux
*** ./iso2usb.sh FAILED at line 561

-another eric

Comment from alienbob
Posted: June 10, 2016 at 11:26

Eric W, weird.
Is your USB stick large enough to contain the 2.6 GB of data in that Live ISO?
The error would indicate that the script has not renamed “/boot/syslinux” to “/boot/extlinux”, OR that the /boot directory was not or incompletely copied off the mounted ISO image.
What do you see if you mount the 3rd partition of that USB device and look inside the directory “/boot” ? There should be a subdirectory “/boot/extlinux” if all went well.

You can re-run the script with this commandline which will produce a LOT more feedback, I hope you are able to interpret it:

# sh -x iso2usb.sh -i /images/latest/slackware64-live-current.iso -v -o /dev/sdb

Comment from Boris
Posted: June 11, 2016 at 03:02

Hello Eric,

Are you planning on updating your VLC build to 2.2.4 or will you wait for 3.0 ?

I was originally only having visual artifacts playing *.mkv files with an intel HD 4000 in my laptop, but was able to fix that by increasing the buffer sizes. After building myself a computer with an nvidia graphics card I can’t seem to play any H.264 videos without them. Reading your post for the 2.2.2 release I installed mplayer/smplayer, and they were able to play anything wonderfully. I’m hoping a future version of vlc fixes these issues.

Thanks

Comment from bam
Posted: June 11, 2016 at 19:16

Hi Eric,
is it possible to “sign in” somehow to your site so that I do not have to fill out name and e-mail to put comments every time?

Comment from alienbob
Posted: June 11, 2016 at 20:54

You can not sign in to this site. You need to enter name and optional email/website every time.

Comment from bilbo
Posted: June 14, 2016 at 11:17

hi eric,
for a printer to work i need the glibc-solibs from your multilib packages, and i just wonder if i only replace the slackware standard package of it with that one it would not cause any issue with my pure 64 bit?

Comment from alienbob
Posted: June 14, 2016 at 12:02

Hi bilbo, you can replace the Slackware glibc-solibs package with its multilib version without penalty. But if you have other glibc packages installed as well, you should replace all of them with their multilib versions.

There’s no need to install multilib versions of gcc unless you want to *compile* a 32bit binary, and there’s no need for any of the “-compat32” packages unless you are using a proprietary 32bit program that requires a 32bit Slackware library.

Comment from _metic
Posted: June 16, 2016 at 11:37

Dear Eric,
I wanted to ask you a question re:Other work world IBM.
I believe you able to circumnavigate with Slackware at the Corp Office.
Can you elaborate if you are able how you coaxed this circumnavigation in favor of Slackware as your work laptop.

Applications and what not. (Calendaring, Corp Email, Corp GPolicy, Tools, etc.??

Maybe you have already mentioned this somewhere but I am really interested, for practical matters for me.

Source:
http://www.mylinuxrig.com/post/100003933891/the-linux-setup-eric-hameleers-slackware-linux

Warm regards

Comment from alienbob
Posted: June 16, 2016 at 12:37

Hi _metic

Nowadays, IBM uses RHEL internally on employee computers with a layer of business applications on top of it. These internal IBM applications are witten so that they work both on Linux and on the Windows 7 platform which is also still used.

IBM does not care what you run on your laptop, as long as you adhere to all security guidelines, you install the corporate asset management tools and deliver the work they pay you to do.

In the past, I collaborated with other people at IBM who were Slackware fans like me and we made Slackware packages available to be able to do our daily job with Slackware. At that time, Windows XP was the only officially supported client platform even though a lot of people were already working on the creation of an internal Linux platform. I dual-booted Windows and Slackware.

Nowadays, I just use the RHEL7 installation for work, with Slackware running in a virtual machine.

Comment from _metic
Posted: June 16, 2016 at 13:34

Thank you for your response!

Comment from Hubert Phava
Posted: June 16, 2016 at 20:08

Hi Eric… First of all, thanks for your efforts.
Downloaded and installed latest kde5-packages on a fresh
64–current machine.
The question: is there a way to have the “Delete” button back in contestual menu in Dolphin?
I’ve searched but foud nothing, both in Kde docs and the net. I know that using “Shift+Del” makes the job but for me is better rightclicking the mouse.
Any suggestion?
Thanks again
HP

Comment from alienbob
Posted: June 16, 2016 at 21:01

Hubert Phava, no idea what functionality you are talking about, never use graphical programs to delete stuff.
If some functionality in KDE has gone missing, the best thing to do is open a KDE bug report. And search the bugtracker first; perhaps someone ran into the same issue and already reported it.

Comment from alienbob
Posted: June 16, 2016 at 21:20

Hubert Phava, next time post your questions in the relevant article, for instance the Plasma5 article I wrote yesterday and which probably made you download and install them.

I did your homework for you. This time only.

Go to Dolphin’s “Control” menu and select “Configure Dolphin…”. Click on “Services” in the left pane and scroll to “Delete” in the right pane. Add a check in its checkbox and click “OK”.
Now when you right-click in Dolphin there will be a “Delete” choice in the context menu.

Comment from Hubert Phava
Posted: June 16, 2016 at 22:52

TY Eriic and i apologize for my wrong posting… 🙁

Comment from cwizardone
Posted: June 17, 2016 at 01:11

> hu Jun 16 09:39:25 UTC 2016
> qt5: updated to 5.6.1 for Slackware-current (depends > on libxkbcommon which you will find in the same
> repository).
> qt5-webkit: updated to 5.6.1 for Slackware-current
> (depends on qt5)

As qt5 is not part of -current, I guess you are saying this is required if someone is using your KDE-5 packages in -current?

Comment from alienbob
Posted: June 17, 2016 at 01:20

You are mixing up two separate repositories.
If you are using my KDE 5 (Plasma5) packages you will already have installed my qt5, qt5-webkit and libxkbcommon packages since they are part of its “deps”.
These packages that got an update in my regular repository are meant for those people who do not care for Plasma5 but do need Qt5.

Comment from orbea
Posted: June 17, 2016 at 19:12

Some users have run into issues as reported at ##slackware because of this:

$ md5sum slackware-current-install-dvd.iso MD5SUM
34d952b4312d98122e48a73d41337e0b slackware-current-install-dvd.iso
e334ab7590a70c137298bd44aa78f1e8 MD5SUM

Can you please fix it?

Source: http://bear.alienbase.nl/mirrors/slackware/slackware-current-iso/

Comment from MachinaeWolf
Posted: June 17, 2016 at 19:18

Same here though I got a different md5sum on the .iso for some reason
3983a9925dc81c520df6cda5a19406e5

Comment from alienbob
Posted: June 17, 2016 at 20:24

orbea explain to me what I should learn from your post?

Comment from alienbob
Posted: June 17, 2016 at 20:29

This is how you should test the md5sum:

root@bear:/mirrors/slackware/slackware-current-iso# md5sum –check MD5SUM
slackware-current-install-dvd.iso: OK
slackware-current-mini-install.iso: OK
root@bear:/mirrors/slackware/slackware-current-iso# cat MD5SUM
34d952b4312d98122e48a73d41337e0b slackware-current-install-dvd.iso
4c31c5801b78fe144f69b57d9357e325 slackware-current-mini-install.iso

Comment from MachinaeWolf
Posted: June 17, 2016 at 21:03

Well I tried to install packages from the iso in a chroot and it said the tarballs were corrupt. Then I tried installing it in virtualbox and on the installer it wouldn’t let me setup any partitions at all. I selected the option to start partitioning on the main menu of the installer and it just loaded it right back to that.

Comment from alienbob
Posted: June 17, 2016 at 21:22

MachinaeWolf your MD5SUM is incorrect so your download is corrupt. That is the cause of all your issues.
And orbea could calculate the correct MD5SUM so his downloaded ISO is actually OK. However he used the wrong command and therefore made the wrong assumptions.

Comment from MachinaeWolf
Posted: June 17, 2016 at 21:32

I downloaded it via wget and wget -c says it’s got the whole file. I’ll try again then…

Comment from orbea
Posted: June 17, 2016 at 21:40

Sorry, I did not understand how to check the MD5SUM, thanks for the correction.

$ md5sum –check MD5SUM
slackware-current-install-dvd.iso: OK
slackware-current-mini-install.iso: OK

Comment from MachinaeWolf
Posted: June 17, 2016 at 22:51

Ok well I just did that too and it’s fine but my chroot I’m trying to make doesn’t want to install packages. I mount the iso and then cd to the mounted location and then cd slackware and do
$ installpkg –root ~/tmp/chroot/ a/*.t?z
and I get a load of errors like
Verifying package zoo-2.10_22-i486-1.txz.
/sbin/installpkg: line 378: /home/todd/tmp/chroot/var/log/setup/tmp/tmpsize9510: No such file or directory
/sbin/installpkg: line 378: /home/todd/tmp/chroot/var/log/setup/tmp/tmplist9510: No such file or directory
Unable to install a/zoo-2.10_22-i486-1.txz: tar archive is corrupt (tar returned error code 1)

Comment from alienbob
Posted: June 17, 2016 at 22:52

orbea – your files check out, excellent!

MachinaeWolf – there’s the off chance that you have been downloading the ISO while it was just being re-generated. The server regenerates the ISO whenever an update to the ChangeLog.txt is detected (this check occurs once every hour).

Comment from MachinaeWolf
Posted: June 17, 2016 at 22:53

Well it seems to like to take 2 hours to download at least every time…

Comment from MachinaeWolf
Posted: June 17, 2016 at 22:59

Oh I realized my error… I mounted the iso to the chroot directory I was trying to install the packages to. It’s working now that I have that sorted out.

Comment from alienbob
Posted: June 17, 2016 at 23:04

What’s your download speed MachinaeWolf ? Two hours is awfully long for a 2.7 GB file.

Comment from cwizardone
Posted: June 18, 2016 at 03:51

> Comment from alienbob
> Posted: June 17, 2016 at 23:04

> What’s your download speed MachinaeWolf ? Two
> hours is awfully long for a 2.7 GB file.

Just FYI, but since it was setup, your “bear” mirror has been consistently and considerably slower than other mirrors I’ve used.

Comment from alienbob
Posted: June 18, 2016 at 10:47

Then it is good that there are more mirrors than just bear 😉

Comment from andy
Posted: June 28, 2016 at 17:55

Ninety nine percent of the time I have no trouble or learning curve with slackware even areas that i would assume would be quite a challenge like installing virtual box is Ok because it only involves a build script , source and then installpkg command. Recently though concerning PHP which is 5.4.20 (cli) (built: Oct 11 2013 20:41:59) on 14.1 is not enough for some stuff i want to play with like Zend framework that needs 5.5 Now in /var/log/packages i can see php-5.4.20-i486-1 so i naively thought i should be able to upgrade & then deps phpadmin . It doesn’t look like being that simple . Assuming i’m not interested in having a LAMP stack but just need my core PHP upgraded to >= 5.5 whats the procedure?

Comment from alienbob
Posted: June 28, 2016 at 21:29

You should never mix packages from two different Slackware releases (-current is something entirely different from 14.1) because of the different libraries the packages link to.
Just build a new php package from the sources you can find in the slackware-current tree and you will end up with a package that works on Slackware 14.1.

Comment from andy
Posted: June 29, 2016 at 12:12

cheers bob , when i ran $php -v it came up stating various libs missing & nothing clear on googling . I was about to just remove the install, then saw your post on slackpkg+ its seemed to have ungraded everything to current . bash-4.3$ php -v
//gives :
PHP 5.6.23 (cli) (built: Jun 24 2016 17:18:09)
and with a larvel in home , $php artisan serve works & gives no problem. So it looks Ok with desktop icons looking more modern etc

Comment from John B
Posted: June 30, 2016 at 23:38

Eric,

I noticed that the Document Foundation has released Libreoffice 5.1.4 to patch a vulnerability in how it handles RTF files. The CVE entry for the vulnerability is here: https://www.libreoffice.org/about-us/security/advisories/cve-2016-4324/. A report from Cisco Talos with additional explanation is here: http://www.talosintelligence.com/reports/TALOS-2016-0126/

Comment from alienbob
Posted: July 1, 2016 at 00:20

Hi John.
I have a big TODO…

Comment from preston
Posted: July 8, 2016 at 16:13

Dear alienbob,
I am having various issues with PXE booting the most current version of Slack-ware live. After it boots the kernel, I get an error regarding Cg-manager and how it can’t find cgroup subsystems causing the computer to shut down. After messing around with some scripts in the iso image file to make Cg-manager non executable, the computer would still shut down regardless of the Cg-manager error being gone. Any wisdom or guidance would be much appreciated.
Best wishes,
Preston

Comment from Boris
Posted: July 9, 2016 at 03:09

Steamclient has issues with the latest mesa 12.0 on current.

libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast

Comment from Boris
Posted: July 9, 2016 at 03:33

please ignore my last message. Error on my part.

Comment from cwizardone
Posted: July 10, 2016 at 14:34

Good afternoon.
Many thanks for the VLC update.
Just for general information, with the last couple of updates, and including this one, I get some flicker when playing DVDs. Doesn’t happen when playing a video file off the hard drive.
Also, when installing the last couple of versions of VLC, including this one, the following error is generated,

Executing install script for vlc-2.2.4-x86_64-1alien.txz.
Could not parse file “usr/share/applications/winecfg.desktop”: Key file contains unsupported encoding ‘”UTF-8″‘
Generating VLC plugins cache data…
Package vlc-2.2.4-x86_64-1alien.txz installed.

Again, just FYI.
Thanks for all your work which is “…above and beyond the call….”
🙂

Comment from jim jowski
Posted: July 11, 2016 at 09:23

I hacked around make_slackware_live.sh and have a diff that adds command line options for a different username (something other than ‘live’), a different user password, and a different root password.

It’s at http://dogpoker.space/make_slackware_live.sh.diff and all comments are welcome. The connection may be slow but it’s a small file (less than 7k).

Love your work, Eric.

Thanks,
Jim

Comment from jim jowski
Posted: July 12, 2016 at 16:01

I fixed a few errors and omissions that slipped by MIdnight Testing. The currently posted diff has been tested and works like it should.

Jim

Comment from peebee
Posted: July 13, 2016 at 17:26

32 bit PepperFlash 22.0.0.209
is available again from:
http://www.adobe.com/go/getflash

Comment from alejandro
Posted: July 16, 2016 at 04:40

Hola e instalado slackware 14.2 plasma vivo en mi pc pero que contraseña usa luego de la instalacion pues no doy con cual es saludos

Comment from p431i7o
Posted: July 17, 2016 at 01:43

hola Alejandro, prueba usar el usuario live con el password:
live
tambien esta el usuario root
con el password:
root
Saludos

Comment from alienbob
Posted: July 19, 2016 at 13:57

peebee yes I will see if my future pepperflash packages can use that as a source. At least we will have a 32bit Flash plugin for Chromium again then (and for Firefox users who install the freshplayer plugin as well),

Comment from alienbob
Posted: July 19, 2016 at 14:04

Preston I have noticed the cgmanager related errors here too but I do not know what to do about them. I know too little of cgroups to debug the issue.
They do no harm here so I let them for what they are. Your shutdown appears unrelated to cgmanager anyway, from what I read of your description so there must be something else going on. Can you see what is happening in the console right before the shutdown? Apparently the live init completed successfully and your issue is somewhere in the Slackware configuration (may still be something custom I added to Slackware Live).

Comment from alienbob
Posted: July 19, 2016 at 14:15

Hi jim jowski – that’s the good thing about open source… you can change all the bits 🙂
However I will not apply your diff to the liveslak sources. The username “live” is immutable as far as I am concerned – this is a Live Edition anyway.
People who re-generate the ISO from scratch and want different values for the ‘live’ and ‘root’ passwords should use the configuration file “make_slackware_live.conf” to specify those non-default strings.

Comment from alienbob
Posted: July 19, 2016 at 14:19

alejandro, you were lucky that p431i7o answered your question…. this is an english blog for good reason: I do not speak or understand spanish (or portuguese for that matter).
Thanks p431i7o ! Perhaps http://docs.slackware.com/slackware:liveslak needs someone to write a proper translation!

Comment from p431i7o
Posted: July 19, 2016 at 15:42

Yeah, I’ll translate it to spanish.

Comment from alejandro
Posted: July 19, 2016 at 20:08

Hello my question is I wanted to install live on my pc , slackware 64 kde 5, and I did the problem it is that the plasma wallet does not accept me I put passwords .But if I turn and pressed ctrl + alt + f2 me ACETA root passwords , the query is that why not allow me to start the greetings I am from Uruguay and I hope the translation and thanks for the previous reading as this is understood.

Comment from lemin
Posted: July 19, 2016 at 20:15

Hi alienbob,

I suggest you could include the package “breeze-kde4” in your ktown repo to introduce the breeze theme for qt4 apps

Thanks for all

Comment from jim jowski
Posted: July 19, 2016 at 22:02

Thanks for the reply, Eric. I understand your position fully. I can see where Slack-on-a-stick could be useful in a work setting which is why I did what I did. I can change the ‘diff’ to remove the command line options and leave in the variable changes to make_slackware_live.conf the place for the changes if you’d like.

Comment from alienbob
Posted: July 19, 2016 at 22:54

lemin the “breeze” package in the ‘ktown’ repository contains the theme libraries for both KDE 4 and Plasma 5. No need for a separate package.

Comment from alienbob
Posted: July 19, 2016 at 23:43

jim jowski, no need for a revised diff. You explained in proper detail why a useraccount other than the name “live” would be useful.
So I implemented a LIVEUID variable in the scripts (to be set in the .conf file and defaulting to “live”) and then looked at your posted .diff file. Almost identical except for the variable name – and the added commandline switches of course.
I added one more line: the skeleton files contain some ocurrences of the string “/home/live” and I fixed those too for the ${LIVEUID}.

These changes will end up in the git repository sometime soon, but I just started working on a new ‘ktown’ package set and that takes my time now.

Comment from alienbob
Posted: July 20, 2016 at 00:41

alejandro – Google translate is not the best option to communicate… I do not understand if you have a problem with the Wallet password in Slackware Live, or after you have installed Slackware on your harddisk using the “setup2hd” script of Slackware Live.

Comment from jim jowski
Posted: July 20, 2016 at 05:54

Works for me! 🙂 I’ll patiently wait for your git.

Thanks,
Jim

Comment from icewalker51
Posted: August 4, 2016 at 01:43

I am enjoying experimenting with slackware live. It runs very fast on a USB3.0 — faster than the installed Win 10. That makes me very happy. You have done amazing work. Thank-You.

Comment from alienbob
Posted: August 4, 2016 at 09:29

icewalker51 – nice.

Comment from inman
Posted: August 5, 2016 at 13:32

hi eric,
I’m just curious about the missing underscore before alien tag in ur packages’ names 😀 … since it is somehow an unspoken rule, that everyone follows, and make ppl’s scripts for handling 3rd parties’ packages look prettier and robust! 😉
I know it is too much to ask, and you will probably kill me for asking this, but you are for sure master of those tiny scripts for changing something this little and make many of us lazy consumer happy! :))))
cheers

Comment from alienbob
Posted: August 5, 2016 at 14:37

Eh, “it is somehow an unspoken rule, that everyone follows, and make ppl’s scripts for handling 3rd parties’ packages look prettier and robust” ?

There is no such rule. Everything is OK as it is.

Comment from jim jowski
Posted: August 8, 2016 at 02:45

Eric,

Is libva still a dependency for your wine package?

Jim

Comment from alienbob
Posted: August 8, 2016 at 09:52

jim – I forgot to add libva to my virtual machine when compiling wine for Slackware 14.1 and that is why that dependency is not needed now. Obviously that is not what I intended, since the lack of libva means you will not have GPU video acceleration in Wine.
I will re-add libva as dependency for the Slackware 14.1 build next time.

On Slackware 14.2/current the libva package is already part of the distro so that was properly picked up by the wine package for those releases.

Comment from Moun
Posted: August 8, 2016 at 13:41

Hi,

Maybe I did something wrong… I’ve noticed a little issue with the Slackbuild for firefox localization : I had to provide VERSION=45.2.0esr to get it able to download the xpi file, but then the filetree inside the build package became “/usr/lib64/firefox-45.2.0esr” instead of “/usr/lib64/firefox-45.2.0”

In fact releases.mozilla.org/[…]/45.2.0/[…] isn’t a valid url but releases.mozilla.org/[…]/45.2.0esr/[…] yes so using VERSION=45.2.0 won’t make the automatic download working.

I had to 1) download the esr xpi 2) rename it to 45.2.0 (instead of 45.2.0esr) 3) build package using VERSION=45.2.0

Regards.

Comment from alienbob
Posted: August 8, 2016 at 14:43

Moun, the SlackBuild was not written with Extended Support Releases in mind.
You found a way to create a working package for Firefox ESR using some minor adjustments, so there is nothing “wrong” in what you did.

Comment from Moun
Posted: August 9, 2016 at 00:26

Ok thanks for your answer. I’ve just understood that this SlackBuild was written for Slackware *current*. ESR type is only included in “stable” versions…

Comment from R.H.
Posted: August 12, 2016 at 21:44

Will multilib ever be folded into the Slackware official packages? Have you written up the steps to build the multilib packages? I would try to do it but not sure what’s involved. Would it be possible to package up the environment to make multilib packages? Then maybe those packages could be included with official Slackware and those that need it can install the multilib-build package and build multilib for themselves.

Is this a boat load of work?

Comment from alienbob
Posted: August 13, 2016 at 00:01

R.H. multilib will not be added to the Slackware distribution.

You can grab my packages or build your own. The process is written down in the README. All you need is an existing set of glibc and gcc multilib packages and install those. Download my glibc-multilib.SlackBuild and gcc-multilib.SlackBuild scripts and copy those into the official source directories, then launch both scripts and wait for new multilib packages to appear.
For the other “compat32” packages you can use my massconvert32.sh script that generates those from the official 32bit Slackware packages.
Have you actually read the documentation?

Comment from R.H.
Posted: August 13, 2016 at 03:33

I did read the doc at the top of the site where the multilib lives. But I guess I failed on the comprehension. Thank you for taking the time to set me straight and sorry for that.
I’m going to have to make room to build all this on my system as I suspect it will need many GBs of storage.

I just updated to your release of the multilib packages and I am having problems with stddef.h. Not sure what’s going on yet.

Comment from peebee
Posted: August 16, 2016 at 16:03

Libreoffice-5.1.5 has a serious display bug which makes it virtually unusable:
https://bugs.documentfoundation.org/show_bug.cgi?id=101213
https://bbs.archlinux.org/viewtopic.php?id=215647
LO-5.1.4 seems to be OK.

Comment from alienbob
Posted: August 16, 2016 at 16:14

So, it looks like https://cgit.freedesktop.org/libreoffice/core/commit/?id=d89abe0806947149eafbd9d7ce4b3095ec38b236&h=libreoffice-5-1 has to be applied to the 5.1.5 source code because otherwise we would be waiting for a 5.1.6 release until the end of october.

Comment from Alex
Posted: August 19, 2016 at 01:47

Hi

Feedback? do you guys REALLY care?
Let’s see then:

1- Make a official Bug-tracking system FGS! or create an official EMAIL for reporting bugs(not just for security bugs)

2- Clean the website from old/crap subpages

3-Replace Packages’s link from http://slackware.com/packages/ to http://packages.slackware.com. (whats the point of displaying OLD and useless page?)

4-Why not merge ALL packaing tools to one? like slackpm, spm, etc or something?

5- Merge ALL Slackware package/software repositories to one Central repository! (yours, slackbuilds.org, vbatts, http://rlworkman.net/pkgs/ and…)
Ofc everyone can have their own package center, but not SW team (IMO)

GL

Comment from alienbob
Posted: August 19, 2016 at 09:31

Alex, please note that I am not affiliated with Slackware, Inc. Your rants will have to be addressed at info@slackware.com.
In the meantime, I can give you some answers, because it is good that you care.

(1) A bug tracker requires (human) resources which the small team of one person (plus a few volunteers like me) can not spare. You have issues, spill them on the linuxquestions.org forum like everyone else does, and you will be heard.

(2) It may happen during this development cycle. Again, it is a matter of prioritization. For up to date information on Slackware, please visit http://docs.slackware.com/

(3) Would be addressed by (2)

(4) There are several 3rd party tools that are not part of Slackware (the ones you mention I do not recognize so they are surely 3rd party) and other than that, they are integrated. slackpkg works by calling the various components of the pkgtools. And there’s no more to it than that.

(5) There is a central repository only for Slackware itself. The rest is not “official”. Me, Robby, Vincent, we are all not getting any money out of this, we do it as a hobby, for fun. Either of us can just stop releasing packages or even abandon Slackware if “real life” became more timeconsuming or more important, and who would then maintain our packages in the “central repository”? Again it is a matter of resource prioritization. We leave Pat to keep the core distro running while the rest of us creates the dressing.

(6) As for your challenging and condescending tone, it does not become you. You have issues with Slackware? Deal with it or move on.

Comment from Brian
Posted: August 19, 2016 at 10:10

Excellent response, alienbob!!

Comment from darkstaring
Posted: September 1, 2016 at 11:51

I installed the last KDE 5_16.08_testing
But i get this error in configuring skype account:
<<>>
And google hangout not working…
Thank you

Comment from alienbob
Posted: September 1, 2016 at 21:44

If you install a “testing” release of mine, I really do expect that you know what you are doing. And actively try to find solutions for your issues instead of letting me guess what’s wrong on your computer. Please install the ‘latest’ release instead.

Comment from darkstaring
Posted: September 2, 2016 at 19:04

all works fine
unless instant messaging

Comment from Eduardo
Posted: September 4, 2016 at 02:42

Hi Eric, I installed KDE 5_16.08 latest. So far everything works great. Thanks!

Comment from John D
Posted: September 4, 2016 at 10:16

I’m running Slackware 14.2 with the provided NetworkManager 1.2.2-x86_64 on an AMD A8-7410 APU (Dell Inspiron 15 – 5000 Series).

For one reason or another I lost the ability to browse the internet and, suspecting malware, formatted the partition and reloaded the O/S. The problem persisted, turning out to be a DNS issue (possibly related to the ISP intercepting/redirecting DNS requests).

If I put the nearest router IP in /etc/resolv.conf, that worked until the next time I rebooted, then it came up with information varying from being updated by Network Manager to eth0.dhcpd. In no case did it have the DNS servers ip numbers. If I manually populated it with the IP of the nearest upstream router, it worked until I rebooted, then, not so much.

Believing that dnsmasq could supersede NetworkManager and dchpd with hard-coded DNS server addresses, I enabled /etc/rc.d/rc.dnsmasq and opted in the /etc/dnsmasq.conf file as follows:

no-resolv
no-poll
server=209.244.0.3
server=209.244.0.4

That did not get me DNS lookups. Instead, something was trying to do DNS lookups on the loopback interface so I opted for:

interface=eth0

… in the /etc/dnsmasq.conf file but that also had no effect. So, noticing that the contenst of /etc/resolv.conf sometimes came from /var/run/NetworkManager/resolv.conf, I tried changing that but it also changed as I rebooted but I figured there was a way to configure Network Manager. Looking in /etc/NetworkManager I found a pointer in NetworkManager.conf to /etc/NetworkManager/conf.d but that was about all I found there.

/etc/NetworkManager/conf.d/00-dhcp-client.conf offered the ability to change the DHCP client from the Slackware default but what would be the trickle-down consequences of that?

I’m a newbie and trouble-shooting is an involved process.

Ultimately, I solved the problem by adding:

dns=dnsmasq

…to the /etc/NetworkManager/NetworkManager.conf file.

I’m guessing you have input on the ultimate densign and release info of Slackware. I don’t see that documented anywhere in Slackware but I’d like to suggest a helpful documenting in the NetworkManager.conf file, i.e.:

# Uncomment the following line if you have /etc/rc.d/rc.dnsmasq enabled and dnsmasq.conf configured.
# dns=dnsmasq

That may be obvious to you and there may be some documentation on NetworkManager or Slackware I’m overlooking but maybe some other newbie would benefit from my experience just by having that comment in the .conf file.

As for the original problem that caused me to reload the O/S, it seems the DNS replies were coming back to the router from TestNet3 (203.0.113.0/24). I don’t know why. I block those kinds of IANA IP ranges, at all junctures, owing to their reputation for being associated with attacks.

Anyway, this fix works. Hope it helps someone else.

Comment from alienbob
Posted: September 4, 2016 at 17:00

Hi John,

The issue you describe is not specific to any customization I offer for Slackware, but since this is the feedback section I have an answer for you.

You enabled dnsmasq to overcome an issue with your local ISP but dnsmasq does not “do” anything by itself – you have to actively use it just like any other service. So you found the correct way to let NetworkManager query dnsmasq as a DNS resolver by adding “dns=dnsmasq” – good!

Not every user-contributed hint and information needs to go into Slackware’s core though – that puts an unnecessary burden on the maintainer (Pat). That is why we now have the Slackware Documentation Project where you can become a contributor to the shared body of knowledge about the Slackware distribution and its use.

Comment from jim jowski
Posted: September 7, 2016 at 01:09

I know the fix is simple but this is driving me crazy. I’m building a custom iso for slackware64-current using make_slackware_live.sh and it builds. When I try to put it on a USB stick I get the following:

— Making the USB drive ‘/dev/sdi’ bootable using extlinux…
/mnt/alienusb.k1nthW/boot/extlinux is device /dev/sdi3
rsync: mkstemp “/mnt/alienus2.BiepOV/EFI/BOOT/theme/.index.html?C=D;O=A.TFxi0r” failed: Invalid argument (22)
rsync: mkstemp “/mnt/alienus2.BiepOV/EFI/BOOT/theme/.index.html?C=D;O=D.7NtYks” failed: Invalid argument (22)
rsync: mkstemp “/mnt/alienus2.BiepOV/EFI/BOOT/theme/.index.html?C=M;O=A.zFNEFs” failed: Invalid argument (22)
rsync: mkstemp “/mnt/alienus2.BiepOV/EFI/BOOT/theme/.index.html?C=M;O=D.pOll0s” failed: Invalid argument (22)
rsync: mkstemp “/mnt/alienus2.BiepOV/EFI/BOOT/theme/.index.html?C=N;O=A.RCn2kt” failed: Invalid argument (22)
rsync: mkstemp “/mnt/alienus2.BiepOV/EFI/BOOT/theme/.index.html?C=N;O=D.GuDJFt” failed: Invalid argument (22)
rsync: mkstemp “/mnt/alienus2.BiepOV/EFI/BOOT/theme/.index.html?C=S;O=A.05er0t” failed: Invalid argument (22)
rsync: mkstemp “/mnt/alienus2.BiepOV/EFI/BOOT/theme/.index.html?C=S;O=D.F9k9ku” failed: Invalid argument (22)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2]
*** ./iso2usb.sh FAILED at line 691 ***
— Cleaning up the staging area…

I can’t find the offending files using locate.

Jim

Comment from jim jowski
Posted: September 7, 2016 at 08:24

I was able to find the offending files (they are created by ‘wget’) and remove them. What now puzzles me is the differences between the EFI directory in http://bear.alienbase.nl/mirrors/people/alien/liveslak/ and http://mirrors.slackware.com/slackware/slackware64-current/. Bear has EFI/BOOT/theme and the other one doesn’t. Is the theme directory really needed?

Jim

Comment from Anton
Posted: September 7, 2016 at 13:25

Hello, Eric.

In Slackware64-14.2 cdrecord does not write DVD disks from regular user but only from root despite I have included my user into cdrom group. It shows next errors:

$ cdrecord dev=/dev/sr0 slackware64-14.2-install-dvd.iso
Cdrecord-ProDVD-ProBD-Clone 3.01 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2015 Joerg Schilling
cdrecord: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler.
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Insufficient ‘file read’ privileges. You will not be able to open all needed devices.
cdrecord: Insufficient ‘file write’ privileges. You will not be able to open all needed devices.
cdrecord: Insufficient ‘device’ privileges. You may not be able to send all needed SCSI commands, this my cause various unexplainable problems.
cdrecord: Insufficient ‘memlock’ privileges. You may get buffer underruns.
cdrecord: Insufficient ‘priocntl’ privileges. You may get buffer underruns.
cdrecord: Insufficient ‘network’ privileges. You will not be able to do remote SCSI.
scsidev: ‘/dev/sr0’
devname: ‘/dev/sr0’
scsibus: -2 target: -2 lun: -2
Warning: Open by ‘devname’ is unintentional and not supported.
Linux sg driver version: 3.5.27
Using libscg version ‘schily-0.9’.
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : ‘ASUS ‘
Identifikation : ‘SDRW-0806T-D ‘
Revision : ‘AE07’
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Using generic SCSI-3/mmc-3 DVD+RW driver (mmc_dvdplusrw).
Driver flags : NO-CD DVD MMC-3 SWABAUDIO BURNFREE
Supported modes: PACKET SAO LAYER_JUMP
cdrecord: Warning: Cannot read drive buffer.
cdrecord: Warning: The DMA speed test has been skipped.
cdrecord: Operation not permitted. rezero unit: scsi sendcmd: fatal error
CDB: 01 00 00 00 00 00
cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl.
cdrecord: Operation not permitted. Cannot open or use SCSI driver.
cdrecord: For possible targets try ‘cdrecord -scanbus’. Make sure you are root.
cdrecord: For possible transport specifiers try ‘cdrecord dev=help’.

Best Regards,
Anton.

Comment from Anton
Posted: September 7, 2016 at 18:41

Hello, Eric.
I have solution of this problem. I just did next steps:

# ls -l /usr/bin/cdrecord
-rwxr-xr-x 1 root root 480232 May 31 22:44 /usr/bin/cdrecord

# chown root:cdrom /usr/bin/cdrecord

# chmod u+s /usr/bin/cdrecord
.

Now cdrecord works fine from regular user. And i think it would be nice if you have included these strings into the doinst.sh script of cdrtols package, of course, if you find this solution to be acceptable.

Best Regards,
Anton.

Comment from alienbob
Posted: September 8, 2016 at 12:30

Anton, I recommend reading the CHANGES_AND_HINTS file located in the root of every Slackware release. For Slackware 14.2 this file is located here: http://ftp.osuosl.org/pub/slackware/slackware64-14.2/CHANGES_AND_HINTS.TXT

Your issue with cdrecord is covered in that file.

Comment from alienbob
Posted: September 8, 2016 at 12:38

jim jowski, I think you are confusing two different things.
Liveslak creates a Live Edition of Slackware. For this, you need the directory “liveslak” plus everything below. You can download that directory tree from “bear” or any mirror but using “wget” for recursive downloads is probably the worst of all available options. Use “lftp” or “rsync” instead please.

The directory you mentioned: “EFI/BOOT/theme” is required by liveslak. It has nothing to do with the original Slackware. Therefore it is not present on an official Slackware mirror repository.

Comment from peebee
Posted: September 9, 2016 at 17:52

Hi Eric

Many thanks for Chromium-53 for 14.2 and current.

Will updates to the 14.1 version now freeze at Chromium-52?

Thanks
peebee

Comment from alienbob
Posted: September 9, 2016 at 20:54

peebee – I only create packages when I have time for that. And currently I need my time for Real Life issues.
So I can not answer your question.

Comment from jim jowski
Posted: September 9, 2016 at 21:08

Eric,

The more I use liveslack; the more I learn. 🙂 Those index files were aren’t removed when the “-f” option is used with make_slackware_live.sh. Now that I’m aware that both ‘lftp’ and ‘rsync’ can be used; I’ll use them. As for ‘wget’: old habits die hard. Twenty years of doing something is hard to change but change in this case is good.

Thanks,
Jim

Comment from Eduardo
Posted: September 10, 2016 at 18:39

Hi Eric,

The latest chromium package has a mixup with keyrings. In Plasma, upon starting chromium, there is a dialog that tells me that a “default keyring” needs to be accessed. And then, *some times* the KWallet dialog appears. At all times, chromium does not get my passwords and I have to relogin every time to my sites.

Thanks,

Eduardo

Comment from alienbob
Posted: September 10, 2016 at 19:57

Hi Eduardo,

I noticed that kwallet popped up with a request to create a new wallet when I started the upgraded chromium. But, I can not find any new wallet and all the passwords stored by chromium are still available in the browser and used to logon to sites automatically.

Comment from cwizardone
Posted: September 10, 2016 at 20:03

Eduardo wrote:
> The latest chromium package has a mixup with keyrings. > In Plasma, upon starting chromium, there is a dialog that > tells me that a “default keyring” needs to be accessed.

Yes, I’ve had the same problem when using chromium to log into Netflix. I figured out how to use widevine with Vivalidi and have not had the same problem, so it looks to be something, as Eduardo said, to do with chromium.

Comment from Sid
Posted: September 11, 2016 at 02:53

I’ve been a long time user of your slackbuilds. Sorry to hear that you are getting laid off. I recently retired from California to Japan, and was fortunate enough to do practically the same job for 33 years, but going from contractor to contractor. Best wishes finding a job soon. Your background and knowledge is far greater than mine.
Sid

Comment from Bjorn
Posted: September 14, 2016 at 15:18

Sorry to hear about you getting laid off and sorry for a non-technical question, I have made up my mind to start a career in IT. What IT technology/subject/certificate would you recommend for someone starting a career in IT for a relative long-term period; since most of the IT subjects available or recommended by the current academia are out of date/or would be out of date in the very near future. Your perspective from someone who has learned, worked and again needs to relearn would be very valuable for me.

Thank you

Comment from alienbob
Posted: September 14, 2016 at 15:49

Bjorn I can not comment on that. It would depend in what area of IT you want to pursue a career. If you are going to work as a network engineer, then a Red Hat certification does not make sense. If you want to make programming a part of your career, then courses in Java, Python and such would be an option. But ultimately, there is no good answer I can provide you with.

Comment from cwizardone
Posted: September 14, 2016 at 19:18

In reference to the problem reported by Eduardo a few messages back were
he said,

> The latest chromium package has a mixup with keyrings.
> In Plasma, upon starting chromium, there is a dialog that
> tells me that a “default keyring” needs to be accessed.

While I was using Vivaldi-1.3.551.38, this was not a problem. However I have just
upgraded to Vivaldi-1.4.589.11, and the problem has appeared just as Eduardo described it. According to the “help” content from the pull down menu, this new version of Vivaldi is based on chrome/53.2785.90/blink53736. So, as they say,
this problem appears to from “upstream.”
Just FYI.

Comment from Brian
Posted: September 16, 2016 at 21:48

AMD could use a good man with your great abilities

Comment from cwizardone
Posted: September 26, 2016 at 17:01

The problem mentioned two post back regarding “default keyring” has disappeared with the release of
Vivaldi-1.4.589.29.

Comment from alienbob
Posted: September 26, 2016 at 17:41

Then I assume that the issue will also disappear with the next release of Chromium. I still have to type two passwords to load my chromium passwords and preferences

Comment from Renato Maria Ferrari
Posted: October 7, 2016 at 21:10

Hello, Eric.
I am a 62 year old Italian Linux user, first with Red Hat, up to version 7.2, then inevitably with Slackware since 2001.
First of all I want to thank you for the great contribution you are giving to the development and maintenance of Slackware, and my compliments to the site your personal and Slackbuilds.org.
I have a question to ask.
I would like to create me my personal repository compiled Slackware packages (the ones that I keep in my hard drive dedicated to it) and to create packages.txt files using the script of slapt-get; but despite having read dozens of web pages, I have looked everywhere, I do not know how to generate the MANIFEST.bz2 file.
I tried to use your gen_repos_files.sh script but, unfortunately, is too complicated for my knowledge of the bash script and, above all, ask me generation and the keys used for encryption that I never use.
I thank you right now if you have time and desire to help me or suggest me where to find the instructions for creating a personal website compiled packages.
Sorry if I express myself badly, but I know little English and I relied on Google translator.

Ferrari Renato Maria

Comment from alienbob
Posted: October 7, 2016 at 22:05

Hi Renato,

The script “gen_repos_files.sh ” has a parameter “-h” which will display some helpful text. It should not be too hard to use even for people without shell scripting skills.
If you do not have a GPG key, the script will warn that it will not be able to generate GPG signature files but it’s only a warning which you can safely ignore.

The one thing you are required to do before using that script is to run the command “uuidgen -t” and copy the resulting UUID string into the script’s “RSS_UUID” variable. If you are not sure you can do that, there is an alternative, which is to create a configuration file which the script will always use when it runs,
Create a new file in your homedirectory and call it “.genreprc”.

In that file, copy the following lines, and make sure that you write something sensible inbetween the empty “” strings:

REPOSROOT=””
REPOSOWNER=””
RSS_UUID=””

The REPOSROOT variable must contain the directory where you keep your package repository.
The REPOSOWNER variable should contain your name and optionally your email address. It will be used to search for a GPG key and it will be used in the repository metadata files.
And finally, RSS_UUID variable must contain the output of the command “uuidgen -t”. This is a string which uniquely defines your repository.
You can add more variables to the “.genreprc” file but they are all optional.
When you have created this file, you can run the script and that should generate the MANIFEST and other files.

Comment from My truth
Posted: October 19, 2016 at 18:32

Hi Eric! You plan to build Plasma 5.8?

Comment from cwizardone
Posted: October 24, 2016 at 01:42

> Sun Oct 23 10:24:48 UTC 2016
> veracrypt: updated to 1.19.

Thank you very much. Greatly appreciated!

Comment from Ivan Tushev
Posted: October 24, 2016 at 14:39

Hi Eric,
I’ve been using your vlc binaries for some time and had great experience with them so far. Today I’ve setup a 64bit Slack v14.2 and installed your latest restricted build of vlc (vlc-2.2.4-x86_64-1alien.txz). It worked great until I needed to use phantomjs which is dependant on libfontconfig. I’ve installed the official slackware64/x/fontconfig-2.11.1-x86_64-2.txz and since then vlc breaks with Segmentation fault. Removing fontconfig fixes the issue.
It will be great if can have a look. Thank you!

-Ivan

Comment from Renato Maria Ferrari
Posted: October 26, 2016 at 19:31

Dear Eric
on the MANIFEST file: thanks for your valuable suggestions: the program works fine.
The only small flaw was due to the fact that I had copied and pasted the instructions directly from this page; but ” of the web page are different from those of the bash script, correct my mistake, I resolved.
Thanks to script of Patrick Volkerding , of Eric Hameleer, to the Advanced Bash Guide, (and to my friend Emilio Conti that has translated into Italian), the Italian slackware http://www.slacky.eu community and all people who have posted on the web their script, I know a little ‘in bash programming; so I will try, as well, to automate the generation of my personal repositories.

Comment from fabio
Posted: October 29, 2016 at 06:29

thanks for the updated veracrypt package.

Comment from Eduardo
Posted: November 5, 2016 at 18:29

Hi Eric, just wanted you to suggest the addition of two packages to your KDE5 collection: KSnip and Krusader.

You may already know Krusader and KSnip is a tool very similar to the Win10 Snipping Tool

GitHub homepage:

https://github.com/Ssiws/KSnip

For Krusader, simply editing the SBo SlackBuild is what it takes to build it.

For KSNip, adapting any KDE app SlackBuild also works. In any case, I have SlackBuilds who build correctly both apps and I would be delighted to share them with you should you like to take a look at them.

Thanks again!!

Comment from Eduardo
Posted: November 5, 2016 at 18:31

I forgot to say:
I suggest Krusader because there is a new version (2.5.0) which is KDE5 only.

I suggest KSnip because I find the tool extremely useful, even better than Spectacle for a quick screen snip capture.

Thanks!

Comment from Eduardo
Posted: November 5, 2016 at 18:38

Sorry agaiin. Ksnip’s GitHub page was incorrect. Here is the correct one:

https://github.com/damirporobic/ksnip

There is also the linux-apps page:

https://www.linux-apps.com/p/1156408/

Apologies for the mistake.

Comment from alienbob
Posted: November 5, 2016 at 21:51

Eduardo,

There’s lots of packages that work well with Plasma 5, but I am not going to add any or all of them.
Dolphin and Spectacle are the official file-manager and snapshot tool, and I leave it at that.

Comment from cwizardone
Posted: November 8, 2016 at 20:36

> Sun Oct 23 10:24:48 UTC 2016
> veracrypt: updated to 1.19.

With the previous version it was not possible to close a “container” and it was necessary to terminate the program, which, in turn, closed the “container.”
With the latest version terminating the program, does, of course, close the program, but the container remains open. Now the only way to close the container is reboot the computer.
Just FYI.

Comment from alienbob
Posted: November 8, 2016 at 20:48

cwizardone if you find a fix let me know.
However, I have personally not experienced what you are describing. For me, dismounting the volume cleans up; no device-mapper entry remains.

Comment from martinowar
Posted: November 9, 2016 at 22:28

Hi,

hexchat is available in Slackware 14.2 / current. If there is not a special reason to keep it, maybe it is a candidate to be removed from the corresponding repositories?

Note: It appears in my slackpkg++ packages-to-be-upgraded list, that is why I inform you.

Comment from alienbob
Posted: November 10, 2016 at 00:19

martinowar yes I should take care of that.

Comment from boris
Posted: November 10, 2016 at 14:10

Calibre 2.71 has an error

This application failed to start because it could not find or load the Qt platform plugin “xcb”
in “”.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, xcb.

Reinstalling the application may fix this problem.
Aborted

I’ve had this error in the past and have the libxkbcommon package.

Post on linuxquestions about this from earlier this year.
https://www.linuxquestions.org/questions/slackware-14/calbre-fails-to-start-4175574668/

Comment from alienbob
Posted: November 10, 2016 at 14:18

Hi boris.

Is this on Slackware 14.2 or -current? If you installed Qt 5.7.0 then apart from ‘libxkbcommon’ you also need to install the ‘libinput’ package.

Comment from boris
Posted: November 11, 2016 at 04:37

-current, and was missing libinput.

Thanks

Comment from cwizardone
Posted: November 12, 2016 at 00:52

> Sun Oct 23 10:24:48 UTC 2016
> veracrypt: updated to 1.19.

> With the previous version it was not possible to close a “container” and it was
> necessary to terminate the program, which, in turn, closed the “container.”
> With the latest version terminating the program, does, of course, close the program, > but the container remains open. Now the only way to close the container is reboot the > computer.
> Just FYI.

> Comment from alienbob
> Posted: November 8, 2016 at 20:48

> cwizardone if you find a fix let me know.
> However, I have personally not experienced what you are describing. For me,
> dismounting the volume cleans up; no device-mapper entry remains.

Apparently it has something to do with KDE-4(in current) or a KDE-4 application.
That thought ocurred to me, so I exited KDE, ran xwmconfig, picked Xfce, started
the same, and was able to successful close the container that would not close while
running KDE. Don’t know if that makes any sense?
🙂

Comment from alienbob
Posted: November 12, 2016 at 01:04

That matches with my experience… I only use veracrypt on XFCE. I will have a look at what happens on KDE when I have some time.

Comment from cwizardone
Posted: November 12, 2016 at 01:23

Another thought is it just might have something to do with Gwenview.

Comment from cwizardone
Posted: November 17, 2016 at 18:53

BTW, “Welcome back,” so to speak. 🙂

Comment from p431i7o
Posted: November 20, 2016 at 02:24

sorry to bother you Eric,
but is there any chance of getting chromium-54 on slackware 14.1?
I saw it on 14.2 on your builds and that the files: chromium-53.0.2785.92-x86_64-2alien.lst and chromium-53.0.2785.92-x86_64-2alien.meta where updated on november 18th. So I thought there may be an update close.
I ask this because of this bug that came with chromium-53.0.2785 NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED https://bugs.chromium.org/p/chromium/issues/detail?id=665484&q=NET%3A%3AERR_CERTIFICATE_TRANSPARENCY_REQUIRED%20&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified that was supposedly solved on chromium-54

Comment from alienbob
Posted: November 20, 2016 at 10:22

I never had a chromium 53 package for Slackware 14.1. It’s currently still at chromium-52.0.2743.116 because I could not get chromium 53 to compile on Slackware 14.1.
I can try again with the new chromium 54.

Comment from p431i7o
Posted: November 20, 2016 at 16:01

Well, this is weird https://postimg.org/image/lkw4091sl/ so this is a chromium 52 package?

Comment from alienbob
Posted: November 20, 2016 at 21:24

I should have been more careful in my wording. The 32bit package could not be compiled successully so http://www.slackware.com/~alien/slackbuilds/chromium/pkg/14.1/ still has a chromium 52 package. But there is a 64bit package.
Compiling chromium 54 on 64bit Slackware 14.1 just failed, nevertheless. It looks like it still needs a patch I removed because it was not required on 14.2/current.

Comment from cwizardone
Posted: November 27, 2016 at 21:19

Regarding our discussion of Veracrypt a few messages back. After using Veracrypt this morning in KDE-4-in-current, it wouldn’t dismount a container, which is its usual behavior.
Just for chuckles I logged out of KDE, then started it again, with, of course, startx, and was able to close the container.
Just FYI.

Comment from alienbob
Posted: November 28, 2016 at 13:18

p431i7o I think I finally created a correct patch that allows chromium-54 to compile on Slackware 14.1. If the compilation completes without further issues, I hope to have the packages (64bit and 32bit) available tomorrow.

Comment from p431i7o
Posted: November 28, 2016 at 13:30

Thanks Eric!
that are great news,
I hope in this December make finally my transition at home of my desktop to Slackware 14.2
but this will relieve a situation at home (wife having much problems with Firefox and its flash player plugin) to watch Videos.

Write a comment