From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100306] System randomly freezes or crashes to the login screen, glitches until rebooted
Date: Thu, 03 Aug 2017 13:18:47 +0000 [thread overview]
Message-ID: <bug-100306-502-G0rQfO0bhw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100306-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1022 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100306
--- Comment #34 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
Today I discovered that even when not toggling desktop effects at runtime, the
freeze can still be mined into the system. I got a crash after 1 day of uptime,
no toggling of desktop compositing required.
I find it remarkable how the cause of the crash appears to have immediately
changed after me making the comment above yesterday; I tested my theory that
desktop effects are the root for 2 months, yet the moment I publish my
observations the behavior changes in less than a day. This further makes me
concerned that someone might be deliberately programming this crash using
vulnerabilities in system components, solely for how strange this coincidence
is. I'm still waiting for the developers to help investigate this further
whatever the case, as I cannot find any explanation at this point.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1904 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-08-03 13:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-100306-502@http.bugs.freedesktop.org/>
2017-03-22 2:16 ` [Bug 100306] System randomly freezes or crashes to the login screen, glitches until rebooted bugzilla-daemon
2017-03-29 19:43 ` bugzilla-daemon
2017-04-02 15:04 ` bugzilla-daemon
2017-04-06 2:45 ` bugzilla-daemon
2017-04-06 11:51 ` bugzilla-daemon
2017-04-07 0:01 ` bugzilla-daemon
2017-04-07 0:35 ` bugzilla-daemon
2017-04-11 5:13 ` bugzilla-daemon
2017-04-14 14:01 ` bugzilla-daemon
2017-04-18 1:31 ` bugzilla-daemon
2017-04-20 13:23 ` bugzilla-daemon
2017-05-09 22:17 ` bugzilla-daemon
2017-05-19 12:58 ` bugzilla-daemon
2017-05-19 13:10 ` bugzilla-daemon
2017-05-19 13:37 ` bugzilla-daemon
2017-05-21 11:30 ` bugzilla-daemon
2017-05-23 20:18 ` bugzilla-daemon
2017-05-23 21:54 ` bugzilla-daemon
2017-05-29 20:42 ` bugzilla-daemon
2017-06-07 21:04 ` bugzilla-daemon
2017-06-08 23:44 ` bugzilla-daemon
2017-06-18 18:59 ` bugzilla-daemon
2017-07-05 13:14 ` bugzilla-daemon
2017-07-05 18:21 ` bugzilla-daemon
2017-08-02 13:31 ` bugzilla-daemon
2017-08-03 13:18 ` bugzilla-daemon [this message]
2017-08-04 12:32 ` bugzilla-daemon
2017-08-05 12:24 ` bugzilla-daemon
2017-08-05 13:31 ` bugzilla-daemon
2017-08-07 20:52 ` bugzilla-daemon
2017-08-07 21:30 ` bugzilla-daemon
2017-08-07 21:31 ` bugzilla-daemon
2017-08-07 21:35 ` bugzilla-daemon
2017-08-31 18:17 ` bugzilla-daemon
2017-08-31 18:38 ` bugzilla-daemon
2017-11-12 15:04 ` bugzilla-daemon
2019-09-25 17:58 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-100306-502-G0rQfO0bhw@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox