From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100289] 'flip queue failed in radeon_scanout_flip: Invalid argument' error and small frame buffer allocated on turning off and on new monitor
Date: Sun, 04 Feb 2018 18:58:05 +0000 [thread overview]
Message-ID: <bug-100289-502-wprkaTBzGZ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100289-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 813 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100289
--- Comment #15 from OmegaPhil@startmail.com ---
After being able to identify xfsettingsd as a potential cause (ignoring whether
or not the monitor was actually Disconnected/Connected), I had a look at its
bug tracker - and https://bugzilla.xfce.org/show_bug.cgi?id=14096 looks
extremely suspicious - after applying the patch and turning on/off the monitor
10 times in a row (waiting 10 seconds inbetween), I haven't had a single
desktop reconfiguration (the patch makes complete sense too WRT this problem),
so I'm going to sit on this for a week to make sure its actually solved.
There seem to be a number of other people complaining of this issue over there
too...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1815 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-02-04 18:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 17:59 [Bug 100289] 'flip queue failed in radeon_scanout_flip: Invalid argument' error and small frame buffer allocated on turning off and on new monitor bugzilla-daemon
2017-03-22 9:19 ` bugzilla-daemon
2017-03-22 9:30 ` bugzilla-daemon
2017-03-22 19:46 ` bugzilla-daemon
2017-03-23 9:30 ` bugzilla-daemon
2017-03-23 15:49 ` bugzilla-daemon
2017-03-23 19:45 ` bugzilla-daemon
2017-03-23 19:47 ` bugzilla-daemon
2017-03-24 18:58 ` bugzilla-daemon
2017-04-19 6:34 ` bugzilla-daemon
2017-06-26 19:39 ` bugzilla-daemon
2017-06-26 20:13 ` bugzilla-daemon
2017-06-27 16:19 ` bugzilla-daemon
2017-07-21 19:39 ` bugzilla-daemon
2017-07-22 14:24 ` bugzilla-daemon
2018-02-04 18:24 ` bugzilla-daemon
2018-02-04 18:58 ` bugzilla-daemon [this message]
2018-03-09 17:26 ` bugzilla-daemon
2018-03-09 17:35 ` bugzilla-daemon
2018-03-10 11:43 ` bugzilla-daemon
2019-11-19 9:26 ` 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-100289-502-wprkaTBzGZ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.