[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=389191

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.26
 Resolution|UPSTREAM|FIXED

--- Comment #38 from Nate Graham  ---
This is fixed in Plasma 5.26! \o/

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Dāvis]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #37 from Dāvis  ---
(In reply to Nate Graham from comment #36)
> (In reply to Dāvis from comment #35)
> > Why this bug report is closed? It's still broken...
> Please see
> https://community.kde.org/Get_Involved/
> Issue_Reporting#Understand_what_the_resolution_statuses_mean
> 

There's actually nothing written about "CLOSED UPSTREAM" state :P and also I
would say it's bad idea to close issue if it's not resolved so it can be easier
findable as people might think it doesn't apply to them and open new issues.
Also I would say upstream needs to see how many people are impacted so everyone
should be pointed there.

> > If this is XWayland bug, then where's the link to upstream bug report?
> In the URL field.

That's a MR for potential fix, not bug report itself but sure.

Also this affects many applications, here's issue for mpv
https://github.com/mpv-player/mpv/issues/9443

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #36 from Nate Graham  ---
(In reply to Dāvis from comment #35)
> Why this bug report is closed? It's still broken...
Please see
https://community.kde.org/Get_Involved/Issue_Reporting#Understand_what_the_resolution_statuses_mean

> If this is XWayland bug, then where's the link to upstream bug report?
In the URL field.

The issue is currently being worked on by multiple people and organizations at
multiple levels of the graphics stack. Not to worry, it'll get fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Dāvis]

https://bugs.kde.org/show_bug.cgi?id=389191

Dāvis  changed:

   What|Removed |Added

 CC||davis...@gmail.com
Version|5.11.95 |git master

--- Comment #35 from Dāvis  ---
Why this bug report is closed? It's still broken...
If this is XWayland bug, then where's the link to upstream bug report?

I've noticed that setting Wayland scaling breaks badly some games running under
XWayland with Wine.
I want to keep Wayland scaling (seems to be working fine at 150% for Wayland
apps I use) but disable any scaling for XWayland because most apps work way
better on X11 without any scaling than this broken scaling.

This particular issue I just encountered isn't related to blurriness but window
shaking/resizing and wrong resolution. It's hard to describe in words so watch
this video demonstration https://youtu.be/AS9H8QrV5Ig

Basically I've native Wayland resolution of 3440x1440 with 150% scaling and
that causes XWayland to report incorrect resolution of 2288x960 which a lot of
applications can't handle as they're used to standard resolutions so I think it
would be very useful if we could force "regular" resolution to X11 clients.

Also are there any workarounds for this other than disabling scaling
altogether?

by the way I'm using latest KWin git master and
$ Xwayland -version
The X.Org Foundation Xwayland Version 22.1.1 (12201001)
X Protocol Version 11, Revision 0

$ wayland-info
interface: 'wl_compositor',  version:  4, name:  1
interface: 'zwp_tablet_manager_v2',  version:  1, name:  2
interface: 'zwp_keyboard_shortcuts_inhibit_manager_v1',  version:  1, name:  3
interface: 'xdg_wm_base',version:  4, name:  5
interface: 'zwlr_layer_shell_v1',version:  3, name:  6
interface: 'zxdg_decoration_manager_v1', version:  1, name:  7
interface: 'wp_viewporter',  version:  1, name:  8
interface: 'wl_shm', version:  1, name:  9
formats: 'XB48'(0x38344258) 'AB48'(0x38344241) 'XB30'(0x30334258)
'AB30'(0x30334241) 'XR30'(0x30335258) 'AR30'(0x30335241) XRGB ARGB
interface: 'wl_seat',version:  7, name: 10
name: 
capabilities: pointer keyboard touch
keyboard repeat rate: 25
keyboard repeat delay: 660
interface: 'zwp_pointer_gestures_v1',version:  3, name: 11
interface: 'zwp_pointer_constraints_v1', version:  1, name: 12
interface: 'zwp_relative_pointer_manager_v1',version:  1, name: 13
interface: 'wl_data_device_manager', version:  3, name: 14
interface: 'zwlr_data_control_manager_v1',   version:  2, name: 15
interface: 'zwp_primary_selection_device_manager_v1',version:  1, name: 16
interface: 'org_kde_kwin_idle',  version:  1, name: 17
interface: 'zwp_idle_inhibit_manager_v1',version:  1, name: 18
interface: 'org_kde_plasma_shell',   version:  6, name: 19
interface: 'org_kde_kwin_appmenu_manager',   version:  1, name: 20
interface: 'org_kde_kwin_server_decoration_palette_manager', version:  1, name:
21
interface: 'org_kde_plasma_virtual_desktop_management',  version:  2, name: 23
interface: 'org_kde_kwin_shadow_manager',version:  2, name: 25
interface: 'org_kde_kwin_dpms_manager',  version:  1, name: 26
interface: 'org_kde_kwin_server_decoration_manager', version:  1, name: 27
interface: 'kde_output_management_v2',   version:  2, name: 28
interface: 'kde_primary_output_v1',  version:  1, name: 29
interface: 'zxdg_output_manager_v1', version:  3, name: 30
xdg_output_v1
output: 43
name: 'DP-1'
description: 'Acer Technologies X34 GS/277881511'
logical_x: 0, logical_y: 0
logical_width: 2293, logical_height: 960
interface: 'wl_subcompositor',   version:  1, name: 31
interface: 'zxdg_exporter_v2',   version:  1, name: 32
interface: 'zxdg_importer_v2',   version:  1, name: 33
interface: 'xdg_activation_v1',  version:  1, name: 36
interface: 'wp_drm_lease_device_v1', version:  1, name: 37
interface: 'wl_drm', version:  2, name: 40
interface: 'zwp_linux_dmabuf_v1',version:  4, name: 41
...
interface: 'kde_output_device_v2',   version:  2, name: 42
interface: 'wl_output',  version:  3, name: 43
x: 0, y: 0, scale: 2,

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Jeffrey Bouter]

https://bugs.kde.org/show_bug.cgi?id=389191

Jeffrey Bouter  changed:

   What|Removed |Added

 CC|k...@kn0x.org|

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[postix]

https://bugs.kde.org/show_bug.cgi?id=389191

postix  changed:

   What|Removed |Added

 CC||pos...@posteo.eu

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=389191

David Edmundson  changed:

   What|Removed |Added

 CC||richrocksmywo...@gmail.com

--- Comment #34 from David Edmundson  ---
*** Bug 448136 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Tyler Gordon]

https://bugs.kde.org/show_bug.cgi?id=389191

Tyler Gordon  changed:

   What|Removed |Added

 CC||tgordon...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=389191

Nate Graham  changed:

   What|Removed |Added

 CC||i...@mikelpr.com

--- Comment #33 from Nate Graham  ---
*** Bug 440883 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=389191

Nate Graham  changed:

   What|Removed |Added

URL||https://gitlab.freedesktop.
   ||org/xorg/xserver/-/merge_re
   ||quests/111

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=389191

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=426263

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Alex]

