Page 2 of 2

Re: Mageia 6 Plasma Dolphin crash

PostPosted: Mar 18th, '18, 10:42
by morgano
You may want to help trying out Plasma5.12 and related updates.
* not for the unexperienced *

https://bugs.mageia.org/show_bug.cgi?id=22656

I am running it on two production machines + tests, and for us it have less but different quirks.

It is a bit tedious to test "only" the related updates though.
https://ml.mageia.org/l/arc/qa-discuss/ ... 00067.html

The adventorous me did the easy thing and installed *all* from testing and -knock on wood- system is stable.

Re: Mageia 6 Plasma Dolphin crash

PostPosted: Mar 19th, '18, 15:34
by wintpe
me too i do the all, on a daily basis

as im more interested in the stability of the updates, and feeding back any new quirks to QA rather than their individual impact on those updating to them.

regards peter

Re: Mageia 6 Plasma Dolphin crash

PostPosted: Mar 26th, '18, 13:42
by spring
Having fairly regular warnings on closing Dolphin:

Code: Select all
Application: kdeinit5 (kdeinit5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f080cc2f800 (LWP 5766))]

Thread 2 (Thread 0x7f07ef94f700 (LWP 5768)):
[KCrash Handler]
#6  0x00007f080b113818 in raise () at /lib64/libc.so.6
#7  0x00007f080b114f2a in abort () at /lib64/libc.so.6
#8  0x00007f080b15243a in  () at /lib64/libc.so.6
#9  0x00007f080b159246 in malloc_consolidate () at /lib64/libc.so.6
#10 0x00007f080b15cb37 in _int_malloc () at /lib64/libc.so.6
#11 0x00007f080b15f633 in calloc () at /lib64/libc.so.6
#12 0x00007f0806df23e3 in  () at /usr/lib64/nvidia-current/tls/libnvidia-tls.so.390.42
#13 0x00007f0807d96ed1 in g_malloc0 () at /lib64/libglib-2.0.so.0
#14 0x00007f0807daf93d in g_slice_free1 () at /lib64/libglib-2.0.so.0
#15 0x00007f0808ae63d9 in __nptl_deallocate_tsd.part.4 () at /lib64/libpthread.so.0
#16 0x00007f0808ae7809 in start_thread () at /lib64/libpthread.so.0
#17 0x00007f080b1d5e0d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f080cc2f800 (LWP 5766)):
#0  0x00007f080b1e32eb in __lll_lock_wait_private () at /lib64/libc.so.6
#1  0x00007f080b15b7d5 in _int_free () at /lib64/libc.so.6
#2  0x00007f080b15ee18 in free () at /lib64/libc.so.6
#3  0x00007f080b7187e8 in (anonymous namespace)::Q_QGS_customTypes::innerFunction()::Holder::~Holder() () at /lib64/libQt5Core.so.5
#4  0x00007f080b1167af in __cxa_finalize () at /lib64/libc.so.6
#5  0x00007f080b5165f3 in __do_global_dtors_aux () at /lib64/libQt5Core.so.5
#6  0x00007ffc907fffb0 in  ()
#7  0x00007f080cae7a57 in _dl_fini () at /lib64/ld-linux-x86-64.so.2

Re: Mageia 6 Plasma Dolphin crash

PostPosted: May 13th, '18, 14:45
by spring
major updates to plasma on weekend of 12 May 2018 did not help this issue. Still Dolphin takes 100% of a core and needs to be killed by hand. It has stopped generating a bug report if you close it normally.

Add kmozillahelper to the list of things that take 100% of a core and need to be killed by hand also since updates.

Re: Mageia 6 Plasma Dolphin crash

PostPosted: May 30th, '18, 10:04
by spring
The issue with Dolphin crashing on exit, and maxing out 1 core appears to have stopped as of late may 2018 - many, many plasma-related updates recently, so something positive :)
So, for me, as of today, this appears to be [Solved] - maybe OP can confirm?

Re: Mageia 6 Plasma Dolphin crash

PostPosted: Jun 8th, '18, 17:02
by spring
cancel that - problem persists, had a glorious week or 2 of no dolphin troubles, then today it kicked off again.

Re: Mageia 6 Plasma Dolphin crash

PostPosted: Jun 8th, '18, 19:59
by morgano
Have you searched if there is a bug report on this at https://bugs.mageia.org/
When you have searched and if you do not find one, please lease open a bug there.
In either case, then please post a link to the bug here.

