I am new to Fedora, I was using a different distro before. It is nearly impossible for me to use my trackpad without this libinput fork:
This fork has 3-finger-drag support, and I was using this without any issue on my previous distro. I built it quite easily, with no errors. (My previous distro was Manjaro)
Now, on Fedora, when I run the command: “ninja -C builddir/” I am getting the following output:
I did install the build dependencies. It was giving me the error nevertheless.
So I tried the option to build without debug gui, it said invalid option. After that I tried with
ninja -C builddir/ -k 2
It finished the job, then I installed it. However after I reboot my machine, GDM didn’t start at all. I am greeted with “Oh no! Something has gone wrong!” screen.
So I switched to TTY and reinstalled libinput with dnf.
So the repo version of libinput is 1.20, the 3-finger-drag fork is 1.19. Problem might be because of this. But as I said, I was using this libinput fork on Manjaro without any issue on Gnome-Wayland.
Everything works after I login to my Gnome-session.
This is where the problem is. GDM gives the famous “Oh no! Something has gone wrong!” screen. I can switch to TTY and start the session with
When build libinput/libinput-git package using meson & ninja, I am having a similar problem.
I can install it. But when I reboot my machine, GDM shows the white screen with “Oh no! Something has gone wrong!”
As I said, I can start session manually and use my machine with the new driver, but this also has several problems (like keychain, some programs are acting strange, etc.)
As I said, the problem is not just about this fork. I am having similar issue when I build the main libinput git version. Plus, I was using this fork with no problem at all on Manjaro.
I will give this topic 3-4 more days. If my problem persists, I will probably switch to an Arch based distro again. But I actually want to stay with Fedora.
Update: I switched to Arch. Built the package with no issue. Everything is working.
I don’t know what was causing the issue while using Fedora. It was something about GDM. GDM was quite vulnerable on Fedora, don’t know why.
I wasn’t able to customize the login manager with the gdm-settings GUI tool. Any change was breaking the GDM. Now, on Arch, I can customize GDM with this tool.
Anyway, when the issue is solved, I can go back using Fedora. It was handling everything else perfectly fine. But not this one. And this was crucial to me.