I observe that on intel + nvidia system booted with nvidia_drm.modeset=0
(intel is primary), vulkan apps such as vkcube running on nvidia gpu
present over Xwayland on xcb wsi. In this setup however swapchain fails
on wayland wsi. This is also indicated by
`vkGetPhysicalDeviceSurfaceSupportKHR
Ok Thank's Olivier!
Kind Regards
Il giorno mer 26 mar 2025 alle ore 10:04 Olivier Fourdan
ha scritto:
>
> Hi
>
> On Wed, Mar 26, 2025 at 9:52 AM Ivan Linty wrote:
>>
>> Hello everyone
>> I signed up to this mailing list because I would like to report a bug
Hi
On Wed, Mar 26, 2025 at 9:52 AM Ivan Linty wrote:
> Hello everyone
> I signed up to this mailing list because I would like to report a bug
> I found on xwayland. Am I in the right place?
Xwayland being an xserver, the best place to report an issue with Xwayland
is to file it
Hello everyone
I signed up to this mailing list because I would like to report a bug
I found on xwayland. Am I in the right place?
Hi all
In preparation for the forthcoming Xwayland 24.1.0 release, I've now
created the xwayland-24.1 branch:
https://gitlab.freedesktop.org/xorg/xserver/-/tree/xwayland-24.1
And there's also a milestone that can be used to tag issues and merge
requests targeting Xwayland 24.
Hi all,
I am pleased to announce xwayland-run version 0.0.3
xwayland-run contains a set of small utilities revolving around running
Xwayland
and various Wayland compositors headless.
Most noticeable change in this release is the addition of kwin as a
supported Wayland compositor.
Leif Liddy (1
Hi Pekka,
On Wed, 29 Nov 2023 at 15:02, Pekka Paalanen wrote:
> On Wed, 29 Nov 2023 10:10:05 +0100
> Olivier Fourdan wrote:
> > * xwayland-run, to spawn an X11 client within its own dedicated Xwayland
> > rootful instance,
>
> wouldn't this one be at home in t
ble to elaborate on the rationale behind your
> opinion, is that because there is no interest at all, because of the quality
> of the code, because of Python, or because it's partly about Xwayland and X11?
To me the main downside is that this project has a hardcoded list of
compositors. I
related Xservers in RHEL [1],
> except Xwayland, there was a need for a replacement utility that would work
> like xvfb-run, but without Xvfb :)
>
> The idea is to run Xwayland rootful within a Wayland compositor headless as
> a replacement for Xvfb. The problem though is that I didn
all related Xservers in RHEL [1], except
> Xwayland, there was a need for a replacement utility that would work like
> xvfb-run, but without Xvfb :)
>
> The idea is to run Xwayland rootful within a Wayland compositor headless as a
> replacement for Xvfb. The problem though is that I di
ate on the rationale behind your
opinion, is that because there is no interest at all, because of the
quality of the code, because of Python, or because it's partly about
Xwayland and X11?
I understand it may not be suitable as a project of its own within the
Wayland space, but couldn'
nale behind your
opinion, is that because there is no interest at all, because of the
quality of the code, because of Python, or because it's partly about
Xwayland and X11?
I understand it may not be suitable as a project of its own within the
Wayland space, but couldn't we consider adding
-plans-wayland-and-xorg-server?channel=/en/blog/channel/red-hat-enterprise-linux>
[2] https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1197
[3] https://gitlab.freedesktop.org/xorg/xserver/-/issues/1595
[4] https://gitlab.freedesktop.org/ofourdan/xwayland-run
--
Martin Stransky
Software Engineer / Red Hat, Inc
On Wednesday, November 29th, 2023 at 10:10, Olivier Fourdan
wrote:
> So my question is, if there is any interest for such a project [4], should
> this be moved to the wayland namespace in gitlab (we could even change the
> name of the project), should that be added to the existing "wayland-utili
Hi all,
In Fedora and Red Hat Enterprise Linux, we ship a small shell script called
"xvfb-run" originating from Debian to launch an X11 client within Xvfb.
With the future removal of Xorg and all related Xservers in RHEL [1],
except Xwayland, there was a need for a replacement utility
Hi,
I think a fix for https://gitlab.freedesktop.org/xorg/xserver/-/issues/946 is
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1130.
Thanks,
Russell
e display, there just is
>>> none. I don't know how Xwayland reacts to that, and how that Java suite
>>> reacts to what Xwayland does. Those would be something to look into, if
>>> Weston upgrade does not help.
>> Yes, it must be XWayland. Maybe there is any conf
s. And I need to cross-compile Weston then,
> > which is maybe challenging?
> >
> > I can try to compile on device and test. But which dependencies also
> > need to be compiled then? XWayland? Wayland? Libraries?
> >
> >>
> >> FWIW, when you unplug the last
for several reasons. And I need to cross-compile Weston then,
which is maybe challenging?
I can try to compile on device and test. But which dependencies also
need to be compiled then? XWayland? Wayland? Libraries?
FWIW, when you unplug the last display, leaving none, then there is no
On Thu, 8 Jun 2023 at 16:54, Martin Petzold wrote:
> Am 08.06.23 um 16:58 schrieb Daniel Stone:
>
> On Thu, 8 Jun 2023 at 14:28, Pekka Paalanen wrote:
>
>> On Thu, 8 Jun 2023 14:49:37 +0200
>> Martin Petzold wrote:
>> > btw. we are using a Weston 9 package from NXP and there may be
>> important
Am 08.06.23 um 16:58 schrieb Daniel Stone:
Hi,
On Thu, 8 Jun 2023 at 14:28, Pekka Paalanen wrote:
On Thu, 8 Jun 2023 14:49:37 +0200
Martin Petzold wrote:
> btw. we are using a Weston 9 package from NXP and there may be
important
> fixes for our i.MX8 platform in there.
Hi,
On Thu, 8 Jun 2023 at 14:28, Pekka Paalanen wrote:
> On Thu, 8 Jun 2023 14:49:37 +0200
> Martin Petzold wrote:
> > btw. we are using a Weston 9 package from NXP and there may be important
> > fixes for our i.MX8 platform in there.
>
> Oh. We cannot support modified Weston, sorry. Significan
And I need to cross-compile Weston then,
> > which is maybe challenging?
Upstream Weston has very little to no dependencies on kernel version.
> >
> > I can try to compile on device and test. But which dependencies also
> > need to be compiled then? XWayland? Wayland? Librar
for several reasons. And I need to cross-compile Weston then,
which is maybe challenging?
I can try to compile on device and test. But which dependencies also
need to be compiled then? XWayland? Wayland? Libraries?
btw. we are using a Weston 9 package from NXP and there may be important
-compile Weston then,
which is maybe challenging?
I can try to compile on device and test. But which dependencies also
need to be compiled then? XWayland? Wayland? Libraries?
FWIW, when you unplug the last display, leaving none, then there is no
display area. Weston does not pretend a fake
lug the last display, leaving none, then there is no
display area. Weston does not pretend a fake display, there just is
none. I don't know how Xwayland reacts to that, and how that Java suite
reacts to what Xwayland does. Those would be something to look into, if
Weston upgrade does
2023 at 10:25:28PM +0200, Martin Petzold wrote:
I guess I have an issue with XWayland (but maybe Weston / Linux). It is very
specific and I kindly ask for help.
I have a Java application running on:
XWayland 2:1.20.11-1+deb11u6, Weston 9.0.0-1, OpenJDK 11.0.18+10-1~deb11u1,
Debian 11, Kernel 5
10:25:28PM +0200, Martin Petzold wrote:
> I guess I have an issue with XWayland (but maybe Weston / Linux). It is very
> specific and I kindly ask for help.
>
> I have a Java application running on:
>
> XWayland 2:1.20.11-1+deb11u6, Weston 9.0.0-1, OpenJDK 11.0.18+10-1~deb11u1,
I guess I have an issue with XWayland (but maybe Weston / Linux). It is
very specific and I kindly ask for help.
I have a Java application running on:
XWayland 2:1.20.11-1+deb11u6, Weston 9.0.0-1, OpenJDK
11.0.18+10-1~deb11u1, Debian 11, Kernel 5.10.52
My JFrame (Window) is set to
Hi Daniel,
El vie, 6 ago 2021 a las 11:57, Daniel Stone ()
escribió:
> Hi Guillermo,
>
> On Fri, 6 Aug 2021 at 10:44, Guillermo Rodriguez Garcia
> wrote:
> > El vie, 6 ago 2021 a las 10:14, Daniel Stone ()
> escribió:
> >> kiosk-shell is something we have in newer versions of Weston which
> >> s
Gil Peyrot<mailto:linkma...@linkmauve.fr>;
wayland-devel@lists.freedesktop.org<mailto:wayland-devel@lists.freedesktop.org>
Subject: Re: FW: xrandr and xwayland
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the
sktop.org<mailto:wayland-devel@lists.freedesktop.org>
Subject: Re: FW: xrandr and xwayland
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
Hi David,
On Thu, 5
@tireprofiles.com>
Cc: Emmanuel Gil Peyrot<mailto:linkma...@linkmauve.fr>;
wayland-devel@lists.freedesktop.org<mailto:wayland-devel@lists.freedesktop.org>
Subject: Re: FW: xrandr and xwayland
CAUTION: This email originated from outside of the organization. Do not click
links or open
Hi Guillermo,
On Fri, 6 Aug 2021 at 10:44, Guillermo Rodriguez Garcia
wrote:
> El vie, 6 ago 2021 a las 10:14, Daniel Stone ()
> escribió:
>> kiosk-shell is something we have in newer versions of Weston which
>> sounds like it would work well for your usecases - it's designed to
>> just run a si
Hi Daniel,
El vie, 6 ago 2021 a las 10:14, Daniel Stone ()
escribió:
> kiosk-shell is something we have in newer versions of Weston which
> sounds like it would work well for your usecases - it's designed to
> just run a single application fullscreen. You might want to check out
> what we have in
Hi David,
On Thu, 5 Aug 2021 at 22:17, David Deyo wrote:
> > Sounds like you're missing wl_display_flush() in your client code, so the
> > requests don't make it to the socket buffer until they're forced to because
> > it's filled up.
>
> That did it. You guys are awesome. I don’t suppose the
Subject: Re: FW: xrandr and xwayland
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
On Thu, 5 Aug 2021 at 21:15, David Deyo
mailto:dd...@tireprofiles.com>> wrote:
I was
On Thu, 5 Aug 2021 at 21:15, David Deyo
mailto:dd...@tireprofiles.com>> wrote:
I was able to re-create the files of your patch and added them into my build
tree.
Not having an accelerometer, I’ve had to make a few changes.
When you said, ‘It had issues’, I am also seeing some issues.
I can ro
On Thu, 5 Aug 2021 at 21:15, David Deyo wrote:
> I was able to re-create the files of your patch and added them into my
> build tree.
>
>
>
> Not having an accelerometer, I’ve had to make a few changes.
>
> When you said, ‘It had issues’, I am also seeing some issues.
>
>
>
> I can rotate my scre
@tireprofiles.com>
Cc:
wayland-devel@lists.freedesktop.org<mailto:wayland-devel@lists.freedesktop.org>
Subject: Re: FW: xrandr and xwayland
Hi,
On Tue, Aug 03, 2021 at 01:04:11PM +, David Deyo wrote:
[…]
> I believe our compositor (Weston) can do it, transform=90, but to use this
Hi,
On Tue, Aug 03, 2021 at 01:04:11PM +, David Deyo wrote:
[…]
> I believe our compositor (Weston) can do it, transform=90, but to use this
> method, it has to be restarted; causing our gui app to crash and lose all
> entered data.
> The client probably needs to drive the orientation. Con
From: Carsten Haitzler<mailto:ras...@rasterman.com>
Sent: Tuesday, August 3, 2021 10:47 AM
To: David Deyo<mailto:dd...@tireprofiles.com>
Cc:
wayland-devel@lists.freedesktop.org<mailto:wayland-devel@lists.freedesktop.org>
Subject: Re: FW: xrandr and xwayland
CAUTION: This ema
vel@lists.freedesktop.org>
> Subject: Re: FW: xrandr and xwayland
>
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> On Tue, 3 Aug 2021
From: Carsten Haitzler<mailto:ras...@rasterman.com>
Sent: Tuesday, August 3, 2021 9:38 AM
To: David Deyo<mailto:dd...@tireprofiles.com>
Cc:
wayland-devel@lists.freedesktop.org<mailto:wayland-devel@lists.freedesktop.org>
Subject: Re: FW: xrandr and xwayland
CAUTION: This ema
freedesktop.org>
> Subject: Re: FW: xrandr and xwayland
>
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> On Tue, 3 Aug 2021 13:04:11 + Da
From: Carsten Haitzler<mailto:ras...@rasterman.com>
Sent: Tuesday, August 3, 2021 8:13 AM
To: David Deyo<mailto:dd...@tireprofiles.com>
Cc:
wayland-devel@lists.freedesktop.org<mailto:wayland-devel@lists.freedesktop.org>
Subject: Re: FW: xrandr and xwayland
CAUTION: This ema
On Tue, 3 Aug 2021 13:04:11 + David Deyo said:
>
>
> From: David Deyo<mailto:dd...@tireprofiles.com>
> Sent: Monday, August 2, 2021 3:53 PM
> To: Pekka Paalanen<mailto:ppaala...@gmail.com>
> Subject: RE: xrandr and xwayland
>
> On Fri, 30 Jul 2021 23:3
From: David Deyo<mailto:dd...@tireprofiles.com>
Sent: Monday, August 2, 2021 3:53 PM
To: Pekka Paalanen<mailto:ppaala...@gmail.com>
Subject: RE: xrandr and xwayland
On Fri, 30 Jul 2021 23:30:38 +0100
Carsten Haitzler wrote:
> On Fri, 30 Jul 2021 16:28:02 + David Deyo said
anywhere. While in theory a wayland compositor could create an
> extension
> that works like xrandr, it'd be problematic to make it general-access like
> xrandr.
Indeed.
> >
> > Hello everyone,
> >
> > I need to rotate my screen 90 degrees and back to
like xrandr, it'd be problematic to make it general-access like
xrandr.
>
> Hello everyone,
>
> I need to rotate my screen 90 degrees and back to normal in xwayland on an
> iMX8 running gatesgarth distro.
>
> Does anyone know if xrandr can be coerced/modified to make ro
Hello everyone,
I need to rotate my screen 90 degrees and back to normal in xwayland on an
iMX8 running gatesgarth distro.
Does anyone know if xrandr can be coerced/modified to make rotations work? I’m
in the middle of xserver, libX11, libxrandr and xrandr source.
How would a client
of the stack trace? There should be more. Please seek
guidance on debugging on your platform in general. You may need to make
sure weston is built with debug info and that the debug info is
available to the debugger.
I just tried xeyes on Weston master and it works here, but that doesn't
say mu
On Thu, 6 Feb 2020 10:51:22 +0530
"Devashish Tiwari" wrote:
> Hello,
>
> As we discussed previously, I have been trying to run X-clients on my
> Weston + Xwayland environment.
>
> I think I have come to a point where my Wayland succeeds in launching
> Xwaylan
Hello,
As we discussed previously, I have been trying to run X-clients on my Weston +
Xwayland environment.
I think I have come to a point where my Wayland succeeds in launching Xwayland,
i.e., I am able to get those three prints you mentioned in the trailing email.
When I run xeyes on my
On Tue, 27 Jun 2017 23:51:36 +0300
Ilia Bozhinov wrote:
> Currently the xwayland implementation of desktop surfaces doesn't do
> anything when weston_desktop_surface_set_maximized/fullscreen() is called.
> In order to support this, we have to add xwayland internal interfaces
>
l/usr/local/lib/dri/omapdrm_dri.so: cannot open shared
> object file: No such file or directory
> failed to load driver: omapdrm
Hi,
looks like you broke your graphics drivers installation at the same
time. Previously there were notes about gbm_pvr.so, not omapdrm. I
cannot even say what y
d in the
> trailing mail.
>
> Also note that, my $WAYLAND_DISPLAY variable is set to wayland-0 and
> $DISPLAY is set to :0. Is that alright?
Yes, they have absolutely nothing to do with each other.
>
> I am once again attaching my weston logs here for your analys
ght?
Yes, they have absolutely nothing to do with each other.
>
> I am once again attaching my weston logs here for your analysis.
> Please let me know how to get those three lines in the log, as in,
> how should I make Xwayland spawn as a separate pid.
>
> Right now I am
three lines in the log, as in, how should I make Xwayland
spawn as a separate pid.
Right now I am not getting any trace of Xwayland in "ps -ef" or anywhere else.
The only silver lining I see here is the log "xserver listening on display :0"
in weston.log
--
On Wed, 11 Dec 2019 14:07:50 +0530
"Devashish Tiwari" wrote:
> Hi,
>
> Thanks for your response.
>
> I am still not sure about how to run X-clients (xeyes, xcalc, xclock
> etc) on Weston running with xwayland module.
>
> I did:
>
> export DISPLAY=
Hi,
Thanks for your response.
I am still not sure about how to run X-clients (xeyes, xcalc, xclock etc) on
Weston running with xwayland module.
I did:
export DISPLAY=':0'
and tried to run Xclient. But I am getting the same error:
Error: Can't open display: :0
I don&#x
On Tue, 3 Dec 2019 12:26:59 +0530
"Devashish Tiwari" wrote:
> Hello,
>
> It seems like Weston with Xwayland is still not working for me.
> Despite of the positive xserver-related prints I get in weston.log
> file :
>
> ---
>
> [02:43:02.573]
Hello,
It seems like Weston with Xwayland is still not working for me. Despite of the
positive xserver-related prints I get in weston.log file :
---
[02:43:02.573] Loading module '/usr/lib/libweston-2/xwayland.so'
[02:43:02.587] Registered plugin API 'weston_xwayland
On Mon, 2 Dec 2019 13:53:24 +0530
"Devashish Tiwari" wrote:
> SDK version. But I was optimistic that Weston could be run with
> xwayland on this EVM. And after adding some final dependencies, I
> think it's good now. I have attached copied logs at the end of this
> em
has patched Weston and customized it with
--enable-xwayland=no
I have tried contacting to vendor several times regarding xwayland/X11 support,
but they don't entertain such requests/questions by claiming that they don't
support X11 in their current Linux
SDK version. But I was optim
e and EGL
> errors were gone.
>
> Next there was an error regarding /usr/lib/libweston-2/xwayland.so
> was missing. The weston provided in my linux-SDK by the vendor was
> not compiled with --enable-xwayland and therefore this library was
> missing.
>
> I had to download we
missing.
The weston provided in my linux-SDK by the vendor was not compiled with
--enable-xwayland and therefore this library was missing.
I had to download weston-2.0.0 and recompile it with --enable-xwayland flag
just to get xwayland.so, and copied it to /usr/lib/libweston-2/ path.
I also copied
On Wed, 27 Nov 2019 16:25:46 +0530
"Devashish Tiwari" wrote:
> Hello,
>
> Thanks for your response.
>
> I rebooted my EVM after making changes to /etc/weston.ini file and I
> found out in /var/log/weston.log that it is using DRM-backend now.
> When I used to ru
Hello,
Thanks for your response.
I rebooted my EVM after making changes to /etc/weston.ini file and I found out
in /var/log/weston.log that it is using DRM-backend now. When I used to run
./Xwayland by hand it used to take Wayland-backend.
However, it still shows some error regarding EGL
On Tue, 26 Nov 2019 17:10:35 +0530
"Devashish Tiwari" wrote:
> Hello,
>
> Thanks for your response.
>
> I am sorry if the link I attached was not visible to you. It's this
> one: Xwayland Compilation
Hi,
sorry, I don't do HTML emails, so there is no lin
Hello,
Thanks for your response.
I am sorry if the link I attached was not visible to you. It's this one:
Xwayland Compilation
I don't know if my cross-build is wrong, because there were no errors during
compilation. Can you please tell how should I check if it's compiled co
On Tue, 26 Nov 2019 10:01:38 +0530
"Devashish Tiwari" wrote:
> Hi All,
>
> I have written a third party application that utilities SDL-X11 to
> draw a window.
>
> I have successfully cross-compiled Xwayland (that is used for X
> clients under Wayland) for my EVM
Hi All,
I have written a third party application that utilities SDL-X11 to draw a
window.
I have successfully cross-compiled Xwayland (that is used for X clients under
Wayland) for my EVM. I have used instructions from this official website and
did the cross-compilation. However, when I run
gt; >
> > >> On Sep 5, 2019, at 3:55 AM, Pekka Paalanen wrote:
>
> > >>> If you redirect weston's both stdout and stderr to a file, you might
> > >>> catch more messages from Xwayland which would hopefully shed more light
>
redirect weston's both stdout and stderr to a file, you might
> >>> catch more messages from Xwayland which would hopefully shed more light
> >>> to why it seems to crash.
> >>>
> >>
> >> How may I go about redirecting that to a fil
> On Sep 6, 2019, at 3:14 AM, Pekka Paalanen wrote:
>
> On Thu, 5 Sep 2019 11:36:50 -0400
> Jd Lyons wrote:
>
>>> On Sep 5, 2019, at 3:55 AM, Pekka Paalanen wrote:
>>>
>>> On Tue, 3 Sep 2019 18:00:02 + (UTC)
>>> Jd Lyons wrote:
On Tue, 3 Sep 2019 18:00:02 + (UTC)
Jd Lyons wrote:
> I'm trying to run Xwayland within weston without Xorg running, I just
> want to be able to run Weston/Wayland and be able to run X11 apps
> within. The trouble I am having is Xwayland won't run any X11 apps
> o
I'm trying to run Xwayland within weston without Xorg running, I just want to
be able to run Weston/Wayland and be able to run X11 apps within.
The trouble I am having is Xwayland won't run any X11 apps outside of just
running Weston within X11.
I'm a little confused about how t
On Fri, 2019-05-10 at 11:09 +0200, Olivier Fourdan wrote:
> Hi,
>
> On Fri, May 10, 2019 at 10:45 AM Jonas Ådahl wrote:
> > On Fri, May 10, 2019 at 11:29:50AM +0300, Pekka Paalanen wrote:
> > > On Thu, 09 May 2019 14:03:52 -0400
> > > Adam Jackson wrote:
> &g
Hi,
On Fri, May 10, 2019 at 10:45 AM Jonas Ådahl wrote:
>
> On Fri, May 10, 2019 at 11:29:50AM +0300, Pekka Paalanen wrote:
> > On Thu, 09 May 2019 14:03:52 -0400
> > Adam Jackson wrote:
> >
> > > The Xwayland component of the Wayland product in bugzilla is sti
On Fri, May 10, 2019 at 11:29:50AM +0300, Pekka Paalanen wrote:
> On Thu, 09 May 2019 14:03:52 -0400
> Adam Jackson wrote:
>
> > The Xwayland component of the Wayland product in bugzilla is still open
> > for bug entry. Does anyone actually want this? I'm happy to migr
On Thu, 09 May 2019 14:03:52 -0400
Adam Jackson wrote:
> The Xwayland component of the Wayland product in bugzilla is still open
> for bug entry. Does anyone actually want this? I'm happy to migrate the
> remaining open bugs into xserver's gitlab issues where they belong, but
The Xwayland component of the Wayland product in bugzilla is still open
for bug entry. Does anyone actually want this? I'm happy to migrate the
remaining open bugs into xserver's gitlab issues where they belong, but
I wanted to make sure nobody's still relying on bugzilla fo
gedit is not acting as a native
> Wayland app, so it will not look at WAYLAND_DISPLAY. Instead, it will be
> acting as an X11 app, which obeys the traditional X11 DISPLAY environment
> variable (and in your case it happens to connect to an Xwayland instance
> that is already associated with
gt; >
> > Is it somewhere documented how Xwayland applications are choosing
> > which compositor to display on? e.g 2 compostiors (1 nested or on
> > another VT)
> > wayland-0 and wayland-1
> > export WAYLAND_DISPLAY=wayland-1
> > GDK_BACKEND=x11 gedit //starts on
as an X11 app, which obeys the traditional X11 DISPLAY environment
variable (and in your case it happens to connect to an Xwayland instance
that is already associated with one of the Wayland displays, but the X11
backend in GTK has no knowledge of Wayland, so it can't know that).
If
On 1/05/19 11:30 pm, Damian Ivanov wrote:
Hello,
Is it somewhere documented how Xwayland applications are choosing
which compositor to display on? e.g 2 compostiors (1 nested or on
another VT)
wayland-0 and wayland-1
export WAYLAND_DISPLAY=wayland-1
GDK_BACKEND=x11 gedit //starts on wayland-0
Hello,
Is it somewhere documented how Xwayland applications are choosing
which compositor to display on? e.g 2 compostiors (1 nested or on
another VT)
wayland-0 and wayland-1
export WAYLAND_DISPLAY=wayland-1
GDK_BACKEND=x11 gedit //starts on wayland-0
If it's not documented how to do it?
> I investigated a bug I encountered while using the Sway Compositor and
> > > traced it back to some behaviour in Xwayland:
> > > The xdg_output and wl_output events are handled in such a way that
> > > output changes (e.g. position) sometimes don't get applied if o
y on the monitor you want. But I
suppose that policy is not implemented anywhere yet.
If your X11 app is written to make its own decisions and override any
window manager actions and ignore RandR information, then the only fix
is indeed to patch Xwayland to set up its rootful Wayland window
differentl
shwar
-Original Message-
From: Pekka Paalanen [mailto:ppaala...@gmail.com]
Sent: Wednesday, February 6, 2019 12:16 AM
To: Singh, Satyeshwar
Cc: wayland-devel@lists.freedesktop.org
Subject: Re: Limiting Xwayland to only one screen
On Tue, 5 Feb 2019 19:51:41 +
"Singh, Satyeshwar" wr
On Tue, 2019-02-05 at 19:51 +, Singh, Satyeshwar wrote:
> Hi,
> I have a 2 screen configuration running Weston. When I run XWayland
> on top, it initially shows a black screen on both the screens. I am
> wondering if there is a way to limit XWayland to only using one
> scr
On Tue, 5 Feb 2019 19:51:41 +
"Singh, Satyeshwar" wrote:
> Hi,
> I have a 2 screen configuration running Weston. When I run XWayland
> on top, it initially shows a black screen on both the screens. I am
> wondering if there is a way to limit XWayland to only using on
Hi,
I have a 2 screen configuration running Weston. When I run XWayland on top, it
initially shows a black screen on both the screens. I am wondering if there is
a way to limit XWayland to only using one screen? Is there a config file or
command line option that allows me to do so?
-Satyeshwar
@@ -106,6 +106,17 @@ Add this to ~/.config/weston.ini (or use the
--xwayland co
xwayland=true
+
+If the default search path for Xwayland in Weston is not correct,
+you need to fix it either by a Weston build option xwayland-path
+or adding this to ~/.config/weston.ini:
+
+
+
+[xwayland]
+path
i915 graphics having this problem)
>
> Bug 1616269 - [abrt] xorg-x11-server-Xwayland: OsLookupColor():
> Display server crashed (edit)
> https://bugzilla.redhat.com/show_bug.cgi?id=1616269
>
> Bug includes a 'coredumpctl gdb' processing of the crashed XWayland
> p
splay
5. nVidia Quadro M1000M
So if any one of those things is not true, problem doesn't happen
(e.g. Fedora QA hasn't yet heard of users with multiple displays using
i915 graphics having this problem)
Bug 1616269 - [abrt] xorg-x11-server-Xwayland: OsLookupColor():
Display server crash
Hi Greg,
On Tue, 10 Apr 2018 at 18:01, Greg V wrote:
> Happened mostly with neovim's xclip usage.
Thanks, I've merged this, updated to include more cases where it could be NULL:
67546bed0..3ea5437db 3ea5437dbd07d9a94aebbb651d8f8eeacc8765bd -> master
Cheers,
Daniel
__
On Mon, 11 Jun 2018 at 11:40, Peter Hutterer wrote:
> On Mon, Jun 11, 2018 at 11:21:25AM +0200, Olivier Fourdan wrote:
[...]
> > > -pad->xdevice = add_device(pad->seat, "xwayland-pad",
> > > +pad->xdevice = add_device(pad->seat, "xwayland
On Mon, Jun 11, 2018 at 11:21:25AM +0200, Olivier Fourdan wrote:
> Hi Peter,
> On Mon, 11 Jun 2018 at 01:12, Peter Hutterer wrote:
> >
> > Changes the device name from "xwayland-stylus" to "xwayland-tablet stylus".
> > This doesn't fully address
1 - 100 of 1035 matches
Mail list logo
