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

About this blog

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

Search

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 375 other subscribers

My Favourites

Slackware

Calendar

June 2018
M T W T F S S
« May    
 123
45678910
11121314151617
18192021222324
252627282930  

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current

RSS SBo

Meta

May update for Plasma5

On with the show.
After recompiling LibreOffice and VLC to compensate for the recent poppler update in Slackware-current, my next target was – naturally – my Plasma5 package set. The KDE-5_18.05 release of ‘ktown‘ for Slackware-current offers the latest KDE Frameworks (5.46.0), Plasma (5.12.5) and Applications (18.04.1) on top of Qt5 5.9.5 (I decided to wait with an update to Qt5 5.11.0).
You can and should check out the README file for more details and for installation/upgrade instructions.

News about this month’s refresh

  • In the deps section I updated my poppler package so that it again matches the version in Slackware-current (my poppler package has support for Qt5 in addition to the Qt4 support in the Slackware original). I also rebuilt cryfs after that was reported broken.
  • Frameworks, Plasma and Applications updates are focusing on improved stability and nothing exciting happened there.
  • In applications-extra I have rebuilt calligra (was affected by the new poppler) and updated the alkimia, falkon, kdevelop, kdev-php, kdev-python, krita and krusader packages. I also added one new package: krename.

I think and hope that the shape of Slackware-current is getting to a point where Patrick feels comfortable with introducing the new Plasma5 into the core. To be honest, the waiting gets tedious. The first preview of Plasma5 for Slackware was introduced in my blog almost four years ago. I’d wager that it has matured quite sufficiently in the meantime.
If you want to read more about the history of Plasma5 development for Slackware, with lots more detail, check out my older blog posts. If you think a git log is easier to read, check out my ktown git repository instead 🙂

If you are using slackpkg with the slackpkg+ extension, don’t forget to run “slackpkg install ktown” to get any new packages installed, because “slackpkg install-new” will not catch new packages in 3rd-party repositories like ‘ktown’.

I am preparing a new PLASMA5 variant of the Slackware Live ISO image, so you can check out the new desktop in the safety of a non-invasive live environment. Hopefully before the weekend… depending on the workload tomorrow.

Enjoy!

Comments

Comment from Darth Vader
Posted: May 24, 2018 at 22:41

Congratulations for the release! 😀

Comment from Antonio
Posted: May 24, 2018 at 23:48

TKS!

Comment from Richard Herbert
Posted: May 25, 2018 at 01:49

Like butter, a usual, Eric. Thanks for all you do. Let’s hope the waiting doesn’t get *too* tedious.

Comment from Darth Vader
Posted: May 25, 2018 at 03:09

Speaking about Plasma5 readiness, I am just curious if it learned meanwhile to handle its own configuration files, or still we should hack them manually to get the bold fonts displayed properly?

Comment from chrisretus
Posted: May 25, 2018 at 09:54

Thanks, working great. Is it just me? Startx from runlevel 3 seems to be a a whole lit faster. 🙂

Comment from alienbob
Posted: May 25, 2018 at 10:08

Well Richard – at some point the level of tediousness will get to where I stop with my Plasma5 package releases. I mean, 4 years.
If Plasma5 is too complex or too high-maintenance for inclusion into Slackware then it’s going to stop for me as well and I’ll switch to XFCE.

All this ‘ktown’ work and recompiling packages that break in -current eats up a lot of my free time which I can no longer justify toward my wife. Many hours, every night. There’s no financial gain in return – the Adsense ads on this blog used to make 10 dollars per month but that has dwindled to only cents per month (I use adblockers myself, so understandable) and donations have all but stopped. Once the money to pay for the rent of the ‘bear’ server has dried up (within a couple of months) I’d have to ask for money and that is something I hate to do – I’d rather pay out of my own pocket.
There’s one kind person who sends me a monthly amount but even that does not cover the cost of the server rent.
End rant. End of the week blues I guess…

Comment from chrisretusn
Posted: May 25, 2018 at 11:08

My last post I spell my name wrong. Hehe.

Noticed a package removed not mention in the README or ChangeLog.txt.

qqc2-desktop-style-5.45.0-x86_64-1alien

Took it for granted it should be removed.

Comment from alienbob
Posted: May 25, 2018 at 11:30

Hi Chris

