From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109001] Freezes when waking up after screen goes blank.
Date: Tue, 11 Dec 2018 20:53:54 +0000 [thread overview]
Message-ID: <bug-109001-502-CkiCkby5vb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109001-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 518 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109001
--- Comment #6 from fin4478@hotmail.com ---
Comment on attachment 142770
--> https://bugs.freedesktop.org/attachment.cgi?id=142770
Xorg Log
Disable the Xfce compositor, vsync feature in that causes it tainted. That
might not help. Use the display port, development focus is in the display
port. Developers have display monitors and are not interested about hdmi so
much.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1397 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:[~2018-12-11 20:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 14:46 [Bug 109001] Freezes when waking up after screen goes blank bugzilla-daemon
2018-12-10 14:47 ` bugzilla-daemon
2018-12-10 14:49 ` bugzilla-daemon
2018-12-10 15:24 ` bugzilla-daemon
2018-12-10 15:26 ` bugzilla-daemon
2018-12-10 15:30 ` bugzilla-daemon
2018-12-10 16:35 ` bugzilla-daemon
2018-12-11 5:20 ` bugzilla-daemon
2018-12-11 20:53 ` bugzilla-daemon [this message]
2018-12-12 16:01 ` bugzilla-daemon
2018-12-12 16:12 ` bugzilla-daemon
2018-12-31 0:18 ` bugzilla-daemon
2019-01-02 9:18 ` bugzilla-daemon
2019-01-03 11:35 ` bugzilla-daemon
2019-01-04 7:50 ` bugzilla-daemon
2019-01-05 3:00 ` bugzilla-daemon
2019-01-05 15:57 ` bugzilla-daemon
2019-11-19 9:07 ` 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-109001-502-CkiCkby5vb@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