Alien Pastures

My thoughts on Slackware, life and everything

Tag: plasma (Page 2 of 5)

KTOWN: live ISO with Plasma6 Alpha. Also, chromium now supports HEVC/AC3 playback

November 10, 2023 / / 20 Comments

I have uploaded a 5 GB ISO file containing a new KTOWN variant of Slackware Live. This is the KDE Plasma6 Alpha release. Play around with it and perhaps you will be able to contribute to an improved Beta by finding and reporting the bugs you encounter.

Get the ISO from my NL or my US server (US ISO still uploading at the moment). There’s also an MD5 checksum and a GPG signature file in those same locations if you want to validate the download.

A lot of packages did not compile yet for various reasons. I am not too concerned about that, next update hopefully will be more complete. A lot of work still needs to be done however (by the KDE developers) to port the remainder of KDE Gear (formerly called Applications or Software Collection) to Qt6.
Not ported to Qt6 as of yet are: artikulate cantor cervisia juk kamoso kde-dev-utils kdenlive kdesdk-thumbnailers kdev-php kdev-python kdevelop kget kgpg kig kio-gdrive kipi-plugins kiten kmix konversation kqtquickcharts krfb ktorrent ktouch kwave libkipi lokalize marble okular parley poxml rocs umbrello.

Still, I was impressed with the fully working and stable Plasma6 Wayland session when I tested an unreleased KTOWN Live ISO a week ago. Of course, as things go, I seem to have broken the Wayland session in this public release of the KTOWN Live.
The version of SDDM graphical session manager should also be Wayland-capable but I will test that in a future ISO.

Let me know in the comments section below what you think of this Alpha release.

News about my chromium package (also its ungoogled sibling).

I was finally able to get the HEVC video and AC3 audio codec support working. There’s a patch set on github, maintained by StaZhu but I did not like the complexity and I am not really interested in GPU hardware-only support. The browser’s internal ffmpeg libraries playback HEVC just fine, taxing your CPU a bit more than in the case of a supported GPU.
Now, the Thorium Browser is also Chromium based and its developer Alex313031 used StaZhu’s patches and wrote some of his own to add not just HEVC video but also AC3 playback support.
Again, I did not like the complexity of his solution (documented on github) but could not get around using some of the patches provided by both. I simplified some of the others into a bunch of ‘sed’ commands. And that made it work for me.

The browser will now playback HEVC and AC3 media formats, as long as the container file is a MP4. I have not found how I can convince Chromium to also support MKV containers.
The chromium-119.0.6045.123 package is already available in my repository, and chromium-ungoogled is still compiling (the ungoogled patch kit only became available earlier today).

You can test the new HEVC playback capability here: https://test-videos.co.uk/ if you select any MP4/HEVC sample (none of those have sound) or Thorium browser test page: https://thorium.rocks/misc/h265-tester.html (those have AC3 audio).

Have fun!

KDE: February 2024 MegaRelease

October 25, 2023 / / 18 Comments

Just a heads-up to you people who wondered when Alien BOB would pick up on the KDE Plasma bleeding edge again.
Simply put: Patrick did a hell of a job pushing every new KDE Plasma update into the slackware-current package tree (even before the 15.0 release) in no time. There was nothing for me to do (or to improve on) since Plasma5 got added to the distro.

My intention is to change that, soon.

Exactly one month ago, KDE published their planning for Plasma6, the successor to Plasma5, so numbered after the version of the Qt framework which underpins it. As seen on the ‘February 2024 MegaRelease‘ page, the first Alpha release of the Qt6-based Frameworks, Plasma and Gear (the three main components of KDE Plasma) is expected to see the light on November 8th, 2023. The final stable release of KDE Plasma6 will be on February 28th, 2024.

I don’t expect that Slackware itself will absorb this new software immediately upon release. Perhaps we will have a Slackware 15.1 next February, maybe not – but a new KDE desktop is a major and potentially disruptive upgrade. Still, it needs solid testing on Slackware -current somehow. Therefore I will have that stable KDE Plasma6 in my ktown repository when it is released.

I am currently working on updating the kde.SlackBuild infrastructure which I took from Slackware-current, to make it work with the new Plasma6 sources. It is not a trivial task; there are new non-KDE dependencies, new KDE programs and changed interdependencies, patches to remove and patches to add.
So far, I have finalized the scripts for all of the new dependencies, as well as the Frameworks and Plasma. Currently working on KDEPIM, and then the Gear collection (formerly called Applications) awaits. The results up to now took me a full week, and the Gear will probably have the same level of unpleasant surprises (hey, it won’t compile! what did they sneak in now? <initiates another search through KDE Invent>…).

