Main menu:

Sponsoring

Please consider a small donation:

 

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

 

Or you can donate bitcoin:

 

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

Page Rank

Fame

FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.

Search

My Favourites

Slackware

Calendar

September 2014
M T W T F S S
« Aug    
1234567
891011121314
15161718192021
22232425262728
2930  

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

Meta

What you do when it rains

alien

I had a great week in Bruges, Belgium. Visited the brewery “De Halve Maan” and had a tour of the new brewing hall as well as the museum with all the ages old brewing equipment. It ended with a free “Brugse Zot” blonde beer, unfiltered (you can get the unfiltered version only in the brewery’s own restaurant on-site). It really tasted great, more flavors than the bottled version.

I will try to post some of the pictures I took while roaming the city of Bruges (I nearly took 200) because it is a very pretty – Bruges is one of Unesco’s World Heritage sites. But anyway, we did not have rain during our stay (a few small showers perhaps). The rain started when we went back home. With that rain, I was less inclined to go out and walk for a bit, or work in the garden. Bread making is one of the things I am doing today (using my sourdough starter which survived a week in the fridge exceptionally well). But after a week of no computing, I wanted to do something again when I got home.

So I uploaded the KDE 4.14 packages and posted the blog article, all of which I had already prepared before traveling to Bruges. And then I looked at what else had been happening during my absence. Not much really :-) Some new systemd related threads on LinuxQuestions.org, which I am trying to stay out of (it’s a pretty hairy discussion in there), and some more talk about Skype 4.3 which needs PulseAudio now.

Perhaps I will pick up zerouno’s successful effort to package all the required 32-bit libraries along with the Skype binaries (he did not have to bother with PulseAudio then, so I think it will be more complex to make it work now)… if I find the time.

On Google+ I had attempted to find some answers to creating an OpenVZ container template for Slackware. I had hoped there would be updates during my holidays, but unfortunately the one guy (who also reads this blog of mine I believe) who has worked professionally with openvz and Slackware and whom I asked for advice did not answer. Probably too busy with his girl friend. Anyone who can help me out, please leave me a note. The G+ post contans a link to the script I wrote for the creation of that Slackware template.

kde44 I did have time this weekend to package KDE 4.13.3 for Slackware 14.1 – as promised when I wrote about KDE 414 for Slackware-current.

The KDE 4.13.3 packages for Slackware 14.1 are available at the usual location,  http://taper.alienbase.nl/mirrors/alien-kde/14.1/latest/. Those of you who like (or need) to use a stable Slackware version will now have the opportunity to enjoy a much-improved KDE. It includes the latest Calligra office suite and also the kdeconnect package (to interface with your Android phone from within KDE)  has been upgraded and has a lot more functionality now.

calibreico I also looked at the weekly update of Kovid Goyal’s Calibre package.

To my surprise he has promoted his beta version of Calibre 2 to production sooner than I expected which creates a dilemma for me. The new version 2.0.0 is no longer based on Qt4 but instead Kovid uses Qt5 for Calibre now, which allowed him to eliminate several longstanding Qt4 related bugs. My dilemma is, how should I treat the transition to Qt5 ? Should I embed the Qt5 libraries into the Calibre 2 package like I used to do long ago for Qt4 (which will greatly increase the package size) or should I request of you (users of my Calibre package) to install my Qt5 package along with the new Calibre? I would like your feedback before I decide to start building a Calibre 2 package. In the meantime, the “old” calibre-1.48.0 package will remain available in my repository.

ARM_powered_300px There were two questions in my old blog pages about the status of my hardfloat ARM port. I must say, the economical crisis and the condition of our remaining parents have resulted in me having a lot less free time, and the ARM port was a victim of that. I am at a point with that port that I need to re-sync to the latest stable Slackware and then transfer the packages to a real machine… I am a bit scared of that last part. Stuart’s Slackwarearm is very successful at installing onto ARM devices, because he uses a (modified version of the) real Slackware installer for that. WIth my ARM port I am noy yet sure if I want a “Slackware-like” installation using the setup script, or create an image file which you just have to copy to your ARM device. Note that the hardware which I had in mind for my port, is the Chromebook, or tablets even, Unlike the older embedded Linux devices, those are typically equipped with a ready-made OS image instead of running an installer. But the ARM port is not dead! I just need to get my act together.

Have fun! Eric

KDE 4.14.0 – no big surprises

The new major release of KDE 4 has been made available. KDE Software Compilation 4.14.0 is the first of four iterations which will all see the light of day this year, 2014 (KDE 4.14.3 will be released on 11 November). A relatively short cycle, caused by the parallel development towards Frameworks 5 and Plasma 5. What’s still missing for Plasma 5 is the KDE Application ports to Qt5 and the Frameworks and this is where most of the action is nowadays. There is nothing really worthwhile to mention about KDE 4.14 if you look at its feature plan. Nevertheless KDEPIM is being worked on a lot and judging by the activities in the applications’ GIT repositories everybody is still alive and kicking out code. The previously mentioned announcement page has more details about the individual application improvements.

Anyway, like I said: even though this is a new major release, it is more a polishing update to the KDE Applications. That did not restrain me from building new KDE 4.14 packages on Slackware-current. I was out of the country this week (my son is glad about the freedom that gives him around the house …) so the release of my new packages was somewhat delayed, but now that I returned I am going to fulfill my promise and create KDE 4.13 packages for Slackware 14.1 somewhere during the next week.

Akonadi is the only dependency that was upgraded after my KDE 4.13 packages. The KDE 4.14 package-set uses two sources from previous major releases because no new tarball was made available for KDE 4.14. Those are: kactivities-4.13.3 and kde-workspace-4.11.11.

How to upgrade to KDE 4.14.0 ?

You will find all the installation/upgrade instructions that you need in the accompanying README file. That README also contains basic information for KDE recompilation using the provided SlackBuild script.

You are strongly advised to read and follow these installation/upgrade instructions!

Where to find packages for KDE 4.14.0 ?

Download locations are listed below (you will find the sources in ./source/4.14.0/ and packages in /current/4.14.0/ subdirectories). Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric

On LKML: an open letter to the Linux World

I wish I were better with words. There’s thoughts that strike a note in your heart and mind,  but I would not be able to express these thoughts on paper so that they deliver the needed punch. That was my first thought when I read this open letter on the Linux Kernel Mailing List (LKML): https://lkml.org/lkml/2014/8/12/459 . The text is written by a longtime Debian user who feels deeply betrayed by its board of leadership. The emotions he penned down are exactly mine. Thank you, Christopher Barry. This was of course not the first eloquently written rant, but I hope it sparks a discussion in Kernel Land about what is happening in User Land, and whether they can afford to keep looking the other way (with the public exception of Linus and some others).

One word. One demon. systemd.

What relation does Christopher’s rant have to Slackware? After all, it’s Debian that got the flak, and in the comments section people indicate they intend to switch to Gentoo… forgetting that Slackware is a good systemd-free alternative (but hey! this automatic dependency resolution thingie that makes life so comfortable in Gentoo is not part of Slackware either).

Last week I asked the SDDM developers to reconsider their decision no longer to support ConsoleKit because Slackware does not have systemd or logind and thus we need to keep using ConsoleKit. The answer could be expected: “answer is no because ConsoleKit is deprecated and is not maintained anymore” and therefore I had to patch it in myself.

Of course, the ConsoleKit successor systemd-logind, written by the same team that gave us all the *Kit crap, depends on PAM which we also do not have in Slackware. One of the fellow core developers in Slackware, who is intimately familiar with the KDE developers community, has heard from multiple sources that KDE is moving towards a hard dependency on systemd (probably because they are going to need the functionality of systemd-logind). We all know what that means, folks! It will be the day that I must stop delivering you new KDE package releases for Slackware. That’ll be the day.

Eric

Updates for Chromium and Flash

Adobe did their monthly security dance and as a result, Google also updated their Chrome browser with the new PepperFlash Plugin. That Chrome release meant that I could compile a new Chromium from the updated sources.

Chromium and Pepper Flash:

