Plasma5 instability

Aeterna · 10-19-2019, 09:15 PM

System updated today
plasma ver 5.17.0
Slackware 14.2 Post 14.2-current

Plasma5 is crashed now few times today.

Quote:

Application: Plasma (plasmashell (deleted)), signal: Segmentation fault
[Current thread is 1 (LWP 1697)]

Thread 28 (LWP 2308):
#0 0x00007f13ad18b966 in ?? ()
#1 0x00000000000002a6 in ?? ()
#2 0x0000008113ffebef in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 27 (LWP 2307):
#1 0x00000000000002a9 in ?? ()
#2 0x0000008100000011 in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 26 (LWP 2306):
#1 0x00000000000002ae in ?? ()
#2 0x00000081357f9bef in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 25 (LWP 2305):
#1 0x00000000000002a2 in ?? ()
#2 0x0000008100000000 in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 24 (LWP 2304):
#1 0x00000000000002a3 in ?? ()
#2 0x000000811c0d8600 in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 23 (LWP 2303):
#1 0x00000000000002a8 in ?? ()
#2 0x0000008136ffc700 in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 22 (LWP 2302):
#1 0x00000000000002a1 in ?? ()
#2 0x00000081ada9b0c1 in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 21 (LWP 2301):
#1 0x00000000000002ac in ?? ()
#2 0x00000081980790d0 in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 20 (LWP 2300):
#1 0x00000000000002a4 in ?? ()
#2 0x00000081add2e6e0 in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 19 (LWP 2299):
#1 0x00000000000002aa in ?? ()
#2 0x00000081085e66d0 in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 18 (LWP 2298):
#1 0x00000000000002ab in ?? ()
#2 0x00000081598fabef in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 17 (LWP 2297):
#1 0x00000000000002af in ?? ()
#2 0x000000815a0fbbef in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 16 (LWP 2296):
#1 0x00000000000002b0 in ?? ()
#2 0x00000081adc57c67 in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 15 (LWP 2295):
#1 0x00000000000002a7 in ?? ()
#2 0x0000008100000000 in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 14 (LWP 2294):
#1 0x00000000000002a5 in ?? ()
#2 0x00000081add2e6e0 in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 13 (LWP 2293):
#1 0x00000000000002ad in ?? ()
#2 0x000000817494abef in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 12 (LWP 2290):
#1 0x0000000000000082 in ?? ()
#2 0x000000817514bca0 in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 11 (LWP 1850):
#1 0x0000000000000081 in ?? ()
#2 0x0000008175d4cca0 in ?? ()
#3 0x0000000000000001 in ?? ()
#4 0x000000000685f368 in ?? ()
#5 0x0000000000000004 in ?? ()
#6 0x0000000000000103 in ?? ()
#7 0x000000000685f36c in ?? ()
#8 0x00000000000000a5 in ?? ()
#9 0x00007f13ad18b680 in ?? ()
#10 0x00007f1375d4cc80 in ?? ()
#11 0x0000000000000000 in ?? ()

Thread 10 (LWP 1849):
#1 0x000000000000012f in ?? ()
#2 0x000000817654dca0 in ?? ()
#3 0x0000000000000001 in ?? ()
#4 0x0000000004cb56a8 in ?? ()
#5 0x0000000000000004 in ?? ()
#6 0x000000000000025f in ?? ()
#7 0x0000000004cb56ac in ?? ()
#8 0x000000000000012e in ?? ()
#9 0x00007f13ad18b680 in ?? ()
#10 0x00007f137654dc80 in ?? ()
#11 0x0000000000000001 in ?? ()
#12 0x0000000000000000 in ?? ()

Thread 9 (LWP 1847):
#1 0x0000000000004954 in ?? ()
#2 0x000000817d3b4ca0 in ?? ()
#3 0x0000000000000000 in ?? ()

Thread 8 (LWP 1842):
#1 0x00007f13780021e0 in ?? ()
#2 0x00007f13780021e0 in ?? ()
#3 0x0000000000000001 in ?? ()
#4 0x0019aeea00000001 in ?? ()
#5 0x00007f1378000c30 in ?? ()
#6 0x00007f13a951ec7e in ?? ()
#7 0x0000000000000000 in ?? ()

Thread 7 (LWP 1837):
#1 0x00007f1380009f70 in ?? ()
#2 0x00007f1380009f70 in ?? ()
#3 0x0000000000000001 in ?? ()
#4 0xffffffff00000001 in ?? ()
#5 0x00007f1380003800 in ?? ()
#6 0x00007f13a951ec7e in ?? ()
#7 0x00007f1380003280 in ?? ()
#8 0x0000000180001270 in ?? ()
#9 0x00007f13add2e6e0 in ?? ()
#10 0xffffffff7fffffff in ?? ()
#11 0x0000000000000002 in ?? ()
#12 0x0000000000000004 in ?? ()
#13 0x00007f1380003800 in ?? ()
#14 0x0000000000000001 in ?? ()
#15 0x0000000000000000 in ?? ()

Thread 6 (LWP 1833):
#1 0x000000000000014f in ?? ()
#2 0x00000081ada8e336 in ?? ()
#3 0x0000000000000001 in ?? ()
#4 0x0000000002219c08 in ?? ()
#5 0x0000000000000004 in ?? ()
#6 0x000000000000029f in ?? ()
#7 0x0000000002219c0c in ?? ()
#8 0x0000000000000000 in ?? ()