Meaning, I won’t make promises on the timeline for a first Slackware-based test release. I aim to make it coïncide with KDE’s own Alpha release, but I may not be able to finish on time. To be clear about my roadmap: anything that I make available before the stable release of Feb 28, will take the shape of a Slackware Live ISO image (the ktown variant, we haven’t seen that one for two years almost!) for you to test and play with.
There will be no new packages in the ktown repository until the time when KDE Plasma6 stable gets released. I am supportive of people who want to compile this set themselves, so I will make the sources available in ktown as soon as I release the first live ISO and will keep updating those sources.

Note that I will not make Plasma6 co-installable with Plasma5. It’s going to be one or the other. Any official Slackware package that I have to recompile to add Qt6 support, will not lose its Qt5 support. Meaning, my ktown versions of gpgme, kdsoap, phonon, polkit-qt-1, poppler, qca, qcoro or qtkeychain will be 100% compatible with standard Slackware.

Hope to have more news in a week or two!

Sunday update (Oct 29) – a screenshot of the “about” screen after I compiled the new dependencies, Frameworks, Kdepim, Plasma, Plasma-extra and Gear (excluding some twenty packages which are not yet compatible with Qt6):

Eric

Patrick, next Slackware and moving forward with KDE Plasma5

July 26, 2018 / / 25 Comments

I assume that many of you will have been reading the recent Linux Questions thread “Donating to Slackware” and in particular Patrick Volkerding’s reply where he explains that the Slackware Store (an entity independent of Slackware with which he has a business arrangement involving a percentage of sales profit and medical insurance) has not been paying him any money for the last two years and that most likely all the PayPal donations through the Store have gone into the pockets of the Store owners. Read that thread if you have not done so yet.
Basically Pat is broke. That thread lists a PayPal address which Pat eventually shared and where donations can be sent directly to him, so that he can fix his roof, his airco, his crashing server and his wife’s car. That would be a start.

That LQ thread is also perused to discuss possible ways forward for Pat (setting up a Patreon account, or a business PayPal account, etc) so that he can support his family and continue working on Slackware. To me it looks like the Store will be a thing of the past unless they change their attitude. Switching from a business model where revenue is generated from optical media sales, to a model where supporters set up a recurring payment in exchange for the prolonged existence of their favorite distro, and possibly get Pat to write up some hands-on stories as a reward, may ultimately benefit Pat, and Slackware, more than the way things are handled at the moment. If you are doubting the financial impact of a recurring payment through Patreon or PayPal, look at it this way: if you donate one euro per month, you will probably not even notice that the money is shifted out. But with 2000 people donating one euro per month, Pat would have a basic income (pre-tax) already. Not a lot, but it’s a start. The 2000 people is a rough estimate of the people who ordered a DVD or CD through the store: the owners told Pat that the earnings of the 14.2 release were 100K (and Pat got 15K out of that, go figure!). Divide that through ~50 euro per DVD, results in 2000 people. Then there’s all these people who donated money through the Store or bought shirts, caps and stickers. I think the amounts of money even a small community (like us Slackware users) can contribute should enable Pat to shed his financial worries. The fact that the Slackware Store basically has been ripping off the hand that feeds them is enraging and inexcusable.
This is all about a community standing up to provide support for what (or who) bonds us together.

Very important to take from Pat’s reply is that he’s “never really been in this for the money” but without income, Slackware’s development is ultimately affected too. I hesitated writing this article, even after Patrick’s LQ post, because it is Patrick’s life and I won’t decide for him how to live it. But I am passionate about Slackware, and care a great deal for Pat, Andrea and Briah, and wish them nothing but the best.

So, in that LQ thread and in private talks, I guess that there will be a lot of discussions as well about the shape and form of a future Slackware. Should it shrink to a “core distro” on which others can build their repositories, for instance offering Plasma5, MATE, Cinnamon desktop environments? How to integrate these external repositories so that a new install could effortlessly be expanded with extra functionality? Should Plasma5 be included? Should PAM be included? And so forth. Lots of exciting developments in stock!