Well thanks for that report. The “qqc2-desktop-style” should have been built but I notice only now that the build logfile told me it was skipped.
It looks like the reason for skipping it is that there are actually 3 source tarballs: 5.46.0, 5.46.1 and 5.46.2. My kde.SlackBuild could not handle the fact that there’s more than one source tarball and boo-booed…
I will compile this package ASAP and add it to the repository… again thanks for spotting and reporting!

Comment from Eduardo
Posted: May 25, 2018 at 14:14

Thank you Eric! I hope Plasma gets included in -current ASAP.
Thanks also for the inclusion of krename!

Comment from alienbob
Posted: May 25, 2018 at 14:23

chrisretusn , I have uploaded the missing ‘qqc2-desktop-style’ package.

Comment from chrisretusn
Posted: May 27, 2018 at 10:23

Thanks Eric. Will rsync after posting and update my install.

Comment from Helios
Posted: May 25, 2018 at 16:26

Thank you very much.
It seems that kile needs also to be recompiled

Pingback from Links 25/5/2018: OpenSUSE 15 Leap Released, PostgreSQL 11 Beta | Techrights
Posted: May 25, 2018 at 22:08

[…] [Slackware] May update for Plasma5 […]

Comment from Darth Vader
Posted: May 26, 2018 at 13:21

And even in this incarnation, the Plasma5 does known to write its own configuration files in a form which itself can read properly…

Same bold fonts issue in config files, even in this build. 🙁

Comment from Darth Vader
Posted: May 26, 2018 at 13:27

And even in this incarnation, the Plasma5 does NOT known to write its own configuration files in a form which itself can read properly…

Sorry for typo, and for the second message, but there is no possibility to edit a message.

Comment from alienbob
Posted: May 26, 2018 at 18:03

Darth, what is the number of the bug report you created to allow the developers to address and fix your issue?

Comment from Candace
Posted: May 26, 2018 at 23:19

Er is elke dag weer te weinig tijd, er is nog zo veel te doen!

I’ve been using the ktown packages for over two years now, and they’ve been nothing but solid for me. As far as I can tell, they were ready for inclusion in 14.2! 🙂

Thanks a lot for all the work you’ve put into Slackware, not only ktown, but all the packages (which I regard as “unofficially official”, a reliable extension of the base system), Slack Live (which I keep on my keyring alongside my house and car keys), and this blog (which has virtually become my only source of news concerning Slack, and has been quite informative). It all makes Slack so much more pleasant to use, and it’s very much appreciated.

Met vriendelijke groetjes,
—Candace

Comment from cwizardone
Posted: May 27, 2018 at 22:34

I’m starting to think I must be a masochist. 🙂
About once a month I’ve downloaded and install kde5 and none, of the few problems I’ve seen, have been corrected.
kde5 doesn’t play well with others. It totally screws up my
Xfce settings. I found a file that said to go into the kde5 settings under “colors” and remove the check mark next to the box that says something along the line of “apply colors to non qt applications.” Didn’t do bit of good.
If you use virtual desktops you can no longer have different wallpaper for each desktop, but that does work for “activities.” Didn’t see any changes in the few kde applications I use that are noteworthy. Spent about 5 hours this time, 8 hours the last time, trying to tweak it. Just don’t care for it, but, then, it took about 6 years before I thought kde-4 was ready for daily, serious work.
Now I’m debating whether to delete kde5 and and re-install kde4, as I use Xfce most of the time, or leave kde5 installed and live with the mess it made of my Xfce setup. Which brings up the thought, would you know what I can do “undo” what kde5 has done to Xfce, and then I can just use the kde5 apps?
As always, thanks for all you hard work.

Comment from cwizardone
Posted: May 27, 2018 at 22:38

I forgot to mention I went to the kitchen for a few minutes and just as I was sitting back into my chair a light blue
screen appeared and locked the screen. Punched in the password and all was well, but I couldn’t find anywhere to turn that off and, yes, I had already turned off the “power saving” switch in the kde5 settngs.

Comment from alienbob
Posted: May 28, 2018 at 00:17

Perhaps you should document somehow how Plasma5 messes up your XFCE. Without screenshots or other actual proof I can not imagine what is wrong on your XFCE desktop.
I think someone already told you that the GTK+ theme engine of Plasma5 writes a configuration file that XFCE might be using.

Perhaps if you just remove the kde-gtk-config package, that will be sufficient.

Comment from cwizardone
Posted: May 28, 2018 at 00:22

