LinuxQuestions.org - All Things KDE5/Plasma for Slackware Users.

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - All Things KDE5/Plasma for Slackware Users. (https://www.linuxquestions.org/questions/slackware-14/all-things-kde5-plasma-for-slackware-users-4175670109/)

Quote:

Originally Posted by pchristy (Post 6270319)

Whilst this may fix the specific issue in Slackware, I feel it is still important to patch solid as well. The developer has acknowledged that there is a bug in solid:

Link: https://invent.kde.org/frameworks/so...bfdb79e7d3d1b6
(Scroll to bottom)

There may be other - as yet undiscovered - situations which trigger this crash, so hopefully the patch for solid will also be incorporated into Slackware soon.

In other words, the rc.S patch fixes the specific, the solid patch fixes the generic.

--
Pete

I know the issue very well , im the 1st on report here and point to solid , but we know solid 5.85 arrives fixed and slackware make a better directory organization , then WE HAVE DOUBLE FIX.

Because now we have solid-5.84 thats the version we need fix , and for now its at least usable.

The solid FIX you claim , arrives on 5.85 , wait.

Yes indeed, you were the first to point to solid, and it enabled those of us affected to "downgrade" to the earlier version and keep running!

Sorry if your efforts seemed to get over-looked in the ensuing rush to find the fix!

:hattip:

--
Pete

Quote:

Originally Posted by pchristy (Post 6270319)

Plasma 5.85 is expected to be released on 14 AUG. So if Pat doesn't decide to add the Solid patch, the updated version should make it to Slackware in around 2.5-3 weeks if Pat sticks to upgrading it within a few days of release.

I've got a stupid question about KDE "Plasma 5".

If you have to update the entire stack (frameworks or plasma, etc), why split kdelibs into separate packages? It just doesn't make sense to me that if the entire thing needs to be updated why have 10000 packages to update instead of just one?

All of them get version bumped at the same time so it's not like there is more actual work going on to any lib that doesn't get any code changes so it turns out to be more actual work and more files to deal with.

Quote:

Originally Posted by Skaendo (Post 6270472)

Probably because all major distributions excluding Slackware uses dependencies resolution and usually they do not install everything like us.

They install just what they need for a particular feature.

Quote:

Originally Posted by LuckyCyborg (Post 6270476)

I suppose that makes sense.

However, I don't install KDE but I do install KPatience and it went from installing 3 packages (kpat, kdelibs and libkdegames) to 30 packages. Where is the difference? I don't think that you can install too many programs/applications from KDE without needing at least most of what was in kdelibs.

Quote:

Originally Posted by Skaendo (Post 6270477)

KDE devs decided to split it up to allow non-KDE software to use specific components of what would've been in kdelibs without needing to introduce a dependency on the whole thing.

When you try and install KDE software without installing all of Plasma5, it will bring in a lot of packages as you've seen, but if someone only wants to use khtml (I don't know why they would, but, it's my example), the required list could potentially be a lot smaller.

My guess is that KDE devs figured the requirement of including kdelibs was high enough that many people wouldn't develop using their libraries unless they knew it was basically a KDE app. This gives outside devs more flexibility to allow them to use some functionality of KDE without bringing in the whole kitchen sink.

Quote:

Originally Posted by Skaendo (Post 6270477)

I don't believe that you need all of the 30 packages just to satisfy kpat's dependencies.

For example, a Kubuntu 20.04 shows these dependencies for kpat:

Code:

Depends: kdegames-card-data-kf5 (>= 4:4.10), kio, libc6 (>= 2.29), libfreecell-solver0, libkf5completion5 (>= 4.97.0), libkf5configcore5 (>= 4.98.0), libkf5configgui5 (>= 4.97.0), libkf5configwidgets5 (>= 4.98.0), libkf5coreaddons5 (>= 5.2.0), libkf5crash5 (>= 5.15.0), libkf5dbusaddons5 (>= 4.97.0), libkf5guiaddons5 (>= 4.96.0), libkf5i18n5 (>= 4.97.0), libkf5kdegames7 (>= 4:19.12.3~), libkf5kiocore5 (>= 5.10.0), libkf5newstuff5 (>= 4.95.0), libkf5widgetsaddons5 (>= 4.96.0), libkf5xmlgui-bin, libkf5xmlgui5 (>= 4.98.0), libqt5core5a (>= 5.12.2), libqt5gui5 (>= 5.9.0~) | libqt5gui5-gles (>= 5.9.0~), libqt5svg5 (>= 5.9.0~), libqt5widgets5 (>= 5.9.0~), libqt5xml5 (>= 5.9.0~), libstdc++6 (>= 4.1.1)

Maybe some of those depencencies also have dependencies.

But then again, if you care about dependencies maybe Slackware is not the right distro for you :)

