Package Details: disman-kwinft 5.25.0-1

Git Clone URL: https://aur.archlinux.org/disman-kwinft.git (read-only, click to copy)
Package Base: disman-kwinft
Description: Qt/C++ display management library
Upstream URL: https://gitlab.com/kwinft/disman
Licenses: LGPL
Conflicts: disman
Provides: disman
Submitter: abelian424
Maintainer: abelian424
Last Packager: abelian424
Votes: 7
Popularity: 0.000205
First Submitted: 2020-05-26 07:55 (UTC)
Last Updated: 2022-06-16 14:53 (UTC)

Latest Comments

abelian424 commented on 2021-05-20 02:27 (UTC) (edited on 2021-05-20 02:31 (UTC) by abelian424)

Hi @IslandC0der, my naming convention has been criticized by Roman Gilg as being unconventional, so I don't mean to suggest that you should add kwinft to the package name. However, I thought it was inconvenient that kwinft, kdisplay, disman, and wrapland had a dependency chain but wouldn't show up under one search term, so I added the -kwinft suffix so that newcomers would find all the packages more easily. An alternative is just to mention kwinft in the description, as I think most AUR helpers also search that field.

IslandC0der commented on 2021-05-19 20:48 (UTC)

Hi, I adopted both disman-git and kdisplay-git, which are essentially the unstable counterparts of disman-kwinft and kdisplay-kwinft. However, it's a bit confusing, since yours have the "-kwinft" suffix but mine don't.

Therefore, I would like to reach some consensus so as make it consistent; what should we do? Which naming convention do you think makes more sense? If it's preferable, I'd be happy to use yours :)

abelian424 commented on 2021-02-19 10:40 (UTC)

@jnko make sure all kde components are updated to 5.21 and that you are not using git releases. I had this happen when disman 0.520.1 was released and expected wrapland to be the same version. Another version mismatch seems to be the likely explanation.

jnko commented on 2021-02-18 08:34 (UTC) (edited on 2021-02-18 08:35 (UTC) by jnko)

I've installed kwinft, kdisplay-kwinft, disman-kwinft and wrapland-kwinft, all v5.21.

Unfortunately I'm not able to configure my two monitors neither grafically nor with dismanctl. I already completely cleard the disman configuration without success.

dismanctl -o

disman: Failed to request backend: unknown error disman.ctl: Received initial config has error. disman.ctl: Invalid config.

journalctl

Feb 18 09:20:50 XPS7590 disman_backend_launcher[33205]: disman.backend.wayland: Connection to Wayland server timed out. Does the compositor support output management? Feb 18 09:20:50 XPS7590 disman_backend_launcher[33205]: disman.backend.wayland: "kwayland" backend could not be aquired in time. Feb 18 09:20:21 XPS7590 plasmashell[33109]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

Any suggestions about this? Is it running fine on your installation?

abelian424 commented on 2021-01-01 19:58 (UTC)

BluePeril - done. Try installing again.

BluePeril commented on 2021-01-01 13:41 (UTC)

Would you please at plasma-framework as dependency? Otherwise the package will not build in a clean environment

abelian424 commented on 2020-12-15 16:18 (UTC)

On my machine, at least, updating to 0.520.1 does not allow kdisplay to configure displays. Since on of my "monitors" is a VR headset, this means that I had to manually downgrade disman to the previous version in order to get a usable display setup. I imagine this is a niche problem, and most people with multiple monitor setups will be fine with the kdisplay defaults.

abelian424 commented on 2020-09-30 15:44 (UTC)

@sl1pkn07 yeah, for now you can use the disman-git package. The difference between my packages and QuartzDragon's is just that I try to build the release versions rather than the rolling git updates. Right now I'm using kwinft, kdisplay-kwinft, and wrapland-kwinft with disman-git, and it works fine.

sl1pkn07 commented on 2020-09-29 15:35 (UTC)

try to build 0.520-beta.0 lead to compile fail