“I think someone already told you that the GTK+ theme engine of Plasma5 writes a configuration file that XFCE might be using…”

Yes, that is the same file that also give one instructions to removing the checked box next to “apply colors to non qt applications.”

Comment from cwizardone
Posted: May 28, 2018 at 02:30

I took the “easy” way out and did a fresh install of the most recent -current iso.
Problems solved… so to speak.
🙂

Comment from Drakeo
Posted: May 28, 2018 at 03:09

Oh it built. What about the user root.
Pat learned that years ago. unstable and the Icons still do not refresh. good luck

Comment from drakeo
Posted: May 28, 2018 at 03:22

so root is unable to copy from one partition to another. root is a user. You have an Idea why your system does not see UUID per 0
I haven’t looked at the code to be honest. but to be able to to back up as root to another partition is a set back.
sure you can do it in command line I can. but we are working on gui. good luck. edit the code

Comment from Marcus_777
Posted: May 28, 2018 at 16:13

Once finished with KDE, what do you say about Enlightenment? SlackE18 seems dead. I lack reliably packages for Slackware.

Comment from alienbob
Posted: May 28, 2018 at 19:55

Marcus_777 – I installed Enlightenment once, found it ugly as hell and clumsy, and never touched it again. That will not change.

Comment from alienbob
Posted: May 28, 2018 at 20:00

Drakeo sorry – I can’t follow you. Sorry. Explain why my packages are unstable or stop spilling your nefgative vibe on this blog. It is entirely unhelpful. I can not fix anything if you do not mention what needs fixing.
And if you complain about Plasma5 then this is not the place to post. Create KDE bug reports.

Comment from Marcus_777
Posted: May 28, 2018 at 20:56

Surprisingly. For me it is pretties desktop environment. Light, fast, ergonimic and rock stabe. I respect your decision and don’t ask again 🙂

Comment from ArTourter
Posted: May 29, 2018 at 11:40

Hi Eric,

not directly related to ktown, but since it is an optional external dependency, openconnect needs to be recompiled due to the .so bump from libidn.

Thanks for you work.

Comment from chrisretusn
Posted: May 29, 2018 at 17:01

I use Kate a lot. Been busy last few days written scripts. Has anyone experienced Kate freezing for several seconds? Happens perhaps once a day. It always comes back. I can see one of my CPU’s cruising at 100% sometime when this happens. It just a bit annoying and was wondering if it’s just me.

Aside from that, Ktown is running rock solid.

Comment from alienbob
Posted: May 29, 2018 at 17:16

ArTourter – thanks, I will attend to a recompile of openconnect ASAP.

Comment from JtotheD
Posted: May 29, 2018 at 17:57

I look at your blog every day. To show my appreciation I gave you a few bucks via the donate button. Stay awesome.

Comment from alienbob
Posted: May 29, 2018 at 23:47

JtotheD – much appreciated!

I released something new today (useful for followers of -current) and hope to write about it soon. If you search, you may find out what it is before I write that post… no bonus points though 🙂

Comment from Helios
Posted: June 2, 2018 at 14:47

It seems that dvdauthor needs also to be recompiled (in slackware64-current):

/usr/bin/spumux: libMagickCore-6.Q16HDRI.so.5 => not found

Comment from alienbob
Posted: June 2, 2018 at 20:50

Helios yes indeed. I had not yet upgraded to the latest packages (also I never use dvdauthor myself) but now I see it. I’ll fix it with an updated package.

Comment from Richard Van Den Boom
Posted: June 2, 2018 at 21:54

Just for the record, but currently vlc fails to build here because the libxkbcommon-0.8.0-x86_64-1alien.txz still contains a .la file that seems to refer to some XCB .la file that no longer exist. Not sure if I’m doing something wrong or if it’s a real issue, but vlc builds with XCB support if I remove the above package.

Comment from alienbob
Posted: June 3, 2018 at 00:31

Strange because I just built it a day or so back and had no issue.
Perhaps if you had posted the errors…

Comment from LoneStar
Posted: June 4, 2018 at 11:24

ap/mariadb-10.3.7-x86_64-1.txz: Upgraded.
Shared library .so-version bump.
libmysqld.so.19 was renamed to libmariadbd.so.19.
Anything linking to libmysqld.so.19 will need to be recompiled.

I suppose this impacts something in Plasma? Akonadi?

Comment from alienbob
Posted: June 4, 2018 at 19:40