chromium_icon The update to my Chromium package was not just triggered by the update (in Chrome) of the Pepper Flash plugin. Chromium 36.0.1985.143 comes with a couple of critical bug fixes:

  • [$2000][390174] High CVE-2014-3165: Use-after-free in web sockets. Credit to Collin Payne.
  • [398925] High CVE-2014-3166: Information disclosure in SPDY. Credit to Antoine Delignat-Lavaud.
  • [400950] CVE-2014-3167: Various fixes from internal audits, fuzzing and other initiatives.

Note that I also updated the package for chromium-pepperflash-plugin to version 14.0.0.177- it contains the newest library, taken from the official Google Chrome binaries and is a recommended companion for the new Chromium package.

Linux Flash:

adobe_flash_8s600x600_2 The Flash updates are released for all platforms, one of them is the “legacy” Linux NPAPI plugin for Mozilla-compatible browsers. See Adobe’s monthly security bulletin for all the version numbers and vulnerabilities. The Linux flashplayer-plugin went up to 11.2.202.400.

First preview for Slackware of Plasma 5

qt-kde-620x350Today is my son’s 16th birthday, and I do have a gift for all of you, not just for him. I present to you a first preview for Slackware, of the KDE Frameworks 5.1.0 libraries, combined with Plasma 5.0.1, the next-generation desktop workspace from KDE.

I wrote about this in my previous post, but now you can experience it first-hand: Plasma 5.0 improves support for high-DPI displays and comes with a “converged shell”, i.e. one Plasma codebase for different target devices like desktop computers, laptops, tablet, phones etc. Plasma 5 uses a new fully hardware-accelerated OpenGL(ES) graphics stack. Plasma 5 is built using Qt 5 and Frameworks 5.

And with the Breeze themed artwork and its own Oxygen font, this desktop looks clean and modern.

If you want to start an application quickly, use the new KRunner (usually hidden behind Alt-F2) which will now be activated directly when you start typing when your desktop has the focus.

 What to expect from these Slackware packages

I think it worked out very well that I waited with my packages until after the first bugfix release of both the Frameworks libraries and the Plasma programs. The latest sources provide a much stabler desktop with more functionality. Still, we are only at the beginning of KDE 5 (or whatever the name for the software compilation will end up being). KDE 4 will be here for a while and developers are busy porting their applications away from Qt4 and kdelibs, to the new Frameworks libraries based on Qt5 and QML. Give it a year to mature and then we will be able to leave KDE 4 behind, is my guess.

These new packages are only going to be useful if installed on top of Slackware -current and my KDE 4.13 packages (plus dependencies). KDE 5 is still very much  a work in progress and needs the KDE4 applications and artwork to provide you with a fully functional desktop.

Testing Repository URL

I created a repository URL that you can use for slackpkg+ or slapt-get or whatever package manager you use.

The URL http://taper.alienbase.nl/mirrors/alien-kde/current/testing/x86_64/ (for 64-bit) and http://taper.alienbase.nl/mirrors/alien-kde/current/testing/x86/ (for 32-bit) will remain permanent, even when the versions of the software gets updated. Currently “testing” points to “5.0.1″ in the repository because that is the current version of Plasma 5.

Enabling SDDM in runlevel 4 instead of KDM

Runlevel 4

If you want to see the new graphical session (login) manager SDDM in action, add the following lines to the Slackware file “/etc/rc.d/rc.4” right after the line: echo “Starting up X11 session manager…”

# — 8< ————————————–
if [ -x /usr/bin/sddm ]; then
exec /usr/bin/sddm
fi
# — 8< ————————————–

… and then switch to runlevel 4 by typing:

# init 4

Select “KDE Plasma 5” from the SDDM session dropdown. Alternatively, if you prefer good old runlevel 3, you can type:

$ xwmconfig

… and select “xinitrc.plasma” as your default window manager for X11. Then run:

$ startx

To enter your desktop session.

Installing or upgrading Frameworks 5 and Plasma 5

As always, the accompanying README file contains full installation & upgrade instructions. Note that the packages are available in three subdirectories below “kde”, instead of directly in “kde”. This makes it easier for me to do partial updates of packages. The subdirectories are “frameworks” “plasma” and “plasma-extra”.