https://bugs.kde.org/show_bug.cgi?id=389191

Alex  changed:

   What|Removed |Added

 CC||alex...@protonmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=389191

zvova7...@gmail.com changed:

   What|Removed |Added

 CC||zvova7...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Ashark]

https://bugs.kde.org/show_bug.cgi?id=389191

Ashark  changed:

   What|Removed |Added

 CC||ash...@linuxcomp.ru

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Claudius Ellsel]

https://bugs.kde.org/show_bug.cgi?id=389191

Claudius Ellsel  changed:

   What|Removed |Added

 CC||claudius.ell...@live.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[ruruoli]

https://bugs.kde.org/show_bug.cgi?id=389191

ruruoli  changed:

   What|Removed |Added

 CC||maniikarab...@protonmail.ch

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=389191

Nate Graham  changed:

   What|Removed |Added

 Resolution|INTENTIONAL |UPSTREAM

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=389191

Nate Graham  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #32 from Nate Graham  ---
*** Bug 412088 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=389191

David Edmundson  changed:

   What|Removed |Added

 CC||k...@kn0x.org

--- Comment #31 from David Edmundson  ---
*** Bug 404343 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Roman Gilg]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #30 from Roman Gilg  ---
FYI I have written patches for KWin and XWayland with a solution attempt:

