Barrier has not been updated for a while, the new kvm looks like Deskflow : GitHub - deskflow/deskflow: Share a single keyboard and mouse between multiple computers. · GitHub
Successfully built 1.2.6 on local and usable with Xlibre with both ROME and ROCK 
#!/bin/bash -ev
cd ~/Downloads/
wget https://github.com/deskflow/deskflow/archive/refs/tags/v1.26.0.zip
unzip ./deskflow-1.26.0.zip
cd ./deskflow-1.26.0
# Install most of the dependencies
sudo dnf in task-devel
sudo dnf install lib64xkbcommon-x11-devel lib64xkbui-devel lib64xtst-devel gtk-engines2-devel qt6-qttools-devel lib64Qt6Network-devel lib64Qt6NetworkAuth-devel lib64Qt6Xml-devel lib64Qt6WebEngineWidgets-devel qt6-qtbase-theme-gtk3 lib64vulkan-devel lib64ei-devel lib64portal-devel lib64Qt6Test-devel lib64xrandr-devel lib64xinerama-devel lib64xkbfile-devel
# Check dependencies
mkdir build
cd build
cmake ..
# Build
make
# Install in /usr/local/ by default
sudo make install
It’s a pain to kill and restart the process as it was made to avoid multiple instances.
After connecting and creating the config for two computers - I had to restart at least three times in a row - the easiest way I found is to skip the GUI by using the command line like this :
The computer sharing is mouse / keyboard :
/usr/local/bin/deskflow-core server --new-instance
The computer using the mouse / keyboard from an other machine :
/usr/local/bin/deskflow-core client --new-instance
I haven’t got the chance to test with Wayland for now. Might help
At present, we don’t have xlibre on Rock. It won’t be until the next release. All packaging needs to be tested on Cooker because of how we manage releases.
When Cooker is stable, it becomes the next ROME. When ROME is stable, it becomes the next Rock.
1 Like
My bad @zeroability I meant built separately on local on both machine, working with Kwin (X11) from OM Rocks 6 and Kwin (Xlibre) from OM Rome 6. I didn’t built Xlibre on Rocks for sure 
Looking at the other post on the forum explained by @rugyada Barrier still exists on the other (non free?) repo :
Tested with my current config as well, it works actually. For X users like me, Barrier is actually still solid 
The point is, we don’t build packages in anything but Cooker with the mild exception for security issues or major breaking in Rock or ROME. So, we don’t support using things built in Cooker in the other releases, either.
It might still be in extra, but probably needs a maintainer.
1 Like
Rodger @zeroability about the branches 
I have to make a effort to express myself properly 
I was sharing the news / test if someone was interesting to use it before pushing a real proper package request.
About Barrier, after digging a big the active developers moved on to Input-leap, already packaged in OpenMandriva. Guess we can drop the support ?
1 Like
I understand, and appreciate the enthusiasm. We just don’t want people getting the idea that it will work properly in non-Cooker releases.
That is something we normally deal with through attrition. If packages have proper maintainers, it would be discovered much quicker. Sometimes we just have to wait until the build fails in ABF, or a significant amount of time has passed since it was built at all before we discover the software is abandoned.
1 Like
ok totally understand. In this case I will avoid sharing local build tests - in this forum at least - so false positive / wrong ideas won’t be spread and put more effort on learning ABF 
For the rest guess it’s time for me to catch you later more on Matrix.
Thank you for the information and have a wonderful day or night . 
1 Like