I uploaded KDE-5_19.12 as an early Christmas present. You can download these fresh packages as usual from my ‘ktown‘ repository. Still targeting a full installation of Slackware-current (with KDE4 removed first) these packages will not work on Slackware 14.2.
What’s new in the December 2019 release
This month’s KDE Plasma5 for Slackware contains the KDE Frameworks 5.65.0, Plasma 5.17.3 and Applications 19.12.0. All this on top of Qt 5.13.2. Do not forget to install the new packages md4c, kquickcharts, pulseaudio-qt, kpeoplevcard, and elisa !
Deps:
This month I removed the qt-gstreamer package because the only package which depended on it (telepathy-kde-call-ui) has been removed a few months back with the rest of KDE Telepathy.
I added md4c, which is a dependency for Qt 5.14 but then decided against updating my qt5 package to 5.14 because there’s a lot of software which is not completely ready for this new release of Qt. Maybe next month.
I updated the lensfun and mlt packages to their latest releases and updated sip so that it matches the version in Slackware again.
Frameworks:
Frameworks 5.65.0 is an incremental stability release, see: https://www.kde.org/announcements/kde-frameworks-5.65.0.php but the developers added a new Framework this time: kquickcharts.
Plasma:
Plasma 5.17.3 is a an incremental bug-fix release in the 5.17 cycle of the KDE desktop environment. See https://www.kde.org/announcements/plasma-5.17.3.php
Plasma-extra;
In plasma-extra I updated latte-dock and kdeconnect-framework. The new release of kdeconnect required the addition of two new dependencies to plasma-extra: pulseaudio-qt and kpeoplevcard.
Applications;
The Releases 19.12.0 is the start of a new quarterly release cycle for the Applications, but it is also a rebranding. The old name “Applications” was no longer considered representative for what it offers and “Release Service” is the new name. I will probably keep calling this “Applications” nevertheless, tired as i usually get from overzealous PR folk.
Note that there’s a new application in here, the music player ‘elisa‘. I did not compile elisa against VLC even though that would make it more powerful. If I had installed a vlc package and compiled elisa against it, then the elisa program would fail to run for people that do do not have VLC installed. Feel free to recompile though!
For more info, see https://www.kde.org/announcements/releases/19.12/
Applications-extra:
In applications-extra I updated calligraplan, kstars and krita to their latest releases. In particular this Plan (calligraplan) release is seen as a major milestone achievement.
Telepathy:
Note: KDE Telepathy is no longer part of my ‘ktown’ distribution of KDE Plasma5.
Where to get it
Download the KDE-5_19.12 from the usual location at https://slackware.nl/alien-kde/current/latest/ or one of its mirrors like http://slackware.uk/people/alien-kde/current/latest/ (both these sites are also offering rsync access). Check out the README file in the root of the repository for detailed installation or upgrade instructions.
Development of Plasma5 is tracked in git: https://git.slackware.nl/ktown/ .
A new Plasma5 Live ISO should be ready somewhere later during my Christmas holiday (probably after Christmas) and then you will find it at https://slackware.nl/slackware-live/latest/ (rsync://slackware.nl/mirrors/slackware-live/latest/)
Have fun! Eric
Thank you Eric; happy Christmas to your family and to you.
P.
Happy Christmas!
Just a reminder, Qt 14 is released 12 Dec. Any chance of adding Qt Creator?
Hi Henry
Like I stated in the blog post: I think it is too early to switch to Qt 5.14. And I will not add Qt Creator to the ktown package set. It does not add value to the Plasma5 desktop. I may add it to my regular repository though.
Creator isn’t a high priority. I keep running into walls because of Qt’s target customer base. I’m not building automotive guis for Mercedes or Ford. Not good for scientific computing, like analyzing FITS files of radio astronomy data. I had to process hundreds of images using LCh color space which shows the greatest variance of values, but QRgb to LCh is not a trivial pursuit. Has some nice features for fast gui creation, easy to jump back and forth from Designer to code.
Qt 5.13.2 works, no compelling reason to upgrade. I do transforms from world coordinates to NDC to device coordinates, so the new QTransform feature is useful. I maintain my own Qt 5.14 in /home, so no worries. Can’t use the Wayland compositor yet.
Gledelig Jul!
I withdraw my request for Qt 5.14. I do not believe is is compatible with current. Creator 4.11.0 requires libgssapi_krb5.so.2. When I tried Creator 4.10.1 with Qt 5.14, I couldn’t compile a class that included QtMath. When I put the full path to qtmath.h into the include, it threw all sorts of internal errors. Might be better to wait for Qt 5.15.
You mention “Creator 4.11.0 requires libgssapi_krb5.so.2” which means you did not compile it on Slackware. How then will it even work reliably?
Suffering from congenital indolence (born lazy), I just download the few bits I need from qt.io. Will try compiling Creator without kerberos, which I suspect was added for Windows.
The canned creator package has been good to me for years. Gssapi is a config option under Qt Network. Slackware sez GSSAPI … no. I learned my lesson. At the time, I was analyzing FITS radio astronomy images. I needed QtMath for color space conversion from RGB to LCh on another project. Wasn’t concerned with compiling Creator as long as it worked. Now I’m waiting on a 60-hr render job, so I took the time to compile 5.14 as you suggested. Thank you for your patience. Not a problem with Qt, problem was the idiot behind the wacom tablet.
Qt Creator 4.11.0 with Qt 5.14 works in a sandbox. Of course I can’t turn it loose because of all of the kde5/plasma5 packages compiled with Qt 5.13.2 libraries. The canned version from qt.io was compiled on a Red Hat system with libgssapi for Windows networking. My bad, as usual.
Warning: I won’t be baffled by a mere computer. Stymied, but not baffled.
Happy New Decade!
The best Christmas present, for sure 🙂
Happy Holidays Eric.
Thank you Eric for this unexpected present 🙂
Merry Xmas to all!
Many Thanks Eric. What a Xmas surprise and Xmas present !!!!.
Merry Christmas Eric for you and your family.
Have yourself a slackware little Xmas!
Francisco
I just upgraded my system… it was a long upgrade….
everything went smooth… as Santa’s trip tomorrow night!.
I will update my slack live USB tonight.
Merry Xmas! and Thanks for this Xmas gift!!!!! Best wishes for you and your family this Xmas.!
Francisco
Thanks & merry ?mass!
Happy holidays!
Thank you Eric. It works a treat. Happy holidays to you and your family.
Thanks, Eric, just one thing, QScintilla, is updated in current (2.11.4) 😉
Hi Gérard – hmm he must have done that while I was busy with my own updates. I will add the newer version.
Thank you very much for this new release.
I have seen many liblensfun.so.1 not found in digikam. In /usr/lib64 there is a liblensfun.so.2 linked to liblensfun.so.0.3.95 but no liblensfun.so.1 .
Hi Helios, yes I will have to recompile DIgikam.
Hey Eric,
Updated smoothly, all appeared well…..your Libreoffice 6.3.3 doesn’t work after upgrade….no errors….it fires up and disappears. So far that’s all I’ve come across.
LibreOffice works fine here. Have you made sure to install boost-compat?
Thanks for the reminder, that solved the problem…installing boost-compat that is.
Bob, all is ok. LibreOffice 6.3.3.2 works for me. Some minor nuisances with multi-screen display are fixed. Overall maybe slightly faster. Merry Christmas and a Happy New Year to you.
I rebuilt Digikam and the problem is resolved.
Thank you Eric! Upgraded without problems here.
Merry Christmas to you and your family!
Same problem here as Owen, “…your Libreoffice 6.3.3 doesn’t work after upgrade….no errors….it fires up and disappears.”
fix: https://alien.slackbook.org/blog/libreoffice-6-2-5-packages-available/
root@brainrape:/usr/lib64# ln -s libboost_locale.so.1.72.0 libboost_locale.so.1.71.0
root@brainrape:/usr/lib64# ln -s libboost_system.so.1.72.0 libboost_system.so.1.71.0
root@brainrape:/usr/lib64# ln -s libboost_iostreams.so.1.72.0 libboost_iostreams.so.1.71.0
root@brainrape:/usr/lib64# ln -s libboost_filesystem.so.1.72.0 libboost_filesystem.so.1.71.0
solves the problem here on my end.
How fucking difficult is it to read what I write? Third time on this blog in two days for the same LibreOffice issue, here’s the answer repeated again:
Install my boost-compat package and stop linking incompatible libraries which will only induce crashes.
Thanks Eric! I did the upgrade only with upgradepkg –install-new. I did not use –reinstall. I didn’t have a problem, and it saved some time. I couldn’t see any pitfalls, but maybe you may know of something I’m missing doing this shortcut.
Thank you, Eric! I see you included the Elisa media player. I hope you also please consider including Vvave, a promising KDE music player https://vvave.kde.org/
Hi Gerardo,
I did not include Elisa because i liked it, but because it has been added to KDE Applications 19.12. If vvave ever gets added to Applications while I am still releasing Slackware packages, that’ll be the moment it will appear as a package in ‘ktown’.
Hi Eric
Not sure if this is the right forum for this – let me know elsewhere is better.
I’ve gone down the hell-hole that is hardware video acceleration. Specifically in Kdenlive (per this release), it is indicating “no hardware encoders found” when doing “Check hardware acceleration” in the Config wizard. I have the OS-provided packages:
/var/log/packages/libva-2.6.0-x86_64-1
/var/log/packages/libva-utils-2.6.0-x86_64-1
/var/log/packages/libvdpau-1.3-x86_64-1
/var/log/packages/libvdpau-compat32-1.3-x86_64-1compat32
… as well as your driver package:
/var/log/packages/libva-vdpau-driver-0.7.4-x86_64-2alien
vdpauinfo seems to show all is well but vainfo shows an error:
vainfo
libva info: VA-API version 1.6.0
libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so
libva error: /usr/lib64/dri/nvidia_drv_video.so has no function __vaDriverInit_1_0
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
VLC shows good hardware accel:
VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7)
[00007f869cd5ec40] avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 440.44 Sun Dec 8 03:27:26 UTC 2019 for hardware decoding
– latest binary Nvidia driver installed
– nvidia-uvm module loaded
– kde as per latest alienbob release dec2019
– fresh slackware -current install as per 27 Dec 2019
The only thing I can find is that the vdpau driver package may need to be rebuilt for libva2 however. I get this error when trying to rebuild your package:
vdpau_video.h:284:1: note: previous declaration of ‘vdpau_CreateSurfaceFromV4L2Buf’ was here
284 | vdpau_CreateSurfaceFromV4L2Buf(
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[2]: *** [Makefile:574: vdpau_video.lo] Error 1
make[2]: *** Waiting for unfinished jobs….
In file included from vdpau_video_glx.c:24:
vdpau_video.h:288:12: warning: ‘struct v4l2_buffer’ declared inside parameter list will not be visible outside of this definition or declaration
288 | struct v4l2_buffer *v4l2_buf,
| ^~~~~~~~~~~
vdpau_video.h:287:12: warning: ‘struct v4l2_format’ declared inside parameter list will not be visible outside of this definition or declaration
287 | struct v4l2_format *v4l2_fmt,
| ^~~~~~~~~~~
make[2]: Leaving directory ‘/tmp/libva-vdpau-driver-0.7.4-src-1/src’
make[1]: *** [Makefile:440: all] Error 2
I’ve tried with all the latest ubuntu-provided patches too …
Any help would be appreciated. Thanks.
Hi Robby
I cannot help you with the errors you are getting with trying to enable GPU-assisted rendering. The better place to ask for this kind of help is the linuxquestions.org forum.
What I can do is fix the libva-vdpau-driver package for you. I have added a patch and rebuilt the package on -current. I will upload this soon to my repository.
Hi Eric
The new driver package allows vainfo to generate output correctly now – thank you. Still no luck with hardware encoding on kdenlive (or obsstudio which indicates “info: FFMPEG VAAPI supported”). Will pick it up on the forum.
FYI, I have recompiled a bunch of packages – it was required after the update to Python 3.8 in Slackware-current.
I’ll upload them shortly.
I jumped from the fence and installed slackware64 current with your kde5 packages. So this is a fairly recent experience for me. I have one issue with CJK fonts (I actually use only korean). The TTC file in noto-cjk-fonts-ttf package doesn’t seem to be properly handled.
Though the list of CJK fonts appears in the list of fonts in KDE5, the preview of these fonts gives nothing in font configuration nor in KCharSelect. Additionally the CJK fonts are not listed in libreoffice 6.3.4.
I tried to install OTC files. Same result.
Korean characters started to work after I installed nanum fonts from SBo (ttf files).
One caveat: I didn’t install all font files from Slackware but I don’t see why this would matter.
Do you have the same issue? Thanks.
Hi gegechris99.
The handling of TTC font files in LibreOffice seems to be imperfect. I can not see any font contained in NotoSansCJK.ttc. If you can find a fix that does not involve switching from a single TTC file to many TTF files, let me know.
In a “fc-list” command or in kcharselect, I can find Korean font easily. I searched for “KR” in the fc-list output and in kcharselect I selected “East Asian Scripts”, “Hangul Jamo”, and “Noto Sans CJK KR”.
Hi Eric,
If you have one CJK font installed in your system, then it seems that whatever CJK font you select in kcharselect will display CJK characters. But if you look at the preview of a Noto CJK font in system configuration>font>font management, it will be blank while the preview of Nanum (ttf) or any CJK font installed as ttf is OK.
If I remove Nanum font and have no other CJK font installed in my system (except Noto CJK package), then filenames in Korean don’t display properly in dolphin and Konsole (with both Hack font or Noto CJK KR font). After I install Nanum font, these filenames are OK even in Konsole with Hack font. This leads me to believe that Noto CJK TTC file is not correctly handled in KDE5. This is not to say that it’s a bug. My gut feeling is that currently the Noto CJK package with TTC file is not of any use in KDE5 (I may be wrong as I’m no font specialist).
I will continue to investigate as I’d like to have Noto CJK (KR) font working in KDE5. I will let you know.
And finally thank you very much for your huge work on KDE5.
Hi Eric,
Problem fixed. File permission of NotoSansCJK.ttc must be changed from 640 to 644. Fonts are also working in Libreoffice.
Additionally I found that scim is no longer working on QT5 application (ex: kate). I’ve tried ibus for Korean input with success on both QT5 (kate) and GTK (firefox) applications (packages from SBo: cldr-emoji-annotation, ibus, ibus-hangul).
Hope this helps
Hi gegechris99,
That is a nice find! I’ll fix the font package.
About scim versus ibus, there have been other reports that ibus might be needed. I’ll gladly accept packaging instructions that allow for the removal of SCIM and addition of ibus.
Thank you and I wish you a very good new year!
I’m running Slackware current x64 (kernel 5.4.8) and KDE Plasma 5.17.3. Selecting hibernate hangs when trying to write to swap. From an Xfce4 session hibernate is working as allways. Also, no errors in pm-suspend.log.
Hi MLiviu,
Hibernate and resume on my Plasma5 powered laptop works just fine. Still running a 5.4.7 kernel though.
I just updated to the latest -current with kernel 5.4.8 and hibernate/resume from Plasma5 is still working perfectly.
Thank you for all your work. I have a request for your next release. Would you upgrade sddm-qt5 to a newer version? the package SDDM-KCM now creates files in /etc/sddm.conf.d and version 15 of sddm-qt5 does not read the folder structure /etc/sddm.conf.d/.
Hi Chris
I had been trying to hold off on an upgrade of sddm because previous attempts at introducing a newer version were not a succes. I guess that now it has become un-avoidable.
If you do not mind me asking, what issues did you have when trying to introduce newer versions? From a cursory glance your build script (minus patches) seemed to build version 18.1 okay. I did not try the resulting binaries though.
I suggest you try the binaries then.
I see what you mean now. Version 16 and up I am getting the following in sddm.log
[20:26:30.725] (II) DAEMON: Initializing…
[20:26:30.730] (II) DAEMON: Console kit interface found
[20:26:30.730] (WW) DAEMON: QDBusConnection: error: could not send message to service “org.freedesktop.ConsoleKit” path “/org/f
reedesktop/ConsoleKit/Manager” interface “/org.freedesktop.ConsoleKit.Manager” member “ListSeats”: Invalid interface class: /or
g.freedesktop.ConsoleKit.Manager
[20:26:30.730] (II) DAEMON: Starting…
Looks like a reasonable explanation of what is happening is here: https://github.com/ConsoleKit2/ConsoleKit2/pull/102. Not sure if this will be all of the issues though.
Hi alienbob,
I think I found a fix for sddm-qt5. I grabbed a patch from a gentoo repository here: https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-misc/sddm/files.
The patch in question is sddm-0.16.0-ck2-revert.patch. I compiled sddm 0.18.1 with this patch and I was able to login to kde/plasma. I am going to test it for a few days and see if everything works.
Let me know your experiences. If it works for you then I’ll add it to the January batch of updates.
Editing SDDM login settings via systemsettings5 are read and applied by sddm-qt5. I believe it is ready to be included. I applied the following patches to 0.18.1: sddm_consolekit.diff from your patches and sddm-0.16.0-ck2-revert.patch from the gentoo repo. I also used your cmake configuration for generating the binaries.
Dear Eric,
hope you’ve been able to enjoy the festive season and that the new year has had a good start.
Your new lensfun-0.3.95 package broke my old ufraw package. After a lot of fiddling I decided to give up ufraw completely – even with the older lensfun I couldn’t get it going as it should , there seems to be trouble with later exiv2 versions. Also, the number of ufraw patches out there suggests that the ufraw source is far from stable.
Rawtherapee-5.7 builds fine against the new lensfun. The rawtherapee package in your repo seems to be slightly outdated, though… 😉
KG, what about the ‘fork’ of ufraw, https://sourceforge.net/projects/nufraw/ ? That is being actively developed as far as I can see.
Yes, I’ve tried nufraw as well. Latest official source release is dated May 2018. Ran into the same problems as with ufraw: I had to add a few patches, for a successful build, but even then the packages didn’t work properly. When building against lensfun-0.3.2 everything works except that exiv information isn’t picked up. When building against lensfun-0.3.95 the program starts OK but segfaults (without further explanation) when I try to open a raw image.
Since rawtherapee works fine, I’ll stick to that for the few instances I want to edit a raw image.
Just wondering, when I do `upgradepkg` on slackware64 current, a few ktown packages get “upgraded.” Should we then `upgradepkg` back to the ktown version, or keep the current package?
What packages exactly Henry?
Here’s a few in no particular order:
gpme
exiv2
phonon
grantlee
LibRaw
qt-gstreamer
phonon-gstreamer
sip
QScintilla
akonadi
poppler
Whenever i have ‘ktown’ version of a package that is also contained in Slackware itself, then I have a good reason for that (usually added Qt5 support).
If you are using the slackpkg+ extension then you have that misconfigured. You must give the packages from my ktown repository higher priority than their Slackware originals.
The file /etc/slackpkg/slackpkgplus.conf even comes with the instructions to adjust priority but you need to enable that yourself:
I learned that the hard way. I don’t use slackpkg. When a new ChangeLog.txt is issued, I wget the new packages and run updatepkg. Something since the previous kernel update (5.4.13, not today’s 5.4.14) hosed the startx script. Too lazy to hunt it down, I now run find on dep and kde then exec upgradepkg on each txz. Decades-old habit, I’ll look into this new-to-me slackpkg+ utility.
Speaking of lensfun, there’s an older version on alien than on ktown (I accidentally “upgraded” to it a couple of times 🙂 ):
$ slackpkg search lensfun
[ Status ] [ Repository ] [ Package ]
installed ktown lensfun-0.3.95-x86_64-2alien
uninstalled(masked) alienbob lensfun-0.3.2-x86_64-1alien
(I think in my last update I saw another package with an older version but I cant find it right now).
Cheers!
Thanks, I will remove lensfun digikam and darktable from my regular repository, they are obsolete there.
Hi Eric,
I built packages for ibus on Slackware64 current using slackbuild scripts from SBo. All packages listed below are available in SBo.
1) I built cldr-emoji-annotation (ibus dependency)
2) I built ibus. as per README, I added these commands into my ~/.bashrc:
export GTK_IM_MODULE=ibus
export XMODIFIERS=@im=ibus
export QT_IM_MODULE=ibus
These commands should be better placed into scripts /etc/profile.d/ibus.(sh|csh) in the ibus package
3) Ibus needs at least one input method engine. I only built ibus-hangul for Korean input but these engine packages should be considered:
ibus-anthy for Japanese
ibus-chewing for Chinese with its dependencies (gob2 and libchewing)
ibus-unikey for Vietnamese
And that’s all. Ibus will automatically start with KDE 5 (no need for further script/configuration).
ibus-qt is only for QT4, so it’s not needed.
There is also ibus-skk package for SKK (Simple Kana-Kanji). There are a couple of dependencies for this package (gnome-common, libgee1 ,libskk) and I’m not sure it’s needed to start adding ibus packages.
I don’t know if the above are packaging instructions but that’s what I did and would suggest to do.
Finally scim should not be installed.
Hope this helps.
Hi Eric. Today’s -current update removed db42 and db44.
Can you tell if those packages are a dependence of ktown? So I could remove them safely.
Thanks!
I did an ldd on /{usr/}{s,}bin/* and nothing depends on /lib64/libdb-4.2.so, and /lib64/libdb-4.4.so is part of aaa_elflibs now.
So I guess it’s safe to remove them.
It’s safe to remove these two packages.
Hi Eric and Ricardo, thanks for the tip!
Hi Eric,
Hope it is the right place to report (since I have ktown, some of your packages outside ktown and SBo packages installed) :
kamoso that is part of your ktown release won’t launch for my integrated webcam complaining something is missing from gstreamer-bad.
Your gst-plugins-bad was installed and up-to-date.
After installing alongside the SBo SlackBuild it seems to work.
This is on current from jan. the 7th and Christmas Plasma.
Thanks again for all your work : you made Slackware accessible for me long time ago and I can’t be more gratefull !
Hi Tonus,
Gstreamer-bad is not part of ktown and kamoso works without it. I guess that there’s something in that gstreamer-bad package which is not OK for -current and does not play nice with kamoso.
I may have to recompile/upgrade it.
Hi Eric
Using Live-Slack 1.3.5
I’m having problems using the Search settings in System Settings. If I follow
KDE -> System Settings -> Search -> File Search
then disable file search by unchecking the Check Box “Enable File Search”, then pushing the “Apply” button, then If I close System Settings then go back in
KDE -> System Settings -> Search -> File Search
I find that File Search is still enabled.
Whatever I do enabling/disabling seems to not change the lines in .config/baloofilerc
I’m expecting to see the line Indexing-Enabled toggle between false/true depending on the setting in KDE -> System Settings -> Search -> File Search
If I change the file .config/baloofilerc manually this does get reflected in KDE -> System Settings -> Search -> File Search
I searched kde bugs and can’t find anything similar reported. I’m also getting the same experience when running Current updated with slackpkg.
I did raise a thread on Linux Questions, bu closed it as solved when I found I could manually edit .config/baloofilerc to get the result I wanted.
Any thoughts as to what the problem might be?
Alex
ALex,
This is not a problem with liveslak, or with my Live ISO. It is functionality in Plasma5. If you want to have that or its default changed, I suggest that you open a bug report at https://bugs.kde.org/
I am find with Baloo’s current behaviour. Just give it a couple of hours to finish its initial sync. The benefits are huge IMO.
Hi Eric
I’ve added a bug to https://bugs.kde.org/
418513 – Can’t disable File Search from System Settings
This is what I’m seeing in Slackware Current with ktown and multilib.
I had hoped to see things differently in live-slack, but didn’t.
It’s probably my misunderstanding as to how this is supposed to work.
Alex
Two things.
I told you that the Slackware Plasma5 Live has baloo disabled by default when you boot the ISO.
You mention that you have an issue with baloo (you cannot disable it) in “Live-Slack 1.3.5” but that contradicts my statement. I therefore assume that by “Live-Slack 1.3.5” you are NOT referring to my Live ISO image. And I am wondering what are you running then?
Also, something like a “Live-Slack” does not exist. It’s “liveslak” when you refer to the scripts used to generate the ISO images, or “Slackware Live Edition” when you refer to the Live OS which runs from a CDROM, DVD or USB stick. And once you use “setup2hd” to install the OS to a hard drive, there is not a trace of “Live” left and the hard disk installed OS is “just Slackware”.
Final thought: have you checked the file ownership of your baloofilerc file and the directory it is in? Can your non-root user account actually write to that file?
Hi Eric
I apologise for not using the correct terminology.
It is liveslak I’m using.
I’m using slackware64-live-plasma5-current.iso downloaded from https://slackware.nl/slackware-live/1.3.5/
The md5sum is e76e5c8cc36d02aea51a858a377ff7b2
You’re quite correct File Search in liveslak is disabled by default.
How do I enable File Search in liveslak?
I’ve tried to enable it from System Settings -> File Search by ticking the [Enable File Search] check box, then pressing Apply
From the command line I’ve tried balooctl enable
Neither enables baloo file search.
Alex
Seemingly the bug I raised with KDE is a duplicate of https://bugs.kde.org/show_bug.cgi?id=417127
Fixed in Plasma 5.18.2 / Frameworks 5.68.0
You’re in luck because I am uploading a new set of packages, including Frameworks 5.68.0 and Plasma 5.18.3.
Thanks for the upgrades to take us to Frameworks 5.68.0 and Plasma 5.18.3
From my point of view Managing Search from System Settings now works as expected.
Alex
Also, it is not entirely clear to me which of the ISOs you are using. The Plasma5 Live ISO has Baloo disabled by default. Just to be sure, I fired up the Plasma5 ISO in a QEMU virtual machine and sure enough, File Search is disabled and there are zero baloo processes when I look at “ps ax” output.
Hi Eric
Thanks for the reply.
I’m using slackware64-live-plasma5-current.iso downloaded from https://slackware.nl/slackware-live/1.3.5/
The md5sum is e76e5c8cc36d02aea51a858a377ff7b2
You’re quite correct File Search is disabled by default. How do I enable it in live-slack?
I thought you were looking for exactly the opposite.
In Slackware Plasma5 Live, remove these two lines from ~/.config/baloofilerc
[Basic Settings]
Indexing-Enabled=false
After that, you will be able to enable/disable File Search at will. The above two lines are a hard override to everything you tried.