https://gitlab.freedesktop.org/xorg/xserver/merge_requests/111
https://phabricator.kde.org/D18486

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=389191

David Edmundson  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--- Comment #29 from David Edmundson  ---
> Or you can quickly add the ability to disable-enable raster scaling for 
> individual applications

We literally cannot for individual xwayland clients.

Potentially we could do tonne of hacks to make and add an input transformations
framework everywhere to put a toggle for all xwayland. 

But at that point it'll be just as quick to put the option in xwayland where it
benefits every other project - which is my stance that I've already stated ages
ago.


---

Gnome behaviour depends on gsettings set org.gnome.mutter experimental-features
"['scale-monitor-framebuffer']" which will be the default soon putting it in
line with kwin and everyone else.

>there is every reason to assume that GNOME sends some special message

No it doesn't.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Martin Flöser]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #28 from Martin Flöser  ---
Weston supported scaling ages prior to KWin.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #27 from kiv.ap...@gmail.com ---
1) Raster window scaling is done by code in KWin, isn't it? Because I remember
very well that it was in KDE that this feature appeared first. Of course, you
can wait for the necessary functionality to be added to XWayland, and then wait
a few more years for the common applications to start supporting it (but they
will most likely migrate to Wayland during this time). Or you can quickly add
the ability to disable-enable raster scaling for individual applications (and
develop default behavior as XWayland evolves as you want). As a result, users
will be able to comfortably use KDE on Wayland today, rather than wait for
years.

2) GNOME have some sort of workaround especially for Google Chrome. It is
running Xwayland, but when you more its window to another screen DPI is
changed. The DPI of the mouse pointer remains the same as the monitor, where
the window first appeared (that is, there is every reason to assume that GNOME
sends some special message to Google Chrome and it itself changes the size of
the window and the scaling factor). Given that most other applications support
Wayland normally and problems only with popular browsers, this workaround is in
fact decisive for many people who would like to use Wayland but cannot without
a browser.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #26 from David Edmundson  ---
>this is a non-standard feature

No. 

>Gnome

Also no. See their above link brainstorming solutions.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Eike Hein]

https://bugs.kde.org/show_bug.cgi?id=389191

Eike Hein  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |INTENTIONAL

--- Comment #25 from Eike Hein  ---
Please don't change the bug state set by developers.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #24 from kiv.ap...@gmail.com ---
I want to add my opinion:
1) Raster scaling of windows for current DPI is a feature of KWin. Many other
Wayland compositors can't do it. As far as I understand, this is a non-standard
feature, so you should not demand support in XWayland, the settings should be
in KWin itself.
2) Gnome somehow managed to implement the correct scaling of some X.org
applications (Google Chrome) when changing DPI (dragging to another display).
They may have applied not very elegant solutions, but if it is "just work,"
then what's wrong with that? I think the most important thing is a good
experience of users of your DE, and beautiful technical solutions are only in
second place. In the harsh real world, they are not always possible within a
reasonable time.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Mikola]

https://bugs.kde.org/show_bug.cgi?id=389191

Mikola  changed:

   What|Removed |Added

 Resolution|INTENTIONAL |---
 Status|RESOLVED|REOPENED