Thread 5 (LWP 1822):
#1 0x000000000000002b in ?? ()
#2 0x0000008100000000 in ?? ()
#3 0x0000000000000001 in ?? ()
#4 0x0000000000b23c80 in ?? ()
#5 0x0000000000000004 in ?? ()
#6 0x0000000000000057 in ?? ()
#7 0x0000000000b23c84 in ?? ()
#8 0x00007f13ad5355fb in ?? ()
#9 0x00007f13ad18b680 in ?? ()
#10 0x00007f139738ed00 in ?? ()
#11 0x000000000000000e in ?? ()
#12 0x0000000000000000 in ?? ()

Thread 4 (LWP 1787):
#1 0x00007f13a5ed6c10 in ?? ()
#2 0x00007f13ada8e336 in ?? ()
#3 0x00007f13adca8900 in ?? ()
#4 0x00007f13b05a63fc in ?? ()
#5 0x00007f13a5ed6c04 in ?? ()
#6 0x00007f13a5ed6c10 in ?? ()
#7 0x00007f139c0047c0 in ?? ()
#8 0x00007f13adca816a in ?? ()
#9 0x00007f13a5ed6c08 in ?? ()
#10 0x0000000000000000 in ?? ()

Thread 3 (LWP 1704):
#1 0x00007f1398068470 in ?? ()
#2 0x00007f1398068470 in ?? ()
#3 0x0000000000000001 in ?? ()
#4 0xffffffff00000001 in ?? ()
#5 0x00007f1398000c30 in ?? ()
#6 0x00007f13a951ec7e in ?? ()
#7 0x0000000000000000 in ?? ()

Thread 2 (LWP 1703):
#1 0x00000000ffffffff in ?? ()
#2 0x00007f13a7d24cd8 in ?? ()
#3 0x0000000000000001 in ?? ()
#4 0xffffffff008b4d08 in ?? ()
#5 0x0000000000000000 in ?? ()

Thread 1 (LWP 1697):
#1 0x0000000000000000 in ?? ()
[Inferior 1 (process 1697) detached]

maybe this will be useful?

garpu · 10-19-2019, 10:21 PM

Are you on current or 14.2? I thought Plasma 5 was only for current?

ZhaoLin1457 · 10-19-2019, 10:35 PM

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.

RadicalDreamer · 10-19-2019, 11:17 PM

Are you using slackpkg+, if so did you slackpkg install ktown and slackpkg clean-system? Is this a full and updated install of Current?

Aeterna · 10-20-2019, 12:19 AM

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

kgha · 10-20-2019, 03:22 AM

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.

bassmadrigal · 10-20-2019, 01:06 PM

Quote:

Originally Posted by ZhaoLin1457

BTW, the full name of slackware-current is "Slackware 14.2 Post 14.2-current" so I believe that OP runs the -current.

Where did you get this?

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.
       In /etc/os-release, change PRETTY_NAME to:
       PRETTY_NAME="Slackware 14.2 $ARCH (post 14.2 -current)"

Quote:

Originally Posted by garpu

Are you on current or 14.2? I thought Plasma 5 was only for current?

Eric updated the ktown release for 14.2 on Friday.

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.

Alien Bob · 10-20-2019, 02:10 PM

Quote:

Originally Posted by bassmadrigal

Where did you get this?

As far as I know, it is -current, slackware{64}-current, or Slackware{64} 14.2+.

Code:

$ cat /etc/os-release
NAME=Slackware
VERSION="14.2"
ID=slackware
VERSION_ID=14.2
PRETTY_NAME="Slackware 14.2 x86_64 (post 14.2 -current)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:slackware:slackware_linux:14.2"
HOME_URL="http://slackware.com/"
SUPPORT_URL="http://www.linuxquestions.org/questions/slackware-14/"
BUG_REPORT_URL="http://www.linuxquestions.org/questions/slackware-14/"
VERSION_CODENAME=current

Alien Bob · 10-20-2019, 02:17 PM

Quote:

Originally Posted by bassmadrigal

Eric updated the ktown release for 14.2 on Friday.

https://alien.slackbook.org/ktown/14.2/5/

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.

Aeterna · 10-20-2019, 05:22 PM

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.

More about this in another thread: https://www.linuxquestions.org/quest...ed-4175654810/

If one uses a bit of afterthought, -current is surprisingly stable.

so many platitudes in such a short post.. I am crushed. I like -current and I know what is it.

bassmadrigal · 10-20-2019, 06:28 PM

Quote:

Originally Posted by Alien Bob

Code:

$ cat /etc/os-release
NAME=Slackware
VERSION="14.2"
ID=slackware
VERSION_ID=14.2
PRETTY_NAME="Slackware 14.2 x86_64 (post 14.2 -current)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:slackware:slackware_linux:14.2"
HOME_URL="http://slackware.com/"
SUPPORT_URL="http://www.linuxquestions.org/questions/slackware-14/"
BUG_REPORT_URL="http://www.linuxquestions.org/questions/slackware-14/"
VERSION_CODENAME=current

Wow, I never noticed that. Thanks!

Quote:

Originally Posted by Alien Bob

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.

kgha · 10-21-2019, 01:34 AM

Quote:

Originally Posted by Aeterna

so many platitudes in such a short post.. I am crushed.

I'm well aware that I was stating the obvious. Had you taken the obvious into account, you wouldn't have experienced crashes.

Aeterna · 10-21-2019, 07:57 AM

Quote:

Originally Posted by kgha

I'm well aware that I was stating the obvious. Had you taken the obvious into account, you wouldn't have experienced crashes.

this is what I run:

Quote:

# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system

..and I have problems with plasma on exit

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.

Alien Bob · 10-21-2019, 08:27 AM

Quote:

Originally Posted by Aeterna

this is what I run:

..and I have problems with plasma on exit

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)..."

Aeterna · 10-21-2019, 10:18 AM

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)..."

Well as I stated it here:
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