Lines Matching refs:Xwayland
635 One general assumption in Xwayland is that the xwl_window remains the
671 When running non-rootless, Xwayland requires that the Wayland compositor
744 on Xwayland (see
831 The EGLStream backend keeps a queue of pending streams for each Xwayland
855 In this case, Xwayland was thinking that /dev/dri/card0 is already a render node,
890 Xwayland should always wait for a pending frame callback if there's one
1249 The way Xwayland works (like all Wayland clients), it first queries the
1253 That means Xwayland will get the Wayland outputs from the Wayland
1255 the corresponding Xwayland screen properties accordingly.
1266 or existing outputs removed, Xwayland will recompute and update the
1336 Xwayland is just a Wayland client, no X11 screensaver should be
1337 expected to work reliably on Xwayland when running rootless because
1338 Xwayland cannot grab the input devices so it has no way to actually
1341 Turn off the screensaver on Xwayland when running rootless by setting
1432 Thread 1 "Xwayland" received signal SIGSEGV, Segmentation fault.
1475 Simple reproducer in gnome-shell: open up an Xwayland window, press some
1519 Xwayland uses the device private to point to the `xwl_seat`.
1604 GBM_BO_USE_SCANOUT will fail. However Xwayland doesn't need to scan-out
1622 Xwayland is spawned by the Wayland compositor and upon startup will
1628 If the Wayland compositor terminates before Xwayland has got the replies
1747 result in empty windows provided by Xwayland.
2402 circumstances, which would cause an unexpected termination of Xwayland
2856 If Xwayland gets to realize a window meant for composition before the
2862 upfront, but waits to raise Xwayland until there are X11 clients. In this
3098 Running Xwayland non-rootless and resizing the output would lead to a
3216 glamor and Xwayland, e.g.:
3221 (EE) 0: Xwayland (OsSigHandler+0x29)
3231 (EE) 10: Xwayland (glamor_upload_boxes+0x246)
3232 (EE) 11: Xwayland (glamor_copy+0x4d1)
3233 (EE) 12: Xwayland (miCopyRegion+0x96)
3234 (EE) 13: Xwayland (miDoCopy+0x43c)
3235 (EE) 14: Xwayland (glamor_copy_area+0x24)
3236 (EE) 15: Xwayland (damageCopyArea+0xba)
3237 (EE) 16: Xwayland (compCopyWindow+0x31c)
3238 (EE) 17: Xwayland (damageCopyWindow+0xd3)
3239 (EE) 18: Xwayland (miResizeWindow+0x7b7)
3240 (EE) 19: Xwayland (compResizeWindow+0x3a)
3241 (EE) 20: Xwayland (ConfigureWindow+0xa96)
3242 (EE) 21: Xwayland (ProcConfigureWindow+0x7d)
3243 (EE) 22: Xwayland (Dispatch+0x320)
3244 (EE) 23: Xwayland (dix_main+0x366)
3246 (EE) 25: Xwayland (_start+0x2e)
3265 On pointer enter notification, Xwayland checks for an existing pointer
3273 existing X11 grab which is not an ownerEvents grab, Xwayland would crash
3380 which may not be a render node, thus causing Xwayland to fall back to
3382 VT while Xwayland is starting.
3386 Xwayland can make use of them if it can find one.
3498 With Xwayland, the toplevel window is always redirected, so this would
3900 Xwayland creates and destroys the CRTC along with the Wayland outputs,
4104 Xwayland will add and remove CRTCs as Wayland outputs are added or
4108 `xwl_present_sync_callback()` will be triggered after the Xwayland
4109 output's RRCtrcPtr has been destroyed, hence causing a crash in Xwayland
4268 This fixes both Xorg and Xwayland to refuse glamor in such a setup.
4349 So we do not lose subpixel precision in Xwayland.
4507 Xwayland's `xwl_destroy_window()` invokes `xwl_present_cleanup()`
4627 which can possibly crash Xservers such as Xwayland or Xephyr when the
4880 unfortunately Xwayland's glamor code would not set it as enabled which
4884 Xwayland.
5340 known to Xwayland.
5514 Xwayland: dixGetPrivateAddr: Assertion `key->initialized' failed.
5517 (EE) 0: Xwayland (OsSigHandler)
5523 (EE) 6: Xwayland (dixGetPrivateAddr)
5524 (EE) 7: Xwayland (_fbGetWindowPixmap)
5525 (EE) 8: Xwayland (getDrawableDamageRef)
5526 (EE) 9: Xwayland (damageRegionProcessPending)
5527 (EE) 10: Xwayland (damagePolyFillRect)
5528 (EE) 11: Xwayland (miPaintWindow)
5529 (EE) 12: Xwayland (miWindowExposures)
5530 (EE) 13: Xwayland (miHandleValidateExposures)
5531 (EE) 14: Xwayland (SetRootClip)
5532 (EE) 15: Xwayland (update_screen_size)
5533 (EE) 16: Xwayland (apply_output_change)
5540 (EE) 23: Xwayland (InitInput)
5541 (EE) 24: Xwayland (dix_main)
5543 (EE) 26: Xwayland (_start)
5581 for NVidia GPU was made available only when Xwayland was built with
5584 Wayland compositors who spawn Xwayland have no easy way to tell whether
5585 or not Xwayland was built with EGLStream support enabled, and adding
5586 "-eglstream" command line option to Xwayland when it wasn't built with
5587 EGLStream support would prevent Xwayland from starting (“Unrecognized
5591 EGLStream support in Xwayland. Obviously, if Xwayland was built without
5812 I upgraded Xwayland and the assorted libraries from git masters today,
6509 This adds initial support for displaying Xwayland applications through
6533 surface producer before Xwayland actually damages and commits the
6541 EGLstream. Because Xwayland has to potentially handle both responding to
6546 thus hang while both Xwayland and the wayland compositor await responses
6556 pending reqests before Xwayland hits the part of it's event loop where
6573 error from Xwayland when using the eglstream backend.
6599 into it's own EGL backend for Xwayland, xwayland-glamor-gbm.c.
6919 Present support in Xwayland relies on glamor, make sure Xwayland can
6936 Thread 1 "Xwayland" received signal SIGSEGV, Segmentation fault.
7252 [735/786] Generating 'hw/xwayland/Xwayland@exe/relative-pointer-unstable-v1-protocol.c'.
7903 ... for xfree86, at least for now. Things appear to work for Xwayland
8055 To make use of this functionality Xwayland must run rootless and with
9093 v2: Properly free fds in Xwayland
9866 When xdg_output support was added to Xwayland, need_rotate parameter was
10203 Unfortunately, on my machine Xwayland immediately crashes when I try to
10208 at hw/xwayland/Xwayland@exe/pointer-constraints-unstable-v1-client-protocol.h:612
10561 its redirect before Xwayland has unrealized the window (e.g. if the X11
10575 This is a rare occurrence of a crash in Xwayland for which I don't have
10602 unredirected immediately, before the damage is processed by Xwayland.
10720 This is however much useful for Xwayland to advertise the output size
11094 that don't won't be able to run Xwayland anyway. The trade-off
11096 unusable Xwayland for unusual platform" and this commit switches to the
11427 Xwayland is a pretty standard Wayland client, we want to be able to
11495 a NULL pointer dereference will occur leading to a crash of Xwayland.
12219 This also unbreaks Xwayland builds with -Dglx=false, the thing that
13047 Not all compositors allow for customizing the Xwayland command line,
13049 Xwayland binary hardcoded, which makes it harder for users to disable
13050 glamor acceleration in Xwayland (glamor being used by default).
13053 in Xwayland.
13124 ... instead of its root window. Xwayland's rootless mode empties the
13128 this change, non-glamor Xwayland's GetImage actually works.
13260 Xwayland would crash in some circumstances while trying to issue a
13302 If the compositor has no support for the Xwayland keyboard grab
13634 The keyboard grabbing protocol for Xwayland is included in
13638 builds and add support for this new protocol in Xwayland.
14439 Xwayland doesn't override these, so we don't need defining those
14690 When running an Xwayland server from the command line, we end up
14700 (EE) 0: Xwayland (OsSigHandler+0x3b) [0x4982f9]
14705 (EE) 5: Xwayland (__glXDRIscreenDestroy+0x30) [0x54686e]
14706 (EE) 6: Xwayland (glxCloseScreen+0x3f) [0x5473db]
14707 (EE) 7: Xwayland (glxCloseScreen+0x53) [0x5473ef]
14708 (EE) 8: Xwayland (dix_main+0x7b6) [0x44c8c9]
14709 (EE) 9: Xwayland (main+0x28) [0x61c503]
14711 (EE) 11: Xwayland (_start+0x2a) [0x4208fa]
14721 - Start an Xwayland session with the default settings
15336 (EE) 0: Xwayland (OsSigHandler+0x3b) [0x4982f9]
15338 (EE) 2: Xwayland (xwl_set_cursor+0x9f) [0x429974]
15339 (EE) 3: Xwayland (miPointerUpdateSprite+0x261) [0x4fe1ca]
15340 (EE) 4: Xwayland (mieqProcessInputEvents+0x239) [0x4f8d33]
15341 (EE) 5: Xwayland (ProcessInputEvents+0x9) [0x4282f0]
15342 (EE) 6: Xwayland (Dispatch+0x42) [0x43e2d4]
15343 (EE) 7: Xwayland (dix_main+0x5c9) [0x44c6dc]
15344 (EE) 8: Xwayland (main+0x28) [0x61c523]
15346 (EE) 10: Xwayland (_start+0x2a) [0x4208fa]
15591 on Xwayland, so have cursor changes trigger a xwl_cursor update on
15592 every tool (and the pointer, again). Maybe Xwayland could keep track
15820 This is a work in progress that builds Xvfb, Xephyr, Xwayland, Xnest,
16005 crash of the Xserver. This affects Xwayland, Xephyr, modesetting driver
17124 _XWAYLAND_ALLOW_COMMITS property to control when Xwayland sends
17130 state before Xwayland does the first commit. XWM can use this to ensure
17141 Without this patch (i.e. with the old behaviour) Xwayland can and will
17170 CC Xwayland-xwayland.o
17368 Xwayland support for pointer locking in confinement requires
17516 Previously, we would swap the width/height of the Xwayland output based
17525 when the output is rotated, so by changing the Xwayland output width and
17526 height based on rotation, Xwayland causes XRandr to report the wrong
17531 Xwayland outputs, leave the actual width/height unchanged but apply the
17546 If the Wayland compositor sets a rotation on the output, Xwayland
18908 configure: Enable glamor when building just Xwayland
18922 Sometimes, Xwayland will try to use a cursor that has just been freed,
18927 XYToWindow() returns, and Xwayland implements its own xwl_xy_to_window()
18960 (EE) 0: Xwayland (OsSigHandler+0x29)
18962 (EE) 2: Xwayland (glamor_sync_close+0x2a)
18963 (EE) 3: Xwayland (glamor_close_screen+0x52)
18964 (EE) 4: Xwayland (CursorCloseScreen+0x88)
18965 (EE) 5: Xwayland (AnimCurCloseScreen+0xa4)
18966 (EE) 6: Xwayland (present_close_screen+0x42)
18967 (EE) 7: Xwayland (dix_main+0x4f9)
18969 (EE) 9: Xwayland (_start+0x2a)
19277 On some random condition, a touch event may trigger a crash in Xwayland
19653 Strictly speaking Xephyr/Xwayland may require version greater than the
19902 with unaccelerated motion deltas. This will later be used by Xwayland
20366 In Xwayland's xwl_unrealize_cursor(), the x_cursor is cleared up only
20393 wl_display_flush() can fail with EAGAIN and Xwayland would make this a
20396 When this happens, it means that Xwayland has flooded the Wayland file
20399 blocking, waiting for an X reply while Xwayland tries to write data to
21016 emulation in Xwayland.
21908 if they match then it means the pointer has left an Xwayland window for
21998 Without this a change in eg Xext/ wouldn't relink Xwayland, making you
22076 Xwayland would do the same in its xwl_output_destroy() called from
23216 (EE) 0: ./hw/xwayland/Xwayland (ForceClockId+0x5c) [0x47713c]
23217 (EE) 1: ./hw/xwayland/Xwayland (OsInit+0x25) [0x4763d5]
23218 (EE) 2: ./hw/xwayland/Xwayland (dix_main+0x11c) [0x43e60c]
23220 (EE) 4: ./hw/xwayland/Xwayland (_start+0x29) [0x4238e9]
24247 Xwayland window matching, DoEnterLeaveEvents() does not get invoked and
24821 The rountrip in Xwayland's InitInput() is unlikely the culprit for the
25138 avoid repeating keys in Xwayland while the Wayland compositor cannot
25264 To avoid these issues, make Xwayland always use CLOCK_MONOTONIC, so
26865 xrandr command and get confused with the mode name returned by Xwayland,
27605 This allows building Xwayland without Xorg and still include the
27879 (EE) 9: /usr/bin/Xwayland (_start+0x29) [0x423299]
27881 (EE) 7: /usr/bin/Xwayland (dix_main+0x3b3) [0x544ef3]
27882 (EE) 6: /usr/bin/Xwayland (Dispatch+0x31e) [0x54109e]
27883 (EE) 5: /usr/bin/Xwayland (ProcRRGetMonitors+0x9b) [0x4ca18b]
27884 (EE) 4: /usr/bin/Xwayland (RRMonitorMakeList+0x269) [0x4c9ba9]
27885 (EE) 3: /usr/bin/Xwayland (RRMonitorSetFromServer+0x118) [0x4c9198]
27886 (EE) 2: /usr/bin/Xwayland (MakeAtom+0x30) [0x530710]
27888 (EE) 0: /usr/bin/Xwayland (OsSigHandler+0x29) [0x5792d9]
28472 looking at the file names of the currently open fds of the Xwayland
29019 This adds support to Xwayland to try and use OpenGL core
31637 This makes Xwayland correctly handle a monitor getting unplugged.
32443 solved part of the problem. If Xwayland is launched without a capability
32444 (e.g. no pointer device is connected when Xwayland was spinned up), and
34491 Xwayland opens anonymous files for its sharing buffers, move these
34892 any user on the system connect to the Xwayland server.
34894 That's clearly suboptimal, given Xwayland is generally designed
34917 Xwayland, on the other hand is new, and much more targeted
34929 A subsequent commit will add that call for Xwayland.
34942 Xwayland currently allows wide-open access to the X sockets
36207 When using glamor (either in Xephyr or Xwayland) on hardware with too
36445 So that Xwayland gets re-linked each time glamor is modified.
37666 Xwayland Makefile explicitely set its dependencies on
37671 "No rule to make target '-L/path/to/the/lib', needed by 'Xwayland'.
47399 Xwayland will eventually need the current client in dri3_open. Simply
47483 Xwayland DDX
47488 a better plan is to just make Xwayland its own DDX, similar to Xwin
47492 is that Xwayland dosn't need to be setuid root.
47494 The Xwayland support for DRI3, Glamor and render nodes was done by
47496 to the Xwayland DDX.
48470 When the Xwayland server is socket-activated, we need to connect and
48473 descriptor for the window manager connection to the Xwayland server,
48792 and will be useful for on-demand launched Xwayland servers.