Alex Goins writes:
> Adding Keith, as this is a regression that completely breaks PRIME Sync
> configs
> at top of tree.
Adam asked me to look at this last week, and I'm afraid I've not had a
chance as I've been traveling. Thanks for the reminder. Reading through
the
Adding Keith, as this is a regression that completely breaks PRIME Sync configs
at top of tree.
Thanks,
Alex
On Fri, 20 Oct 2017, Alex Goins wrote:
> Change 677c32bc refactored all usages of drmWaitVBlank() into a helper
> function,
> ms_queue_vblank().
>
> ms_queue_vblank() takes in an
Here is an updated version of the spec based on the recent feedback, also
including a couple new issues that came up.
Diff is followed by full text.
Thanks,
Alex
diff --git a/deepcolorproto.txt b/deepcolorproto.txt
index 7406762..87fbf2d 100644
--- a/deepcolorproto.txt
+++ b/deepcolorproto.txt
On Thu, 2017-10-26 at 19:15 +0300, Evgeny Zubok wrote:
> Adam Jackson writes:
>
> > Such a function does not exist. As far as the protocol is concerned,
> > screens do not have any relative geometry.
>
> Can the pointer barriers which were introduced in X Fixes extention
> serve
Adam Jackson writes:
> On Sat, 2017-10-21 at 13:08 -0700, Jim Westfall wrote:
>
>> I'm wanting to determine when the mouse pointer is near the edge of the X
>> Display.
>>
>> In the case when there is only one X screen, the edge of the X screen
>> will be the edge of the X
Hello Oliver,
I will do that later, but I should have provided more background. This
actually occurs if I open and close my laptop a couple of times in a
short period of time. I originally did that while experimenting to see
what would make GNOME Shell recognise my external monitor, and
Actually the problem I'm having with Motif is getting the managing,
mapping and realizing right.
This version is working as far as it goes in realizing etc. I start a
window, put on a notebook, the a rowcol, then a drawingarea at the
top. The drawing area should be about the top 1/3 of the
Hi,
Could you please post a backtrace, breaking on xwl_log_handler() ?
Another interesting data to capture would be the WAYLAND_DEBUG logs
(between Xwayland and gnome-shell)
wl_registry_bind() occurs when actually binding to an interface, which in
the case of wl_output occurs when adding a new
Hello,
Reporting this here in case it is of interest. I have been debugging
regular desktop crashes on my new Ubuntu 17.10 systems. One of them
seems to happen when Xwayland FatalError-s out because a Wayland output
disappears. I have only investigated this so far, but hopefully this
will be