> What's worse is that in the client side, there is no way to tell what failed.
> System calls can be traced to see their return values, and X11 error events
> exist, but Wayland has neither unless you disconnect the client.
For debug purposes, there are the compositor logs (and any other loggin
This is the RC1 release for Wayland 1.24.
Aside from the usual bug fixes and protocol clarifications, this new
release includes:
- A new wl_fixes interface to add a request to destroy a wl_registry
object.
- A new wl_keyboard.key repeated state, to allow compositors to take
over the responsib
Thanks for the feedback! It seems like everybody is on board for
skipping alphas/betas, so let's try that. We can always go back to the
old process later if we realize it was valuable.
Simon
On 2025-05-22 11:27, Pekka Paalanen wrote:
> On Thu, 22 May 2025 09:54:50 -0400
> Harry Wentland wrote:
>
>> On 2025-05-22 09:49, Simon Ser wrote:
>>> On Thursday, May 22nd, 2025 at 15:28, Harry Wentland
>>> wrote:
>>>
>> What we should
>> do is reject YCbCr-type buffers with the
On Thu, 22 May 2025 09:54:50 -0400
Harry Wentland wrote:
> On 2025-05-22 09:49, Simon Ser wrote:
> > On Thursday, May 22nd, 2025 at 15:28, Harry Wentland
> > wrote:
> >
> What we should
> do is reject YCbCr-type buffers with the color pipeline until we
> implement support for
On 2025-05-22 09:49, Simon Ser wrote:
> On Thursday, May 22nd, 2025 at 15:28, Harry Wentland
> wrote:
>
What we should
do is reject YCbCr-type buffers with the color pipeline until we
implement support for COLOR_ENCODING and COLOR_RANGE as a new
CSC colorop.
>>>
>>> Reject
On Thursday, May 22nd, 2025 at 15:28, Harry Wentland
wrote:
> > > What we should
> > > do is reject YCbCr-type buffers with the color pipeline until we
> > > implement support for COLOR_ENCODING and COLOR_RANGE as a new
> > > CSC colorop.
> >
> > Rejecting is fine, but is implementing COLOR_ENC
On 2025-05-22 03:57, Pekka Paalanen wrote:
> On Wed, 21 May 2025 15:48:00 -0400
> Harry Wentland wrote:
>
>> On 2025-05-17 07:51, Xaver Hugl wrote:
>>> Am Do., 15. Mai 2025 um 22:00 Uhr schrieb Leandro Ribeiro
>>> :
On 5/15/25 15:39, Daniel Stone wrote:
> Hi,
>
> -Original Message-
> From: Simon Ser
> Sent: Thursday, May 22, 2025 3:45 PM
> To: Harry Wentland
> Cc: Xaver Hugl ; Alex Hung ; dri-
> de...@lists.freedesktop.org; amd-...@lists.freedesktop.org; wayland-
> de...@lists.freedesktop.org; leo@amd.com; ville.syrj...@linux.intel.com;
>
> -Original Message-
> From: wayland-devel On Behalf
> Of Simon Ser
> Sent: Tuesday, April 15, 2025 9:55 PM
> To: Harry Wentland
> Cc: Shankar, Uma ; Alex Hung ;
> dri-de...@lists.freedesktop.org; amd-...@lists.freedesktop.org; intel-
> g...@lists.freedesktop.org; wayland-devel@lists.fr
On Wednesday, May 21st, 2025 at 21:18, Harry Wentland
wrote:
> On 2025-05-20 16:13, Harry Wentland wrote:
>
> > On 2025-05-19 19:43, Simon Ser wrote:
> >
> > > On Sunday, May 18th, 2025 at 00:32, Xaver Hugl xaver.h...@gmail.com wrote:
> > >
> > > > > We can always make the property mutable on
On Wed, 21 May 2025 11:49:34 +0200
Jonas Ådahl wrote:
> On Wed, May 21, 2025 at 05:43:09AM -0400, Neal Gompa wrote:
> > On Tue, May 20, 2025 at 4:03 PM Simon Ser wrote:
> > >
> > > I would suggest to drop the alphas/betas from the release process, ie.
> > > go straight to RC1. The process woul
On Tue, 20 May 2025 19:11:06 +
"Sloane, Brandon" wrote:
> > -Original Message-
> > From: Pekka Paalanen
> > Sent: Tuesday, May 20, 2025 4:58 AM
> > To: Sloane, Brandon
> > Cc: wayland-devel@lists.freedesktop.org
> > Subject: Re: [RFC] Wayland Security Modules
> >
> > On Mon, 19 May
On Wed, 21 May 2025 15:48:00 -0400
Harry Wentland wrote:
> On 2025-05-17 07:51, Xaver Hugl wrote:
> > Am Do., 15. Mai 2025 um 22:00 Uhr schrieb Leandro Ribeiro
> > :
> >>
> >>
> >>
> >> On 5/15/25 15:39, Daniel Stone wrote:
> >>> Hi,
> >>>
> >>> On Thu, 15 May 2025 at 19:02, Harry Wentland
14 matches
Mail list logo