As for KDE Plasma5, I talked with Pat about the way forward and what his plans are with regard to Slackware and Plasma5. Pat indicated that he would at this moment be in favor of going with the latest and greatest instead of adopting LTS (Long Term Support) releases of KDE, because of the reports from several Slackware Plasma5 users that several usability bugs have been solved in the latest releases (part of those improvements can be attributed to the newer Qt5). If Pat decides not to adopt Plasma5 into Slackware, then as long as he provides a solid base in Slackware 15.0 I can keep providing Plasma5 as an add-on through my ‘ktown’ repository. That “solid base” would at least have to be Qt5, its supporting libraries, and recompiled/upgraded phonon, poppler, harfbuzz etc packages to add Qt5 support so that I can cut my “deps” section substantially and no longer have to provide alternate versions of packages that are also part of Slackware but lack required functionality.

And that is why my next update of ‘ktown‘ will see the removal of the LTS software versions in the ‘latest‘ sub-repository and at the same time, the bleeding edge ‘testing‘ sub-repository will be promoted to the ‘latest‘. The ‘testing’ and ‘latest’ will then contain the same packages, so that everyone will upgrade to the same July ’18 packages.
I still need to start collecting the new KDE source archives, sync my virtual machines to latest -current and start compiling. Don’t expect packages before the weekend…

Eric

Poll: who needs 32bit packages for latest Plasma 5?

January 25, 2017 / / 81 Comments

During the past week I have been spending time on getting the latest KDE Frameworks, Plasma and Applications built. The new Applications 16.12 was quite a bit of work due to the splitting of tarballs in many smaller ones. Also, the Slackware 14.2 and -current versions have now diverged sufficiently that the packages I compile on 14.2 are no longer guaranteed to work on -current, so that introduces additional work.

This effort took much longer than I am comfortable with. I do not have as much time available as I used to have due to “real life” – meaning my new job is quite a bit more demanding than my previous one.
This made it clear to me that I have to start making decisions about my Slackware activities, with more detail than what I said in the past along the lines of “updates may come less frequent”. It is obvious that I can not keep releasing a new set of ‘ktown‘ packages every month, for both 32bit and 64bit platforms, and for both Slackware 14.2 and -current. I have a few options:

  1. stop releasing 32bit packages for Plasma 5 (ktown repository)
  2. stop releasing Plasma 5 for Slackware 14.2 and start focusing on -current exclusively

I tend to lean into option (1) and therefore wrote this blog post. Who is using my Plasma5 (ktown) packages on a 32bit Slackware OS?

If there are users running a 32bit Slackware-current OS then this could mean a stop to new Plasma5 releases for Slackware 14.2. Updates to the graphical desktop does not have priority at this time in the development cycle of Slackware-current which means I will have to keep maintaining my ‘ktown’ repository for a while to come.

Bottomline: I will have to make one of the two above choices, and I will listen to you – the users of my packages – to help me make that decision.

New Slackware-current Live ISOs with latest Plasma

December 11, 2016 / / 45 Comments

blueSW-64pxI am ready with a new batch of packages for Plasma 5 and to showcase that in a Slackware Live Edition, I stamped a new version on ‘liveslak‘.
Version 1.1.5 is ready, again containing only minor tweaks compared to the previous release. I made a set of ISO images for several variants of the 64bit and 32bit versions of Slackware Live Edition based on liveslak 1.1.5 and using Slackware-current dated “Thu Dec  1 08:49:20 UTC 2016“. These ISO images have been uploaded and are available on the primary server ‘bear‘. You will find ISO images for a full Slackware, Plasma5, MATE and Cinnamon (yes, I did one this time!) variants and the 700MB small XFCE variant.

If you already use a Slackware Live USB stick that you do not want to re-format, you should use the “-r” parameter to the “iso2usb.sh” script. The “-r” or refresh parameter allows you to refresh the liveslak files on your USB stick without touching your custom content.

liveslak-1.1.5

New in the ISOs

The new ISOs are based on the latest slackware-current with Linux kernel 4.4.32.

The SLACKWARE variant contains exactly that: the latest slackware-current and nothing else.

The XFCE variant contains a stripped down Slackware with a minimalized package set but still quite functional. The small size is also accomplished by excluding all documentation and man pages, and the localizations for the languages that are not supported in the boot menu. This ISO is small enough that you can burn it to a ’80 minutes’ CDROM (700 MB).