Note that the new Plasma5 packages do not upgrade any package from my KDE 4.13 set, although they will upgrade several Slackware original packages. Be careful when upgrading Slackware packages afterwards. Slackpkg+ will help you, if you add the above repository URL to the slackpkgplus.conf file and give these packages higher priority than the Slackware originals.

If you decide to remove the Plasma 5 packages but not KDE 4.13 (or whatever latest version of KDE I have in my ktown repository), be sure to re-install two packages at least: akonadi from my ktown repository and harfbuzz from the Slackware-current repository.

Separated configuration files

I have taken great care to ensure that the configurations for the new KDE5 are not overwriting your old configuration files for KDE4. New configurations will be written to ~/.local5 , ~/.cache5 , ~/.config5 and ~/.kde5 . That way, you should be able to go back to your stable KDE4 desktop without ill effects after having played with KDE5.

One “issue” you will notice, is that some non-KDE applications will forget their configuration and will start as if you are using them for the first time. Chrome/Chromium is such an example. If you want to use the old configuration in Plasma 5 as well, simply create a symlink, This is how I did it for my Chromium after I found out (first remove the new chromium directory that was created by starting Chromium in Plasma 5):

$ rm -r ~/.config5/chromium
$  ln -s ../.config/chromium ~/.config5/

Where to get the new packages for Plasma 5

Download locations are listed below (you will find the sources in ./source/5.0.1/ and packages in /current/5.0.1/ subdirectories). Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Known issues

The “known issues” section ends this article, and I will keep it updated with the feedback I receive in the comments section below, direct email, LinuxQUestions.org, Google+ etc. Be sure to visit here regularly! For the first batch, I simply used the information that Willy had already gathered on his own blog:

  •  When you switch back to KDE 4, in some cases, all the icons in the Applications tab in the KDE  Menu will change to a blue folder icon.
    • Solution: reinstall KDE 4.13.3 packages, log out and login again. That will fix it.
  • Adding a new entry to the KDE Menu using the Menu Editor sometimes does not seem to work.
    • Solution: Logout/login and the changes you made will appear. This happened to me and Willy -but only the first time we tried it. After that first time, all seems to work normally.
  • HPlip shows an error message about not finding a system tray area. The reason is because the Plasma 5 workspace does not implement the X11 “Xembed” protocol. The system tray area works differently now. Not just HPlip, but all other applications that are not part of  Plasma  5, will have this issue, but only HPlip shows an error. You will not see any icons for Dropbox, SCIM etc… as they don’t have a place to dock.
    • Solution: There is a short-term solution which is not elegant, but it gives you back your old systray ocins. Use third-party Xembed system tray implementations like stalonetray or wmsystemtray . I have stalonetray in my own repository, and both are also available at SBo.
  • There are now two SystemSettings programs. One is part of Plasma 5 and the other is the one from KDE 4. The Plasma 5 version is found in the “Favorites” tab of the K-Menu, while the one from KDE 4 (which is more complete) is available in the menu as “Applications > Settings > System Settings“. The Plasma 5 version is not yet feature-complete.
  • Certain conditions may crash your Plasma Shell. E.g. typing in the  Search field in the K-Menu “Favorites” tab and then removing that text will crash plasmashell (your desktop goes black), fortunately it will restart automatically.
  • KRunner (Alt-F2) will not save your command history.
  • Public holidays are not yet shown in the System Tray clock. See this URL for more information.
  • Resource usage of this new desktop is currently rather high due to a design limitations in KWin, The cause is known and this will be fixed in future releases.
  • In some cases, if your desktop becomes unresponsive, you might want to take a look at “top”. You may find that kded5 runs at 100%, eating all CPU resources available.
    • Solution: Killing the kded5 process or logout/login will fix this.
  • The updated harfbuzz package breaks the library’s ABI. As a result, LibreOffice 4.3.0 will no longer work (error looks like “symbol lookup error: libvcllo.so: undefined symbol: hb_icu_script_to_script“).
    • Solution: Downgrading to the original Slackware harfbuzz package solves it, which is a pity because I thought I had taken care of the ABI breakage by applying a patch which re-adds that missing symbol.
  • The hardware keys for altering volume and mute do not work on a global level. They seem to work for some applications – VLC is one of them. Sound is working fine though.

Have fun! Eric