Akonadi is probably the only affected package. Pat rebuilt Amarok in -current but that’s not part of my ‘ktown’ repository.

Comment from Gérard Monpontet
Posted: June 6, 2018 at 09:43

I do not think that akonadi depends on mariadb 😉

Comment from alienbob
Posted: June 6, 2018 at 19:21

Gérard indeed I came to the same conclusion when I updated my VM with Plasma5 and the latest -current. There are no library dependencies which would mandate a recompilation.

Comment from Pete Christy
Posted: June 7, 2018 at 13:25

The latest -current updates seem to be causing a major increase in “idle” cpu usage with KDE5. Stopping cupsd solves the problem, though it is plasmashell that is affected worse. KDE4 isn’t affected. The whole saga is here:
https://www.linuxquestions.org/questions/slackware-14/cpu-usage-through-the-roof-after-latest-updates-4175631401/

Cheers,


Pete

Comment from alienbob
Posted: June 8, 2018 at 11:17

These are the bug reports for the CUPS issue, since it is not just Slackware that suffers:
https://bugs.kde.org/show_bug.cgi?id=395115
https://github.com/apple/cups/issues/5325

It seems to be a regression in cups-2.2.8. Reverting to 2.2.7 solves the high CPU load.

Comment from Pete Christy
Posted: June 8, 2018 at 14:53

Hi Eric, yes, agreed – it looks like a cups issue, but strange that it only rears its head in kde5! Its still there in the latest beta release of cups (2.3b5) – I tried that too! Luckily, thanks to your new git repository, I was able to retrieve the build package for 2.2.7, and all is now working well.

Cheers,


Pete

Comment from alienbob
Posted: June 8, 2018 at 21:29

Even though the bug is triggered by a change in CUPS, the solution is at least worked on in KDE’s print-manager software.
If they come up with a fix I’ll patch my package with it.

Comment from Pete Christy
Posted: June 9, 2018 at 11:22

gmgf has pointed out that archlinux have a patch for cups-2.2.8 that appears to fix the issue:

https://git.archlinux.org/svntogit/packages.git/tree/trunk/cups-2.2.8-5325.patch?h=packages/cups

I’ve tried it, and its all working fine, so far!


Pete

Comment from alienbob
Posted: June 9, 2018 at 19:15

Another patch than
that Arch patch has been offered to the CUPS developers through a push request: https://github.com/apple/cups/pull/5330

So perhaps you should try this patch: https://github.com/heftig/cups/commit/455c52a027ab3548953372a0b7bdb0008420e9ba.patch

Comment from Pete Christy
Posted: June 9, 2018 at 20:04

Yes, that seems to work fine too. As it has come from the cups developers, I guess that makes it the preferred option! 😉

Are you going to point this out to Pat, or should one of us do it? I know it only affects kde5 as far as we can tell, but if something is wrong, then it is wrong and needs correcting….


Pete

Comment from alienbob
Posted: June 10, 2018 at 14:46

The patch has already been applied to the cups package in -current so after you upgrade it, all should be well.

Comment from All
Posted: June 12, 2018 at 21:44

Kde-connect and Kuser all work?

Comment from alienbob
Posted: June 12, 2018 at 23:41

Yes.

Comment from alienbob
Posted: June 13, 2018 at 14:46

When attempting to build the new KDE Plasma 5.13 sources, I ran into the issue that a Plasma 5.13 requires a minimum version of Qt5 that is 5.10.0.
I.e. the qt5 package in my repository is too old.

I think I’ll have to make a decision here. Pat will likely not want to include a short-lived version of Qt5 in slackware-current.
Qt 5.9 is a LTS release with update support until 2020 while Qt 5.10 support will end later this year and Qt 5.11 will be supported to halfway 2019.
Therefore I estimate that Pat will add Qt 5.9 and Plasma 5.12 (which is also a LTS release) together with the newest versions of Frameworks and Applications that work with those.
Which means that I will stick with Qt 5.9 and Plasma 5.12 for a little while but I will upgrade Frameworks and Applications.
In parallel I will use my “testing” repository on ‘ktown’ to introduce Qt 5.11.0 (released 3 weeks ago) and Plasma 5.13.0 (to be released this week).
Wayland support will not be considered in that upcoming ‘testing’ update.

Comment from Gérard Monpontet
Posted: June 13, 2018 at 20:38