--- Comment #23 from Mikola  ---
All the links above are not relevant to current bug, because they discuss ways
of improving situation over what is available in X11 session. But at the moment
situation in Wayland session is much worse than in X11 session.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Eike Hein]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #22 from Eike Hein  ---
Since pooling of information is a good idea, I'll also add this link with some
relevant GUACEC notes David passed me:
https://wiki.gnome.org/Initiatives/Wayland/XWayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Eike Hein]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #21 from Eike Hein  ---
I think there's some people working on it now:
https://keithp.com/blogs/window-scaling/

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Martin Flöser]

https://bugs.kde.org/show_bug.cgi?id=389191

Martin Flöser  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |INTENTIONAL

--- Comment #20 from Martin Flöser  ---
I'm resetting the state. As explained in comment #17 this needs to resolved in
XWayland. I'm fully with David on this. There is IMHO nothing KWin could do
about it, though XWayland can.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Mikola]

https://bugs.kde.org/show_bug.cgi?id=389191

Mikola  changed:

   What|Removed |Added

 Resolution|INTENTIONAL |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #19 from Mikola  ---
I have to reopen this, because bug still exist and causes very bad user
experience. Screenshots of current situation can be found in
https://bugs.kde.org/show_bug.cgi?id=389196

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Eike Hein]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #18 from Eike Hein  ---
> I'm genuinely curious as to whether your machine is worse than mine or 
> whether it's subjective opinions on the same thing. We should test at Akademy.

I guess we didn't get around to this :). But I guess I don't really see how it
couldn't be terrible. It's a 1x window being scaled naively to 2x with no
smoothing or so, i.e. straight up pixel-doubling, which makes everything look
like Minecraft. Do you remember the bug Gwenview had for a long time with hidpi
where its content view was heavily pixelated? Same thing ...

I'm fine with pursuing the path of "get Firefox/Wayland working, and forget
about XWayland" anyway, but I also can't begrudge anyone with a 4K screen not
wanting to use Plasma/Wayland at the moment due to this. I think this problem
will come up again with certain 2D games in the future however.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Haochen Tong]

https://bugs.kde.org/show_bug.cgi?id=389191

Haochen Tong  changed:

   What|Removed |Added

 CC||i...@hexchain.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Haochen Tong]

https://bugs.kde.org/show_bug.cgi?id=389191

Haochen Tong  changed:

   What|Removed |Added

 CC|i...@hexchain.org  |

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=389191

David Edmundson  changed:

   What|Removed |Added

 CC||jm.ouwerk...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #17 from David Edmundson  ---
I'm genuinely curious as to whether your machine is worse than mine or whether
it's subjective opinions on the same thing.
We should test at Akademy.

My stance remains, but for completeness, here's some links on the topic:

It's a topic we discussed when I went to Guadec. Here's Jonas and Daniel S's
current notes.

https://wiki.gnome.org/Initiatives/Wayland/XWayland

It's more in depth as they're mostly talking about runtime supporting multiple
options at once.

An option in xwayland to change would be much simpler.

One would need to:
 - set the wl_surface.scale to the wl_output.scale
 - set the X screen size appropriately to match the mode
 - do the relevant input redirection to our fake surface local co-ordinates

-

There is an other option I tried playing with.

Chrome made a wayland proxy wrapper with xwayland support called sommelier. The
interesting twist being that it converts Xwayland clients into wayland windows.

https://chromium.googlesource.com/chromiumos/platform2/+/HEAD/vm_tools/sommelier/README.md
 

I did some work to try and make it compile, but I got stuck on some virtwl
nonsense which they use for SHM and gave up trying to remove that

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Eike Hein]

https://bugs.kde.org/show_bug.cgi?id=389191

Eike Hein  changed:

   What|Removed |Added

 CC||h...@kde.org

--- Comment #16 from Eike Hein  ---
I'm not super happy with this being marked WONTFIX. It makes the Wayland
session extremely unpleasant to use for the time being.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Roman Gilg]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #15 from Roman Gilg  ---
I run Chrome and Firefox on Wayland with 2x scaling. And there is no pixelation
at all. I have not tinkered with any scaling options in the apps.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Frederik Gladhorn]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #14 from Frederik Gladhorn  ---
Is there any mainstream browser that works with Wayland in HighDPI then? (sadly
I cannot fully switch to Falkon for various reasons and not having a browser is
for the time being what keeps me from using wayland)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=389191

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 CC||k...@davidedmundson.co.uk
 Status|UNCONFIRMED |RESOLVED

