It doesn't work well with HiDPI, tried launching plasma 5.11, all the native things looked fine but Chrome and Steam (pretty sure running under Xwayland) were both twice as big as I was expected, seems the hidpi settings are being passed through. It actually made steam readable for the first time under hidpi
Announcement
Collapse
No announcement yet.
KDE Plasma 5.12 Pushing For "An Awesome Release On Wayland"
Collapse
X
-
Does plasma offer a way to change montior confiuration using a cli interface? Currently i rely on a script which uses xrandr bound to hotkeys to turn specific monitors on and off, but that won't work on wayland anymore. At the moment i use gnome, which seems to offer a dbus api to do this, but i could get it to work so far.
I think something which provides xrandr-like functionality and works on all wayland compositors would be preferable though.
- Likes 1
Comment
-
Originally posted by sandy8925 View PostYeah, Martin made it clear that they are not going to support two different ways of speaking to drivers.
For KWin such patches do not exist and we have no plans to develop such an adaption as long as the patches are not merged into Weston.The announcement of KDE Neon dev/unstable switching to Wayland by default raised quite a few worried comments as NVIDIA’s proprietary driver is not supported. One thing should be clear: we wo…
- Likes 3
Comment
-
Originally posted by johanb View PostRedshift and screenrecording.
Those are the two showstoppers for me,
Although I don't think 5.11 comes with it, I hope it will be included in 5.12.
- Likes 5
Comment
-
Originally posted by sandy8925 View PostYeah, Martin made it clear that they are not going to support two different ways of speaking to drivers. NVIDIA was aware for years that Wayland was happening, major toolkits finished their Wayland support, GNOME finished porting to it, and then NVIDIA came and said "we want all of you to redo all of that work and do it our way".
Actually, GBM approach is pretty stupid. App tells driver how to fill a frame buffer then driver should convert it to GBM then app passes it to a composer then the composer passes the buffer back to the driver to use it as a texture instead of just using original framebuffer as is. Wayland was designed to fix some flaws of current display system, so Nvidia guys are right when they want to do everything sane way.
Gnome supports eglstreams, Martin is too stubborn to do so, thats all.
You are right, they was aware, but they was aware of Mir too. Nobody have to participate in every new experimental project.
And one practical issue. Xwayland doesn't support glx on nvidia blob. So adding GBM support won't fix anything for Nvidia, it still will be unusable. Until xwayland developers won't add glx for Nvidia (which is unlikely) or most 3d apps will get native wayland support, Nvidia has no reason to hurry.
- Likes 1
Comment
-
Originally posted by bug77 View Post
Nvidia doesn't have a problem. They sell hardware and they have a driver that puts hardware's capabilities in the hands of users. Technically speaking, that's where their responsibility ends. That's how the "problem" looks in Nvidia's eyes and that's why there see no pressure to change.
Meanwhile, I'm stuck with the blob and X. And everything works as well as ever..
Anyway even if they would provide a working implementation accepted by the other graphic developers working well on Plasma-Wayland, Nvidia wouldn't be an option for me and I think for a lot of others as well, they only provide a proprietary driver and they refuse to work with the community (=> signed firmware blob not available for nouveau).Last edited by R41N3R; 11 October 2017, 07:20 AM.
- Likes 5
Comment
Comment