similar to: Is wine portable to other windowing system?

> On 30/10/2023, at 8:38 AM, Dirk Eddelbuettel <edd at debian.org> wrote: > > > On 30 October 2023 at 07:54, Paul Murrell wrote: > | I am unaware of any Wayland display support. > | > | One useful way forward would be an R package that provides such a device > | (along the lines of 'Cairo', 'tikzDevice', et al) > > As I understand it, it is

On 29/10/2023 4:20 p.m., Simon Urbanek wrote: > > >> On 30/10/2023, at 8:38 AM, Dirk Eddelbuettel <edd at debian.org> wrote: >> >> >> On 30 October 2023 at 07:54, Paul Murrell wrote: >> | I am unaware of any Wayland display support. >> | >> | One useful way forward would be an R package that provides such a device >> | (along the lines

On 30 October 2023 at 09:20, Simon Urbanek wrote: | > On 30/10/2023, at 8:38 AM, Dirk Eddelbuettel <edd at debian.org> wrote: | > On 30 October 2023 at 07:54, Paul Murrell wrote: | > | I am unaware of any Wayland display support. | > | | > | One useful way forward would be an R package that provides such a device | > | (along the lines of 'Cairo',

On 30 October 2023 at 07:54, Paul Murrell wrote: | I am unaware of any Wayland display support. | | One useful way forward would be an R package that provides such a device | (along the lines of 'Cairo', 'tikzDevice', et al) As I understand it, it is a protocol, and not a device. Several Linux distributions have long defaulted to it, so we already should have thousands of

Hi I am unaware of any Wayland display support. One useful way forward would be an R package that provides such a device (along the lines of 'Cairo', 'tikzDevice', et al) Paul On 27/10/23 23:16, quentin.thorne via R-devel wrote: > Hello, > > I'm interested in understanding the current state of Wayland display > support in R plot, and I was wondering if any

On 29-10-2023 22:29, Dirk Eddelbuettel wrote: > On 30 October 2023 at 09:20, Simon Urbanek wrote: > | > On 30/10/2023, at 8:38 AM, Dirk Eddelbuettel<edd at debian.org> wrote: > | > On 30 October 2023 at 07:54, Paul Murrell wrote: > | > | I am unaware of any Wayland display support. > | > | > | > | One useful way forward would be an R package that provides

El lun., 30 oct. 2023 12:26, Roger Bivand <Roger.Bivand at nhh.no> escribi?: > I also noticed this: > > https://www.theregister.com/2023/10/13/gnome_proposes_dropping_x11/ > > which is concerning. Until now, I've retained X11 on Fedora because of > difficulties in screen sharing via zoom in Wayland sessions. > KDE Plasma user here. FWIW, I've been using Wayland

Hi, > > Hmm? I'm assuming the wayland client (in the guest) talks to the > > wayland proxy, using the wayland protocol, like it would talk to a > > wayland display server. Buffers must be passed from client to > > server/proxy somehow, probably using fd passing, so where is the > > problem? > > > > Or did I misunderstand the role of the proxy? >

Hi, > > Hmm? I'm assuming the wayland client (in the guest) talks to the > > wayland proxy, using the wayland protocol, like it would talk to a > > wayland display server. Buffers must be passed from client to > > server/proxy somehow, probably using fd passing, so where is the > > problem? > > > > Or did I misunderstand the role of the proxy? >

On Mon, Feb 05, 2018 at 03:46:17PM +0100, Tomeu Vizoso wrote: > On 02/05/2018 01:20 PM, Gerd Hoffmann wrote: > > Hi, > > > > > > Why not use virtio-vsock to run the wayland protocol? I don't like > > > > the idea to duplicate something with very simliar functionality in > > > > virtio-gpu. > > > > > > The reason for

On Mon, Feb 05, 2018 at 03:46:17PM +0100, Tomeu Vizoso wrote: > On 02/05/2018 01:20 PM, Gerd Hoffmann wrote: > > Hi, > > > > > > Why not use virtio-vsock to run the wayland protocol? I don't like > > > > the idea to duplicate something with very simliar functionality in > > > > virtio-gpu. > > > > > > The reason for

https://bugs.freedesktop.org/show_bug.cgi?id=48074 Bug #: 48074 Summary: 3D / OpenGL clients used with wayland always cause an immediate hang Classification: Unclassified Product: Mesa Version: 8.0 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=99400 Bug ID: 99400 Summary: [nouveau] garbled rending with glamor on G71 Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

Hi Gerd and Stefan, can we reach agreement on whether vsock should be involved in this? Thanks, Tomeu On 02/07/2018 10:49 AM, Tomeu Vizoso wrote: > On 02/06/2018 03:23 PM, Gerd Hoffmann wrote: >> ?? Hi, >> >>>> Hmm?? I'm assuming the wayland client (in the guest) talks to the >>>> wayland proxy, using the wayland protocol, like it would talk to a

Hi Gerd and Stefan, can we reach agreement on whether vsock should be involved in this? Thanks, Tomeu On 02/07/2018 10:49 AM, Tomeu Vizoso wrote: > On 02/06/2018 03:23 PM, Gerd Hoffmann wrote: >> ?? Hi, >> >>>> Hmm?? I'm assuming the wayland client (in the guest) talks to the >>>> wayland proxy, using the wayland protocol, like it would talk to a

https://bugzilla.mindrot.org/show_bug.cgi?id=2552 Bug ID: 2552 Summary: ssh -X and "ForwardX11Trusted no" break most applications, distros turn on "ForwardX11Trusted yes" Product: Portable OpenSSH Version: 7.2p1 Hardware: All OS: All Status: NEW Severity:

https://bugs.freedesktop.org/show_bug.cgi?id=109341 Bug ID: 109341 Summary: Plasma Wayland locks up immediately on sign in Product: Mesa Version: 18.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: Drivers/DRI/nouveau

Hello, I'm interested in understanding the current state of Wayland display support in R plot, and I was wondering if any progress or discussions have taken place regarding this matter. As Wayland continues to gain popularity as a display protocol on modern Linux systems, having Wayland support for R's plotting capabilities would be a significant enhancement. Could anyone provide

Hi, > > (a) software rendering: client allocates shared memory buffer, renders > > into it, then passes a file handle for that shmem block together > > with some meta data (size, format, ...) to the wayland server. > > > > (b) gpu rendering: client opens a render node, allocates a buffer, > > asks the cpu to renders into it, exports

Hi, > > (a) software rendering: client allocates shared memory buffer, renders > > into it, then passes a file handle for that shmem block together > > with some meta data (size, format, ...) to the wayland server. > > > > (b) gpu rendering: client opens a render node, allocates a buffer, > > asks the cpu to renders into it, exports