SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
BTW, the full name of slackware-current is "Slackware 14.2 Post 14.2-current" so I believe that OP runs the -current.
@Aeterna
In the past I had crashes of Plasma5 because incompatibilities with the video drivers. Was a particular issue with R600 drivers and Radeon HD3200 or Radeon HD4350 over more than one year ago, and I helped the former forum member Darth Vader to debug it. And somehow he fixed those crashes on those particular video cards.
However, even today, I have random freezes with a Radeon R5-240 and current Plasma5.
So, my suggestion is to look for the video drivers.
Last edited by ZhaoLin1457; 10-19-2019 at 10:43 PM.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,022
Original Poster
Rep:
Thank you everybody for suggestions,
My problem was solved after the upgrade of qt5 and qt5-webkit (I run slackpkg upgrade few minutes ago)
only these two packages were listed for update so I believe that this solved my problem.
@RadicalDreamer:
yes, I always run clean-system after update.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,097
Rep:
Since -current can be seen as Slackware's development branch, crashes will happen when upgrades to -current affects 3rd party stuff, with Eric's Plasma5 as one example.
There are, however, ways to prevent nasty surprises:
1) Always check the -current changelog before upgrading, and
2) keep yourself informed about the 3rd party stuff you use by following information from the maintainers. In this particular case, Eric's blog ( https://alien.slackbook.org/blog/ ) thus would have given you information and solutions, e.g installing his icu4c-compat package which would have avoided your crash in the gap between the upgrade of aaa_elflibs in -current (Oct. 14) and Eric's rebuilt qt5 and qt5-webkit packages.
That is incorrect statement, look at the ChangeLog.txt please.
Everytime I re-generate the repository metadata (the stuff that makes slackpkg+ or slapt-get work with the repo), the timestamps of directories get updated as well. The packages remain unchanged, but files like MANIFEST.bz2, PACKAGES.TXT etc are always re-created from scratch.
I guess I should perhaps remove those Plasma5 packages for Slackware 14.2, they are now 2 years old and receive no security updates. Anyone who wants to run Plasma 5 should be running Slackware-current.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,022
Original Poster
Rep:
Quote:
Originally Posted by kgha
Since -current can be seen as Slackware's development branch, crashes will happen when upgrades to -current affects 3rd party stuff, with Eric's Plasma5 as one example.
There are, however, ways to prevent nasty surprises:
1) Always check the -current changelog before upgrading, and
2) keep yourself informed about the 3rd party stuff you use by following information from the maintainers. In this particular case, Eric's blog ( https://alien.slackbook.org/blog/ ) thus would have given you information and solutions, e.g installing his icu4c-compat package which would have avoided your crash in the gap between the upgrade of aaa_elflibs in -current (Oct. 14) and Eric's rebuilt qt5 and qt5-webkit packages.
That is incorrect statement, look at the ChangeLog.txt please.
Everytime I re-generate the repository metadata (the stuff that makes slackpkg+ or slapt-get work with the repo), the timestamps of directories get updated as well. The packages remain unchanged, but files like MANIFEST.bz2, PACKAGES.TXT etc are always re-created from scratch.
I guess I should perhaps remove those Plasma5 packages for Slackware 14.2, they are now 2 years old and receive no security updates. Anyone who wants to run Plasma 5 should be running Slackware-current.
Sorry for the noise. I was really surprised when I saw the updated timestamps on the directories and no mention of it on your blog. Guess I should've looked a bit closer. Thanks for the correction and I'll update my previous post.
my solution is simpler and that is why my main system never crashed with -current:
I am running second instance of Slackware -current in VM. First I upgrade VM client and then if all works I run upgrade of main system.
If I post any sorts of problems, these are with VM client and my main system is patiently waiting for a solution.
I don't have Slackware kernel installed (removed completely) but I have two custom kernels: latest and last good. So up until now I did not have any issues with my working main system. This additionally protects me from any possible kernel related troubles.
I think that whatever your opinions/rants they are not applicable here and I consider them off topic as issue is solved.
when I run the above again later my problem was fixed. So I did nothing wrong.
Indeed, you did nothing wrong.
The first update caused some breakage for people that do not have icu4c-compat installed from my regular repository. Which is what you experienced.
Your second update fixed that issue by applying the fixed/recompiled packages in my Plasma5'ktown' repository.
Next time though, please use the common name "Slackware-current" instead of creating doubt with the less familiar "Slackware 14.2 x86_64 (post 14.2 -current)..."
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,022
Original Poster
Rep:
Quote:
Originally Posted by Alien Bob
Indeed, you did nothing wrong.
The first update caused some breakage for people that do not have icu4c-compat installed from my regular repository. Which is what you experienced.
Your second update fixed that issue by applying the fixed/recompiled packages in my Plasma5'ktown' repository.
Next time though, please use the common name "Slackware-current" instead of creating doubt with the less familiar "Slackware 14.2 x86_64 (post 14.2 -current)..."
No problem I can use Slackware-current name although I am surprised that anyone is surprised: just Open system info in Plasma.
I did use full name as in system info because I thought that this will give precise information what I am running
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.