GitLab

GIT_SILENT

Announces that the wayland backend supports the XwaylandClientsScale
setting, which is a boolean value to tell kwin whether it should
automatically scale xwayland apps or let the apps do it themselves.

When the setting changes:
- Updates and notifies kwin's xwayland scale value so it adapts.
- Runs the fonts kcminit module so that the system gets properly
initialised.

dacheng yang authored May 24, 2022 and Xaver Hugl committed May 24, 2022

Because of the order of calls in XRandRConfig, screen is dirty when switching display modes.

This patch removes the intermediateScreenSize.
Swap the change order of crtc and screen size, and disable crtc before that.

The previous method was to first set an intermediate screen size then set the crtc and finally set the target screen size.
The modified method is to disable crtc first, then change the screen size and finally set crtc.
This change can effectively solve the problem of blurry screen when switching display modes.

GIT_SILENT
NO_CHANGELOG

CCMAIL: plasma-devel@kde.org

GIT_SILENT

GIT_SILENT

When our wrapper class QtWayland::kde_primary_output_v1 gets destroyed
there is no code to delete the underlying wl_proxy object. Any events to
that proxy after our wrapper have gone will get disaptched to the
generated code which in turn will just crash.

BUG: 451847

This includes Qt6 specific code changes as well, but still lacks the port
to KWaylandServer (that's also needed due to KF5::WaylandServer being
gone in 6).

Model doesn't include the connector type.

...to reflect reality. It already needs kde-primary-output-v1.xml,
which appeared in 1.6.0.

GIT_SILENT

GIT_SILENT

Méven Car authored Dec 15, 2021 and Méven Car committed Dec 21, 2021

GIT_SILENT

Patrick Häcker authored Nov 05, 2021 and David Redondo committed Nov 15, 2021

When kscreen_backend is started by D-Bus activation, the Journal does
not use the correct log levels, but instead all logs are output at
priority warning.

Therefore, do the D-Bus activation with a systemd unit file, so that
log levels keep their intended priority.

This has the additional benefit of moving kscreen_backend from app.slice
to background.slice.

BUG: 444084

If the compositor supports newer version of output-device or
primary-output, any app that uses libkscreen will crash eventually.

The proper way to select the interface version is to choose the minimum
between the implemented version and the version supported by the
compositor.

Adopts the kde_outputmanagement_v2 hooks for it, lets our users specify
a primary display for a workspace.

As now it's supported on both wayland and X11

In VirtualBox KDE runs at low resolution,
and when you try to change the resolution through the "Screen Settings"
it returns to the original one again.
How to check:
- run KDE neon on VirtualBox
- change the resolution

VirtualBox sets the hotplug_mode_update property, but its preferred mode
is always 800x600, and KScreen returns the resolution to 800x600.

Now XRandRCrtc stores the timestamp of the last resolution change
request from backend, and the timestamp of the last config update from
X11.
If the changes were initiated by XRandR backend (i.e. 'timestamp of the
last config update from X11' less or equal 'last resolution change
request'), then the followPreferedMode flag in KScreenConfig is set to
false.

BUG: 407058

GIT_SILENT

BUG: 428626

The setTabletModeAvailable and setTabletModeEngaged properties
were not copied across in Config::apply.

While they were written to the control file, they were not written into
the configuration files from kded and were thus reset after a session restart

BUG: 442520

GIT_SILENT

GIT_SILENT