Plasma5 instability
System updated today
plasma ver 5.17.0 Slackware 14.2 Post 14.2-current Plasma5 is crashed now few times today. Quote:
|
Are you on current or 14.2? I thought Plasma 5 was only for current?
|
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. |
Are you using slackpkg+, if so did you slackpkg install ktown and slackpkg clean-system? Is this a full and updated install of Current?
|
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. Thank you again |
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. More about this in another thread: https://www.linuxquestions.org/quest...ed-4175654810/ If one uses a bit of afterthought, -current is surprisingly stable. |
Quote:
As far as I know, it is -current, slackware{64}-current, or Slackware{64} 14.2+. EDIT: I was incorrect on this and never realized it had been updated from 14.2+. I found the entry in the changelog from the mass rebuild in 2018. Code:
a/aaa_base-14.2-x86_64-4.txz: Rebuilt. Quote:
https://alien.slackbook.org/ktown/14.2/5/ EDIT: Eric corrected my incorrect belief it had been updated based on directory timestamps. It's still about 2 years old. |
Quote:
Code:
$ cat /etc/os-release |
Quote:
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. |
Quote:
|
Quote:
Quote:
|
Quote:
|
Quote:
Quote:
when I run the above again later my problem was fixed. So I did nothing wrong. However you refer me to this: https://www.linuxquestions.org/quest...ed-4175654810/ 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. |
Quote:
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)..." |
1 Attachment(s)
Quote:
https://www.linuxquestions.org/quest...-a-4175662778/ I have icu4c-compat installed and installed it as soon package became originally available in your collection some time ago. 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 |
All times are GMT -5. The time now is 02:20 PM. |