similar to: NemoShell

Greetings! I'm currently gathering information that helps software in assessing the user's context. One very important such data would be the application that the user is currently working with which mostly is roughly equivalent to the name of the window that has the focus. Unfortunately I'm at a loss even about which API to ask for this information. As personally I am using compiz as

Hi Rowland, > Remove 'map untrusted to domain = Yes', it has been removed. > > Add 'domain logons = Yes' > > This gets it back to being a PDC: thanks for the hints! I did that, but it doesn't help. I guess the problem is not on the PDC server but on SERVER2. That's the one that got upgraded and stopped working (even with the non-pdc config of SERVER1). I

Rowland penny via samba wrote: > So your server doesn't seem to be able to find winbindd, are you sure it > is running ? > > What does this show: > > ps ax | grep '[w]inbind' > > What OS is this ? It's SuSE Linux Enterprise 15sp1. winbindd is definitely running, I showed that in the first mail in the output of "rcwinbind status", there you can

Hi Rowland, thanks for all your input! Rowland penny via samba wrote: > Could it be Selinux or Apparmor (not sure which SLES uses) stopping smbd > contacting winbindd ? No, none of these is running on our systems. > Could the SLES Samba packages be wrong ? Yes, that's a possibility. I opened a SR with SUSE support, but they usually take some time to analyse and propose a

X.Org/Wayland Security Advisory: June 10th, 2015 - CVE-2015-3164 Unauthorised local client access in XWayland ============================================ Description: ============ Ray Strode, a developer at Red Hat, discovered an authentication setup issue inside the XWayland compatibility server, used to host X11 clients inside a Wayland compositor's session. XWayland is used by Weston and

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

> 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 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 >>> wayland display server. Buffers must be passed from client to >>> server/proxy somehow, probably using fd passing, so where is the >>>

On 02/05/2018 05:03 PM, Gerd Hoffmann wrote: > 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 >>>>>

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

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

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

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

On 02/12/2018 12:45 PM, Gerd Hoffmann wrote: > 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,

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

On Thu, Dec 06, 2018 at 09:39:54AM -0500, Frediano Ziglio wrote: > > > > On Thu, Dec 06, 2018 at 05:55:58AM -0500, Frediano Ziglio wrote: > > > > > > > qxl surfaces (used for framebuffers and gem objects) can live in both > > > > VRAM and PRIV ttm domains. Update placement setup to include both. Put > > > > PRIV first in the list so it

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