Skip to content
Snippets Groups Projects
Select Git revision
  • master default
  • xwayland-24.1
  • server-21.1-branch
  • xwayland-23.2
  • xwayland-23.1
  • xwayland-22.1
  • xwayland-21.1
  • server-1.20-branch protected
  • server-1.19-branch
  • server-1.18-branch
  • server-1.17-branch
  • server-1.16-branch
  • server-1.15-branch
  • server-1.14-branch
  • server-1.13-branch
  • server-1.12-branch
  • server-1.11-branch
  • server-1.10-branch
  • server-1.9-branch
  • server-1.8-branch
  • xwayland-24.1.6
  • xorg-server-21.1.16
  • xwayland-24.1.5
  • xorg-server-21.1.15
  • xorg-server-21.1.14
  • xwayland-24.1.4
  • xwayland-24.1.3
  • xwayland-24.1.2
  • xwayland-24.1.1
  • xwayland-24.1.0
  • xwayland-23.2.7
  • xwayland-24.0.99.902
  • xwayland-24.0.99.901
  • xorg-server-21.1.13
  • xwayland-23.2.6
  • xorg-server-21.1.12
  • xwayland-23.2.5
  • xwayland-23.2.4
  • xorg-server-21.1.11
  • xwayland-23.2.3
40 results
Compare
user avatar
xwayland: Fix setting of _XWAYLAND_RANDR_EMU_MONITOR_RECTS prop on new windows
Hans de Goede authored 
For window-manager managed windows, xwl_realize_window is only called for
the window-manager's decoration window and not for the actual client window
on which we should set the _XWAYLAND_RANDR_EMU_MONITOR_RECTS prop.

Usualy this is not a problem since we walk all client windows to update
the property when the resolution is changed through a randr call.

But for apps which first do the randr change and only then create their
window this does not work, and our xwl_output_set_window_randr_emu_props
call in xwl_realize_window is a no-op as that is only called for the wm
decoration window and not for the actual client's window.

This commit fixes this by making ensure_surface_for_window() call
xwl_output_set_window_randr_emu_props on the first and only child of
window-manager managed windows.

Note this also removes the non-functional xwl_output_set_window_randr_emu_props
call from xwl_realize_window, which was intended to do this, but does not
work.

This fixes apps using the ogre3d library always running at the
monitors native resolution.

Acked-by: default avatarOlivier Fourdan <ofourdan@redhat.com>
Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
148f428d
History
user avatar 148f428d
History
Name Last commit Last update
.gitlab-ci
Xext
Xi
composite
config
damageext
dbe
dix
doc
dri3
exa
fb
glamor
glx
hw
include
m4
man
mi
miext
os
present
pseudoramiX
randr
record
render
test
xfixes
xkb
.appveyor.yml
.dir-locals.el
.gitignore
.gitlab-ci.yml
.travis.yml
COPYING
Makefile.am
README.md
autogen.sh
configure.ac
devbook.am
docbook.am
manpages.am
meson.build
meson_options.txt
xorg-server.m4
xorg-server.pc.in
xserver.ent.in
README.md

X Server

The X server accepts requests from client applications to create windows, which are (normally rectangular) "virtual screens" that the client program can draw into.

Windows are then composed on the actual screen by the X server (or by a separate composite manager) as directed by the window manager, which usually communicates with the user via graphical controls such as buttons and draggable titlebars and borders.

For a comprehensive overview of X Server and X Window System, consult the following article: https://en.wikipedia.org/wiki/X_server

All questions regarding this software should be directed at the Xorg mailing list:

https://lists.freedesktop.org/mailman/listinfo/xorg

The master development code repository can be found at:

https://gitlab.freedesktop.org/xorg/xserver

For patch submission instructions, see:

https://www.x.org/wiki/Development/Documentation/SubmittingPatches

As with other projects hosted on freedesktop.org, X.Org follows its Code of Conduct, based on the Contributor Covenant. Please conduct yourself in a respectful and civilized manner when using the above mailing lists, bug trackers, etc:

https://www.freedesktop.org/wiki/CodeOfConduct