Re: Mageia 6 Plasma Dolphin crash

PostPosted: Jun 15th, '18, 18:39
by spring
It's was appearing in various forms in Bug reports for a while now, example: https://bugs.mageia.org/show_bug.cgi?id=21296 but this exact crash has not happened to me for a while, now Dolphin hangs int he background taking up 100% of a core until i kill it manually when i close - this seems only to happen if i use SMB or a (F4) Terminal in Dolphin.

It's frustrating because it is not chronic, sometimes it happens, sometimes not.

Re: Mageia 6 Plasma Dolphin crash

PostPosted: Jun 15th, '18, 18:56
by doktor5000
spring wrote:It's frustrating because it is not chronic, sometimes it happens, sometimes not.

Well, that is a problem for a bugreport, in case there is no reproducible error then it's pretty hard for the developers to try to nail this down.

Did you try the workaround mentioned in that bug, does it help in your case?

Re: Mageia 6 Plasma Dolphin crash

PostPosted: Jun 17th, '18, 00:39
by yankee495
spring wrote:It's was appearing in various forms in Bug reports for a while now, example: https://bugs.mageia.org/show_bug.cgi?id=21296 but this exact crash has not happened to me for a while, now Dolphin hangs int he background taking up 100% of a core until i kill it manually when i close - this seems only to happen if i use SMB or a (F4) Terminal in Dolphin.

It's frustrating because it is not chronic, sometimes it happens, sometimes not.



I had a problem when closing konsole where it would show 100% CPU on one core until I killed it.
I could open a konsole (no Dolphin) and close it and it'd hang, but it quit with no updates.
I didn't even run anything in it. Your F4 and Dolphin my be a problem in konsole.

I did/do have a problem with Dolphin when closing multiple tabs. The popup notification will hang the whole thing.
I thought it was when I had a search in a tab but then I can't make it do it, so I don't know but it hasn't done it in a while.
If I track it down any better I'll post it.

Re: Mageia 6 Plasma Dolphin crash

PostPosted: Jul 26th, '18, 22:09
by spring
Over the past weeks i have been making a point of NOT using the konsole F4 in Dolphin, and the processor takeover is rare now, but i am 99% convinced it's indeed Konsole that does this when used in Dolphin. I also think Dolphin has issues with SMB drives, forgetting, or asking for a password when there is none and so on, but really very sure Konsole use in Dolphin causes the processor takeover..

Re: Mageia 6 Plasma Dolphin crash

PostPosted: Jul 27th, '18, 11:47
by wintpe
thats a great observation, as ive watched out for this issue, and never once realized that you used konsole in dolphin.

ive been watching my separate konsole instances and never once seen this issue.

im not sure what the benefit is of using konsole inside dolphin, so perhaps you can help with that.

regards peter

Re: Mageia 6 Plasma Dolphin crash

PostPosted: Dec 10th, '18, 04:48
by yankee495
I was having all kinds of problems but couldn't solve or even repeat them. They seemed to come and go which meant they never really quit. One was when I closed Konsole I'd have a CPU stuck at 100% and Dolphin did it sometimes, too. I had a flickering desktop when two windows were opened on top of each other after resuming from suspend. Before sleep, it was ok and restarting kwin_x11 fixed it. I used a small script on the desktop and just double clicked it after waking it up. This was better than logging out and back in.

Code: Select all
#!/bin/bash
/usr/bin/kwin_x11 --replace &


I removed my Nvidia GTX 760 and installed an AMD RX 580 and everything is fixed. I don't know how a Nvidia driver causes a stuck core when closing Konsole, but it sure appears changing the card fixed it. I haven't had a problem in a few days and this includes in Mageia 6 and Suse Tumbleweed. Tumbleweed hasn't been updated in months, it's for testing and working on Mageia if I break it. In Tumbleweed I removed the Nvidia driver and installed the open source driver, AMDGPU, and then over wrote xorg.conf with xorg.conf.install which was created at initial install. When I was able to boot into Tumbleweed, I double checked and everything seemed to be ok and I still didn't update it.

Mageia was much less trouble to get going. I removed the Nvidia driver and shutdown then changed the card and rebooted and it detected the new card and just worked. I gave you the driver details to point out that I didn't change anything that wasn't driver related and it fixed everything on both distros, so Nvidia is causing serious problems. I was using whatever the current Nvidia driver was in Mageia 6, nothing custom or anything. I hope this helps some of you.