One cause is known, see https://bugzilla.redhat.com/show_bug.cgi?id=1264486
-- Rex
________________________________________ From: kde-bounces@lists.fedoraproject.org kde-bounces@lists.fedoraproject.org on behalf of Glenn Holmer shadowm@lyonlabs.org Sent: Sunday, September 20, 2015 6:36 PM To: KDE on Fedora discussion Subject: Re: A near freeze of plasma
On 09/18/2015 06:49 PM, Ed Greshko wrote:
On 09/19/15 07:19, Ed Greshko wrote: The best way to get a "near freeze" is to tell everyone that you've not had one in at least a week. Seriously, less than one hour after writing this I got a "near freeze" and was able to confirm that "killall -9 drkonqi" got me going again.
I've reached my limit with the Plasma 5 freezes. Speaking to users who've tried alpha builds: do you think there's any hope of this situation improving in Fedora 23? I see we're scheduled for a beta this week. If the cause of the freezes hasn't been found yet, I'll start making other plans for this machine.
-- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe." _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Rex Dieter wrote:
One cause is known, see https://bugzilla.redhat.com/show_bug.cgi?id=1264486
Well, that's the proximate cause, but the root cause is still unknown (or it'd be fixed by now): Why does DrKonqi hang up that way?
Kevin Kofler
On 2015-09-21 02:32, Kevin Kofler wrote:
Rex Dieter wrote:
One cause is known, see https://bugzilla.redhat.com/show_bug.cgi?id=1264486
Well, that's the proximate cause, but the root cause is still unknown (or it'd be fixed by now): Why does DrKonqi hang up that way?
Kevin Kofler
_______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
This is the response that I received for the bug I submitted for kwin.
https://bugs.kde.org/show_bug.cgi?id=353428
The process "freeze" is a bug in DrKonqui, the kwin process isn't frozen but sigstop'ped (there was a comment in some kwin bug indicating this happens) sending the KWin process a SIGCONT will continue (and kill) it. (Stopping is required by drkonqi to conditionally obtain the backtrace)
So it looks like it is doing what it is supposed to do but just doesn't do it properly.
Robin