From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 100306] System randomly freezes or crashes to the login screen,
glitches until rebooted
Date: Wed, 02 Aug 2017 13:31:04 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1131260423=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[IPv6:2610:10:20:722:a800:ff:fe98:4b55])
by gabe.freedesktop.org (Postfix) with ESMTP id E3F506F141
for ; Wed, 2 Aug 2017 13:31:03 +0000 (UTC)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1131260423==
Content-Type: multipart/alternative; boundary="15016806631.604eC5cA.6004";
charset="UTF-8"
--15016806631.604eC5cA.6004
Date: Wed, 2 Aug 2017 13:31:03 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D100306
--- Comment #33 from MirceaKitsune -=
--
After months of careful testing and experimentation, I have discovered what
seems to be the primary trigger of this freeze at last. It's not what trigg=
ers
it per say, but what "rigs" the system and causes it to crash within the co=
urse
of the next hours... the actual trigger is alt-tab switching between window=
s,
or certain desktop effects playing.
The freeze is mined into the system when you disable and re-enable KDE desk=
top
compositing. If I hit Alt + Shift + F12 to turn off desktop effects, then h=
it
the key combo to turn them back on... there is a great chance that within a=
few
hours the crash occurs. If I don't toggle compositing on the run and just l=
eave
it enabled after the system has started, I seem to be fine... this only hap=
pens
if I turn it off and back on during runtime. It's uncertain whether anything
else mines the system, but this is almost always what seems to do it for me.
Notice: I use OpenGL 3.1 for desktop compositing. I remember selecting Open=
GL
2.0 long ago, but that still caused the freeze at that time. I can't use
Xrender on a daily basis as many effects don't work with it. No other
compositor options seem to affect the problem either.
It would be highly appreciated if at least after this information, the
developers and maintainers could finally look at this issue! It has taken me
months to confirm this as a cause, and I really hope this information
(alongside dozens of comments and logs I have posted) can finally be put to
use.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15016806631.604eC5cA.6004
Date: Wed, 2 Aug 2017 13:31:03 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Comme=
nt # 33
on bug 10030=
6
from MirceaKitsune=
span>
After months of careful testing and experimentation, I have di=
scovered what
seems to be the primary trigger of this freeze at last. It's not what trigg=
ers
it per say, but what "rigs" the system and causes it to crash wit=
hin the course
of the next hours... the actual trigger is alt-tab switching between window=
s,
or certain desktop effects playing.
The freeze is mined into the system when you disable and re-enable KDE desk=
top
compositing. If I hit Alt + Shift + F12 to turn off desktop effects, then h=
it
the key combo to turn them back on... there is a great chance that within a=
few
hours the crash occurs. If I don't toggle compositing on the run and just l=
eave
it enabled after the system has started, I seem to be fine... this only hap=
pens
if I turn it off and back on during runtime. It's uncertain whether anything
else mines the system, but this is almost always what seems to do it for me.
Notice: I use OpenGL 3.1 for desktop compositing. I remember selecting Open=
GL
2.0 long ago, but that still caused the freeze at that time. I can't use
Xrender on a daily basis as many effects don't work with it. No other
compositor options seem to affect the problem either.
It would be highly appreciated if at least after this information, the
developers and maintainers could finally look at this issue! It has taken me
months to confirm this as a cause, and I really hope this information
(alongside dozens of comments and logs I have posted) can finally be put to
use.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15016806631.604eC5cA.6004--
--===============1131260423==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1131260423==--