Package Details: kdisplay-git 6.0.0_r1602.ga606d52-2

Git Clone URL: (read-only, click to copy)
Package Base: kdisplay-git
Description: App and daemon for display managing by the KWinFT project (kscreen fork)
Upstream URL:
Licenses: LGPL
Conflicts: kdisplay
Provides: kdisplay
Submitter: QuartzDragon
Maintainer: IslandC0der (chaotic-aur)
Last Packager: IslandC0der
Votes: 0
Popularity: 0.000000
First Submitted: 2020-05-26 08:39 (UTC)
Last Updated: 2024-03-27 01:39 (UTC)

Latest Comments

1 2 Next › Last »

ms178 commented on 2023-02-03 23:37 (UTC) (edited on 2023-02-03 23:39 (UTC) by ms178)

On the kscreen/kdisplay-discussion I'd like to add that in my testing, performance of several game benchmarks with my Vega 56 are significantly worse when using kscreen or when both are installed next to each other (e.g. Company of Heroes 2, which is very CPU-sensitive on modern hardware loses around 5-7 %). This seems to be a problem with kscreen. Hence I recommend performance-oriented people to use wrapland/disman/kdisplay and to delete kscreen even if they want to keep using stock Kwin. I also limit my screen refresh rate to 119,997 Hz and the in-game resolution in most games to 1080p despite having a 1440p/165 Hz monitor, as that lower refresh rate keeps it in sync with most game engines and provides a smoother experience for me this way.

IslandC0der commented on 2021-11-28 23:01 (UTC)

Alright, fair enough :D

sl1pkn07 commented on 2021-11-27 18:30 (UTC) (edited on 2021-11-27 18:33 (UTC) by sl1pkn07)

in short. yes (the dependencies)

in long. install kwin or kwinft when one of two is broken, and keep the dependencies intact installed

IslandC0der commented on 2021-11-21 20:37 (UTC)

Sorry, I understand what you mean now.

But why would you want to have both kscreen and kdisplay installed?

kscreen is used by kwin, and kdisplay is used by kwinft; therefore, if you want to switch to kwinft, you don't need kscreen anymore, so it can safely be removed (that's why it's in conflicts()).

Do you want to have both compositors installed?

sl1pkn07 commented on 2021-11-18 15:34 (UTC)

tested removing kscreen from conflicts(). build ands install ok without removing kscreen. so set kscreen in conflicts is not needed

sl1pkn07 commented on 2021-11-18 15:19 (UTC) (edited on 2021-11-18 15:21 (UTC) by sl1pkn07)

kdisplay-kwinft and kscreen

if i whant swicth to kdisplay-git, this remove kscreen

IslandC0der commented on 2021-11-18 01:26 (UTC)

Which 2 packages can be installed together?

IslandC0der commented on 2021-11-18 01:25 (UTC)

I know, I'm saying this package conflicts with kscreen, kdisplay, and kdisplay-kwinft

sl1pkn07 commented on 2021-11-18 01:16 (UTC) (edited on 2021-11-18 01:24 (UTC) by sl1pkn07)

im talking about kscreen, not kdisplay

kdisplay-git sets kscreen as conflicts. but kscreen-kwinft not have this requeriment and can be installing together

IslandC0der commented on 2021-11-17 19:16 (UTC)


Both this package and kdisplay-kwinft provide and conflict with kdisplay, so they automatically conflict with each other (if you try installing them together, it won't work).