Eric, i use qt5-5.11.0, and i have installed the latest frameworks, plasma, and applications compiled with this qt5 version, it work correctly 😉

Comment from alienbob
Posted: June 13, 2018 at 21:10

Gérard I have no doubt that the latest KDE would fail against Qt 5.11. I will put Qt 5.11 and Plasma 5.13 in ‘testing’ because I can not compile Plasma 5.13 against QT 5.9 and I don’t want to force Pat’s hand.

To be honest, I had not expected that in June 2018 I would still be maintaining Plasma 5 here in this repository, outside of the Slackware core.

Comment from cwizardone
Posted: June 14, 2018 at 08:19

>To be honest, I had not expected that in June 2018 I >would .still be maintaining Plasma 5 here in this >repository, outside of the Slackware core.

Really??!! It brings nothing but convoluted complexity to Slackware.

Comment from Pete Christy
Posted: June 14, 2018 at 10:28

“Really??!! It brings nothing but convoluted complexity to Slackware.”

Unfortunately, many of the apps of which I make quite a lot of use are now only supported under Plasma5. Mostly multimedia stuff like kdenlive and kaffeine, but there are others too.

It would be really nice to see kde5 offered as an install option alongside kde4 and all the other window managers in Slackware. Then we could just install what we needed for our individual purposes.

Slackware was quite late adopting 64 bit, with Fred Emmot’s SLAMD64 offering a viable alternative until Slackware64 was deemed ready. Hopefully Pat and the Slackware team will finally offer kde5 as an option in the next release.

In the meantime, many thanks to Eric for his efforts here!


Pete

Comment from alienbob
Posted: June 14, 2018 at 13:09

cwizardone,

> Really??!! It brings nothing but convoluted complexity to Slackware

I’ll be blunt for once and hopefully this sets the record straight.
It’s not the software. It is your frankenstein computer which is the cause of all these issues you report on my blog about the use of my software packages.
And Plasma 5 is visually displeasing to your eyes, I respect that. But “convoluted” and “complex” ? You pull that out of your arse.

Comment from alienbob
Posted: June 14, 2018 at 13:34

Pete,

KDE4 has been un-maintained since even before the release of Slackware 14.2. Only the kdelibs sources received the occasional bug fix but that stopped at the end of 2017.
KDE4 is still a useful and stable desktop environment, but it is not something that should be carried as part of the distro ‘ad infinitum’. Like you said, KDE4 no longer supports new applications because its libraries are too old. Just like with KDE3, it will have to be replaced by the new development at some point. Plasma Desktop has been in development for several years now, it is stable, featureful, and consumes less resources than KDE4.
If KDE4 is removed from Slackware, someone could take over maintenance of the packages. But more likely, no one will want to commit to that, just like how it went with KDE3 – even when it was rebranded to Trinity Desktop. There’s no quality repository for KDE3/Trinity Slackware packages.

Comment from cwizardone
Posted: June 14, 2018 at 19:41

My apologies. I shouldn’t post after too many Heinekens, but still doesn’t change my opinion of kde5. I’ve never forgiven them for kde4.0 and won’t be using kde5. Each to their own.

Comment from cwizardone
Posted: June 14, 2018 at 19:46

BTW, the hardware is less than a year old. An Asus motherboard with a Ryzen CPU, a GeForce 740 graphics card, 16 gigs of ram and a name brand SSD.

Comment from alienbob
Posted: June 14, 2018 at 21:46

cwizardone,
> I’ve never forgiven them for kde4.0
You know that the hubbub about KDE 4.0 is exclusively the fault of certain distros? KDE 4.0 was released as a “tech preview” not meant to be included into distros and not meant for the average enduser. Yet some distros replaced their KDE3 with KDE 4.0 and public outrage followed.
This was, again, not the fault of the developers. Perhaps their PR department should have done a better job which would have prevented this distro failure, but don’t blame the code or the devs.

I started building KDE 4.2 packages when developing the 64bit port of Slackware (read https://alien.slackbook.org/blog/kde3-kde4-and-slackware-13-0/ to refresh your memory). Version 4.2.1 was the first KDE4 release to enter Slackware, replacing KDE3. That was 2009, and by then the KDE4 Desktop Environment had properly stabilized.
I think Plasma5 today is more stable than KDE 4 back then. I also think it’s more than overdue that after 9 years, there’s still a KDE 4 in -current.

Write a comment