--- Comment #13 from David Edmundson  ---
>The addition of XDG Output Protocol could solve this issue: 
>https://phabricator.kde.org/D12235

It's unrelated.

Making it optional per client with one xwayland is simply not feasible. 
Making it optional inside xwayland is quite feasible, but not implemented. If
that happened I would happily add relevant support in kwin.

Though the number of clients that are modern enough to have high DPI support
and don't have a wayland implementation is a very small and decreasing
minority.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Roman Gilg]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #12 from Roman Gilg  ---
The addition of XDG Output Protocol could solve this issue:
https://phabricator.kde.org/D12235

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Leonard Lausen]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #11 from Leonard Lausen  ---
Another one is Emacs. Unlike Firefox and Chrome it likely won't support Wayland
natively in the near future either.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Frederik Gladhorn]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #10 from Frederik Gladhorn  ---
Prime examples are Chromium and Firefox (I'm using 2x usually).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Roman Gilg]

https://bugs.kde.org/show_bug.cgi?id=389191

Roman Gilg  changed:

   What|Removed |Added

 CC||subd...@gmail.com

--- Comment #9 from Roman Gilg  ---
Pls name a few test applications on Xwayland, which show these behavior. Which
scale factor are you using?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Frederik Gladhorn]

https://bugs.kde.org/show_bug.cgi?id=389191

Frederik Gladhorn  changed:

   What|Removed |Added

 CC||gladh...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Martin Flöser]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #8 from Martin Flöser  ---
(In reply to kiv.apple from comment #7)
> Is there a temporal workaround that allows to completely disable the scaling
> of XWayland applications without recompiling KWin?

no

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #7 from kiv.ap...@gmail.com ---
Is there a temporal workaround that allows to completely disable the scaling of
XWayland applications without recompiling KWin?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=389191

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Kai Uwe Broulik]

https://bugs.kde.org/show_bug.cgi?id=389191

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||kiv.ap...@gmail.com

--- Comment #6 from Kai Uwe Broulik  ---
*** Bug 390049 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Kai Uwe Broulik]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #5 from Kai Uwe Broulik  ---
Good idea!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Martin Flöser]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #4 from Martin Flöser  ---
(In reply to Kai Uwe Broulik from comment #2)
> What I would ideally like to see is a checkbox in KPropertiesDialog to
> disable scaling on a per-application basis, like we already have with "run
> in terminal" and "run on discrete GPU" and then have KRun tell KWin not to
> scale windows of that application.

on my blog someone suggested using window specific rules. That is a good idea
IMHO. It could even allow to match all X windows.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Kai Uwe Broulik]

https://bugs.kde.org/show_bug.cgi?id=389191

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||mikolabr...@ukr.net

--- Comment #3 from Kai Uwe Broulik  ---
*** Bug 389196 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Kai Uwe Broulik]

https://bugs.kde.org/show_bug.cgi?id=389191

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #2 from Kai Uwe Broulik  ---
What I would ideally like to see is a checkbox in KPropertiesDialog to disable
scaling on a per-application basis, like we already have with "run in terminal"
and "run on discrete GPU" and then have KRun tell KWin not to scale windows of
that application.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Leonard Lausen]

https://bugs.kde.org/show_bug.cgi?id=389191

--- Comment #1 from Leonard Lausen  ---
Possibly upscaling could be replaced by downscaling for the lower DPI screens.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional

[Martin Flöser]

https://bugs.kde.org/show_bug.cgi?id=389191

Martin Flöser  changed:

   What|Removed |Added

   Severity|normal  |wishlist

-- 
You are receiving this mail because:
You are watching all bug changes.