Wait, I just remembered that I have installed a tool called sbbdep (https://slackbuilds.org/repository/1...?search=sbbdep), I'm not sure how accurate it is but it reports:

Code:

$ sbbdep $(which kpat)

sync cache /home/richis/sbbdep.cache

cache up to date



check /usr/bin/kpat, 64bit binary

 .. from package kpat-21.04.3-x86_64-1



aaa_glibc-solibs = 2.33-x86_64-2 | glibc = 2.33-x86_64-2

aaa_libraries = 15.0-x86_64-7 | gcc = 10.3.0-x86_64-2

aaa_libraries = 15.0-x86_64-7 | gcc-g++ = 10.3.0-x86_64-2

freecell-solver = 6.2.0-x86_64-3

kauth = 5.84.0-x86_64-1

kcodecs = 5.84.0-x86_64-1

kcompletion = 5.84.0-x86_64-1

kconfig = 5.84.0-x86_64-1

kconfigwidgets = 5.84.0-x86_64-1

kcoreaddons = 5.84.0-x86_64-1

kcrash = 5.84.0-x86_64-1

kdbusaddons = 5.84.0-x86_64-1

kguiaddons = 5.84.0-x86_64-1

ki18n = 5.84.0-x86_64-1

kio = 5.84.0-x86_64-1

kpat = 21.04.3-x86_64-1

kservice = 5.84.0-x86_64-1

kwidgetsaddons = 5.84.0-x86_64-1

kxmlgui = 5.84.0-x86_64-1

libkdegames = 21.04.3-x86_64-1

qt5 = 5.15.2-x86_64-10

Maybe you can trim you package list for kpat after all :)

Cheers,

Quote:

Originally Posted by bassmadrigal (Post 6270502)

Yes, IIRC the size of kdelibs and co. was the number one complain for not using them in external projects, which derived in the current split and tiers of KF5, but to make the lives of distro packagers a bit easier they still release them as a whole.

Quote:

Originally Posted by richarson (Post 6270505)

I don't believe that you need all of the 30 packages just to satisfy kpat's dependencies.

For example, a Kubuntu 20.04 shows these dependencies for kpat:

I literally installed kpat then had to run it from terminal just to figure out what it was asking for.

Quote:

attica karchive kauth kcodecs kcompletion kconfig kconfigwidgets kcoreaddons kcrash kdbusaddons kdeclarative kglobalaccel kguiaddons ki18n kiconthemes kio kitemviews kjobwidgets knewstuff kpackage kpat kservice ktextwidgets kwidgetsaddons kwindowsystem kxmlgui libkdegames solid sonnet syndication

I'm not really complaining or anything, I can figure it out as I did. I'm just trying to figure out why they split kdelibs. I don't know too many projects that use KDE libraries. I know that LXQt does, but with the new and improved Qt license who would want to develop on KDE/Qt. Don't get me wrong, GTK is a mess as well now with CSD so the whole system looks like a cobbled together mess.

Quote:

Originally Posted by Skaendo (Post 6270508)

I don't know too many projects that use KDE libraries.

This is probably a big reason they decided to split it. People weren't using KDE libraries because the footprint was too big when they had to require all of kdelibs.

It is likely their hope that more people will start using KDE libraries now that they're much smaller and may not pull in nearly as many dependencies.

The last week's new features, bug fixes and performance improvements,

Quote:

We made a big improvement to Plasma’s high DPI support on X11 this week!......

https://pointieststick.com/2021/07/3...-hidpi-on-x11/

Thanks for the link, cwizardone. It was really good to see the noted improvement in the weather widget configuration... much better.

This last week's new features, bug fixes and performance improvements,

https://pointieststick.com/2021/08/0...kde-stability/

Quote:

This was a major bugfix week, with many important fixes to our core apps as well as the touchscreen experience.........

WARNING: if your using akonadi don't upgrade MariaDB

There might be a bug or incompatibility between akonadi and MariaDB 10.6.4.

I have upgraded and now kmail is broken.

In akonadi logs I see errors like this:

DB error: "Incorrect datetime value: '2021-08-07T22:52:47Z' for column `akonadi`.`pimitemtable`.`atime` at row 1"

There might be a mysqld option to avoid this issue but I haven't found it yet.

I opened https://bugs.kde.org/show_bug.cgi?id=440717 to make the developers aware.