The MATE variant (a Slackware OS with KDE 4 replaced by Mate) contains packages from the repository at http://slackware.uk/msb/current/ which is still Mate 1.16 (GTK3 version).

The Cinnamon variant (KDE 4 replaced by Cinnamon) contains the latest Cinnamon 3.2 desktop environment created from the repository at http://slackware.uk/csb/14.2/ .

The PLASMA5 variant (Slackware with KDE 4 replaced by Plasma 5) comes with the latest Plasma 5 release “KDE-5_16.12” as found in my ktown repository. This ISO also contains the LXQT and Lumina Desktop Environments. Both are light-weight DE’s based on Qt5 so they look nice & shiny.
One word of caution when using the Lumina DE:

  • The network applet is not enabled by default, and you may have to enable the network manually. I used “nmtui” in a terminal window but you can try enabling the networkmanager-applet instead. I did not find out how, yet.

The changes between liveslak scripts 1.1.4 and 1.1.5

The ‘1.1.5’ tag was applied to accompany the release of the new ISOs so the progress is not stellar – liveslak is quite stable:

  • (e)liloconfig are patched when installed, so they work properly when executed from a Live environment through the harddisk installer ‘setup2hd’. I had some issues in the past when installing from PLASMA5 Live to an UEFI based computer and hope that these patches are the cure.
  • various updates in package content for the XFCE, PLASMA5, MATE and CINNAMON ISOs.
  • the ‘bonus’ subdirectory in the ISO the download area contains multilib related modules which you can copy to either the ‘addons’ or the ‘optional’ subdirectory of liveslak. The two will add multilib capability to your 64bit Live environment. Note that the PLASMA5 ISO already contains these two modules in ‘optional’:
    • 0050-multilib-current-x86_64.sxz
    • 0060-wine-1.9.23-current-x86_64.sxz

Multilib considerations

I added a live module to enable multilib support out of the box in the PLASMA5 variant of Slackware Live. Inside the ISO that module-file is called “/liveslak/system/0020-slackware_multilib-current-x86_64.sxz”.
I host a copy of that module online as “0050-multilib-current-x86_64.sxz” so that you can download it and add it to the ‘addons‘ or ‘optional‘ subdirectory of your non-plasma5 liveslak.
Multilib is something you’d need for Wine, so I also added a live module for Wine (including the 32bit OpenAL libraries) as a separate module in the ‘optional‘ subdirectory of the PLASMA5 ISO and made copy of it available in the aforementioned ‘bonus’ directory online.
This is how I created that live module for wine: by installing the 32bit OpenAL libraries on top of my 64bit wine package for Slackware (which contains both 32bit and 64bit wine):

# SCRATCHDIR=$(mktemp -t -d makesxz.XXXXXX)
# installpkg --root $SCRATCHDIR wine-1.9.23-x86_64-1alien.txz
# installpkg --root $SCRATCHDIR OpenAL-compat32-1.17.1-x86_64-1aliencompat32.txz 
# ./makemod $SCRATCHDIR ./optional/0060-wine-1.9.23-current-x86_64.sxz 
# rm -r $SCRATCHDIR

Remember, the modules in the ‘optional‘ subdirectory of liveslak can be loaded into the live OS on boot when you use the “load=” boot parameter in syslinux or grub. Loading the optional wine module for instance, needs this as additional boot parameter: “load=wine” and if you would be using a non-plasma5 based Live OS and have added the multilib module in the ‘optional‘ subdirectory also, then the boot parameter needs to load both multilib and wine: “load=multilib,wine”.
Of course, if you place both modules in the ‘addons‘ subdirectory instead, they will always be loaded on boot unless you want to prohibit that using the “noload=multilib,wine” boot parameter in syslinux or grub.

Download the ISO images

The ISO variants of Slackware Live Edition are: SLACKWARE, XFCE, PLASMA5, MATE and CINNAMON. These ISO images (with MD5 checksum and GPG signature) have been uploaded to the master server (bear) and should be available on the mirror servers within the next 24 hours.

Download liveslak sources

The liveslak project can be found in my git repository: http://bear.alienbase.nl/cgit/liveslak/ . That’s all you need to create a Slackware Live ISO from scratch. Documentation for end users and for Live OS developers is available in the Slack Docs Wiki.

Have fun! Eric

« Older posts Newer posts »

© 2026 Alien Pastures

Theme by Anders Noren — Up ↑