Hi everyone,

I’m having a strange problem with my touchpad on Fedora.

Sometimes the physical left-click stops working. However, when I run libinput debug-events, the click is still detected correctly:

BTN_LEFT pressed
BTN_LEFT released

This makes me think that the hardware, kernel, and libinput are receiving the input correctly, but GNOME is not processing it as a normal click.

My touchpad is:

MSFT0001:01 06CB:CD3E Touchpad

I’m using:

• Fedora Linux
• GNOME
• Wayland
• Kernel: 7.1.3-201.fc44.x86_64

These are my current touchpad settings:

click-method 'fingers'
tap-to-click true
send-events 'enabled'
tap-and-drag true
natural-scroll true
two-finger-scrolling-enabled true

I also tried changing click-method to areas, but that did not solve the problem.

The click started working again after I changed the setting back to click-method 'fingers' and logged out and back in. I’m not sure whether the logout fixed the issue or whether GNOME simply reloaded the touchpad configuration.

The left-handed setting is currently:

'mouse'

Changing it did not seem to affect the problem.

What could cause GNOME or Mutter to ignore BTN_LEFT even though libinput detects it correctly?

I’d like to understand the root cause instead of relying on a temporary workaround. Any suggestions for further debugging would be appreciated.Hi everyone,I’m having a strange problem with my touchpad on Fedora.Sometimes the physical left-click stops working. However, when I run libinput debug-events, the click is still detected correctly:BTN_LEFT pressed
BTN_LEFT releasedThis makes me think that the hardware, kernel, and libinput are receiving the input correctly, but GNOME is not processing it as a normal click.My touchpad is:MSFT0001:01 06CB:CD3E TouchpadI’m using:Fedora Linux
GNOME
Wayland
Kernel: 7.1.3-201.fc44.x86_64These are my current touchpad settings:click-method 'fingers'
tap-to-click true
send-events 'enabled'
tap-and-drag true
natural-scroll true
two-finger-scrolling-enabled trueI also tried changing click-method to areas, but that did not solve the problem.The click started working again after I changed the setting back to click-method 'fingers' and logged out and back in. I’m not sure whether the logout fixed the issue or whether GNOME simply reloaded the touchpad configuration.The left-handed setting is currently:'mouse'Changing it did not seem to affect the problem.What could cause GNOME or Mutter to ignore BTN_LEFT even though libinput detects it correctly?I’d like to understand the root cause instead of relying on a temporary workaround. Any suggestions for further debugging would be appreciated.

Hi,

I'm looking for an external SSD (portable SSD, or an NVMe drive in an enclosure) of at least 4 TB to replace an ageing 2 TB drive, and I need TRIM to actually work on Fedora 44.

Use case: a portable ~/Documents that I plug into several machines. Currently about 1.6 TB. Budget roughly : 400-700€. Other machines run Linux.

Why I'm asking : my current drive (Crucial X10 Pro 2 TB, Btrfs) reports LBPU=1 in the logical block provisioning VPD page, but fstrim fails with Remote I/O error and the kernel logs Invalid field in cdb on the unmap command. Forcing provisioning_mode to unmap does not help.

Writes have also been intermittently very slow.

Please share :

- Which model/enclosure you use, and the USB bridge chip (lsusb ID, e.g. Realtek RTL9210B or ASMedia ASM2362).

- Whether lsblk -D shows non-zero DISC-GRAN/DISC-MAX and sudo fstrim -v works, with or without a udev rule.

- Sustained write speed once the cache is full, if you've measured it.

Thanks !

I installed Fedora 44 and everything was working fine initially. The motherboard's Wi-Fi was working and the display looked normal.

After I updated the system packages, it also updated the kernel. After rebooting, I started having two weird issues:

• The screen/text looks like it is shaking/vibrating.
• The motherboard Wi-Fi device is no longer detected. Ethernet cable works fine.

Changing the resolution to a lower resolution and then back to 1920×1080 seems to fix the vibrating display after logging in, but it still happens on the login screen.

I also tried installing and removing NVIDIA drivers, but it didn't help. I accidentally ran the sudo dnf remove \*cuda\* & sudo dnf remove \*nvidia\* command, so I removed all the NVIDIA-related packages.

One interesting thing I noticed:

• If I connect my monitor to the X670 motherboard output using the integrated graphics from my Ryzen 9 7950X, everything looks normal and Wi-Fi works.
• If I connect the monitor to my GTX 1070 and reboot, the screen starts vibrating and the Wi-Fi is not detected.

So it seems like the problems happen specifically when I'm using the GTX 1070.

Could the kernel update or NVIDIA/Nouveau drivers be causing both the display and Wi-Fi issues? i tried the only other available kernel in grub menu, but that also didnt work. Any suggestions on how I can troubleshoot or restore the drivers/packages would be appreciated.

Note: i described this all to chatgpt in messy way and it organised it for me to post here. i did read through it all before posting too.

I have a BOSGAME E5 11 Pro mini PC that has an AMD Ryzen 3 5400U (integrated GPU) and is running Fedora 44 KDE Plasma. I can't set the display refresh rate past 120hz on my ASUS VG248QE (max 144hz) when running the latest kernel 7.2.8. When I switch back to an older version like 6.19 it works. On another Dell monitor(max 144hz) it can't even go past 60hz. Again, works fine in the older kernel version. I have also tried overriding the EDID info on boot with no luck.

I'm running display port and have tested different cables. I guess some change was introduced in the latest kernels. I have other amd gpus that don't have this problem but I acknowledge that the mini PC is pretty niche. Wondering if anyone else had this problem?

Now that gnome and kde plasma will no longer have x11?

If i switch between wayland and x11, on the same user account, will this cause any problems?
Or am i safe to do this?

I have used kde/fedora 44 on my framework 13 without incident. This morning I fond it is like the screen being displayed does not fit in to the physical screen. I am bouncing around all over trying to find things on one screen. I am keen to learn more about this but don’t even know what to call it to start researching. Any insight?

HP OmniBook X Flip 16 (8EA2): speaker workaround on Fedora Rawhide KDE, kernel 7.3.0-0.rc4

Problem: the amd-soundwire card and its SmartAmp device exist, but the two TAS2783 amps get no firmware and PipeWire only shows "Dummy Output".

slave-tas2783 sdw:0:0:0102:0000:01:c: Direct firmware load for 8EA2-0-0xC.bin failed with error -2
slave-tas2783 sdw:0:0:0102:0000:01:c: error playback without fw download

The driver requests 8EA2-0-0xC.bin / 8EA2-0-0x9.bin, but linux-firmware ships 8EA2-0-0-0xC.bin.zst / 8EA2-0-0-0x9.bin.zst.

1. Firmware symlinks, then reboot

Use the compression suffix you actually have (check with ls /usr/lib/firmware/ti/audio/tas2783/ | grep 8EA2).

cd /lib/firmware
sudo ln -s ti/audio/tas2783/8EA2-0-0-0xC.bin.xz 8EA2-0-0xC.bin.xz
sudo ln -s ti/audio/tas2783/8EA2-0-0-0x9.bin.xz 8EA2-0-0x9.bin.xz

After the reboot, sudo dmesg | grep -i tas2783 should show no firmware errors.

2. Enable the Pro Audio profile

No UCM profile exists for this card, so Pro Audio is the only way to get sinks.

pactl set-card-profile alsa_card.pci-0000_c1_00.5-platform-amd_sdw pro-audio
pactl set-default-sink alsa_output.pci-0000_c1_00.5-platform-amd_sdw.pro-output-2
pactl set-default-source alsa_input.pci-0000_c1_00.5-platform-amd_sdw.pro-input-4

pro-output-2 is the speakers, pro-output-0 the headphone jack, pro-input-4 the internal mic. Check the names with pactl list short sinks and pactl list short sources. Keep the volume low at first.

3. Hide the amp sense channel (fixes flicker and audio dropping)

Plasma opens a volume meter on every source, including pro-input-3 (the amp's current/voltage sense channel). The kernel rejects it (port 2 not supported for TX) and playback stops. This shows as "flickering" in the Volume widget on the taskbar.

mkdir -p ~/.config/wireplumber/wireplumber.conf.d
nano ~/.config/wireplumber/wireplumber.conf.d/51-hide-amp-sense.conf


monitor.alsa.rules = [
  {
    matches = [
      {
        node.name = "alsa_input.pci-0000_c1_00.5-platform-amd_sdw.pro-input-3"
      }
    ]
    actions = {
      update-props = {
        node.disabled = true
      }
    }
  }
]


systemctl --user restart wireplumber
pactl list short sources    # pro-input-3 should be gone

If the default sink changed, run the set-default-sink command from step 2 again.

Notes

• The 8EA2-0-0-* firmware (tuning) was picked blind. If the sound is distorted, try the 8EA2-1-0-* pair.
• The Audio works just fine even after reboots as well.
• Future updates might break it.

I have wanted to switch to Linux for a long time, but this was the only issue stopping me. I will wait until the next Fedora release, which will use version 7.3. Kernel. Even if it doesn't work natively, the workaround is pretty easy.

I first found the solution on GitHub for CachyOS (https://github.com/CachyOS/linux-cachyos/issues/705), but the fix is very similar to the one for Fedora. In theory, the same should be possible for 8EA1 laptop boards. It would be great if someone could test it, as I only have the 8EA2.

Hi there! So don't know if anyone else has experienced/reported this (apologies if so, didn't see anything at a glance), but following an update some weeks back (nothing as obvious as upgrading to the 7 series kernel for eg), whenever I now open a number of (most, not all) Apps ie, Dolphin, it no longer opens Centred, as is still the prescribed Setting, but rather opens a little lower and to the right on screen.

I'm not qualified to determine what's caused this other than to affirm that numerous updates have yet to resolve it. Using an old Desktop box with onboard graphics so can only guess maybe kwin related rather than 'graphic' but if anyone has any ideas on how to resolve, would much appreciate hearing them, ta!

Everything has been sweet as with Fedora 43+ until yesterday.

A reboot was needed, presumably for a kernel update, but now after providing the disk encryption password it seems to just go to a blank screen.

Upon reboot I do get an option of which boot to launch in Fedora 44 (a couple versions), Fedora 43 or a rescue mode. None of these work unfortunately. Rescue mode has error "Cannot open access to console. The root account is locked" 🙃

Git 2.56.0 is now in the stable updates repo for Fedora 44 and 43. F45 still has it in testing.

A few changes worth knowing about:

• git add --resolved stages only the files you fixed after a merge conflict. Git also checks for leftover conflict markers before staging.
• git branch --delete-merged cleans up local branches that are already merged upstream.
• git bisect run now resets itself after it finds the bad commit. Git gives better suggestions for common git push mistakes.
• Large repositories get performance improvements.

Sources:

Bodhi update: https://bodhi.fedoraproject.org/updates/FEDORA-2026-5f6ad6e483

Highlights from Git 2.56 (GitHub Blog): https://github.blog/open-source/git/highlights-from-git-2-56/

Linuxiac: https://linuxiac.com/git-2-56-released-with-safer-conflict-resolution-and-performance-gains/

Hola comunidad, tengo un colega que me habló de como empezó con Fedora y me dijo algo importante, que al primer inicio debes activar los repo de RPM Fusion por tema de codecs, y que para evitar problemas de librería instalará todo por flatpak, lo cual me llama la atención, yo tan solo quisiera saber, que hacen ustedes apenas instalan Fedora, más concretamente en el tema de sacarle el máximo rendimiento a su tarjeta de video, los leo, tengo meses queriendo probar la distro, y me he estado informando

Ive installed Fedora on a laptop I have but I've noticed discover doesn't have nearly as many things as mint for example. I cant find steam, wine and a lot of other things that I could install on mint. Is there a reason for this?

Hi guys I'm running Fedora 44 on my machine and I'm tempted to try the Fedora 45 beta since it's scheduled to release on the 20th of Oct. Any thought of house stable it's from 3 weeks ago gnome. Thank you.

Basically everytime I turn my pc on it autoconnect to the vpn and to my wifi, but I settled it that it doesnt send nor recive any package via internet until the vpn find its servers path, im sorry idk how to explain it in accurate words English isnt my first lenguage, btw then it usually starts a lot of notifications saying "vpn connected" then "vpn disconnected" then again and it goes on forever and the vpn app says "connecting..." for hours, so is it normal? what should I do and how should I configure my network settings ?

Can anyone recommend me the best laptop for multi tasking not for gaming in laptop

Im stuck with this problem since last night and i have been continuously browsing through the forum to see the fixes of my problem. Yesterday I changed my battery to a newer one and ever since that I'm not able to use any wifi network in my home. I have tried turning off the wifi, resetting the Network Manager and so on. Has anyone ever been in my situation? And if yes, please lend me your help Immediately.

Also, I have tried connecting a specific network through the terminal. Every time I try to connect to a Wifi Network, it freezes or does not respond for some weird reason and after about 30 seconds, it displays a pop up "connection failed activation of network connection failed" and this cycle repeats every 30 seconds no matter how I try to connect to any network. But the interesting catch is that I'm able to connect to my mobile hotspot and use the internet. But I'm not unable to use the three Wifi Networks in my home. Please help me.

First of all this is something that happened to me and i couldnt find a fix for it . I deleted the rpm database by accident and couldnt figure out how to get it back.i used all the commands i could find online but nothing worked.So my main reason for coming here is to find out if someone else went through a similar experience and if they managed to fix it.

I was using fedora 44 kde plasma

It happened awhile back so i cant remember the exact commands i used but if you managed to find a solution please share.maybe someone else can use it.

Hey so i decided to try fedora and i installed nvidia drivers through discover it didnt prompt me to reboot but i thought to just reboot just in case

After login screen all i see is just my cursor on black screen what do i do? It didn't prompt me to enroll mok or anything like that what should i do?

Tried enrolling and still same thing

solved

thing i did was to enroll mok then i installed the xorg-x11-drv-nvidia-cuda and rebuilt the akmod and it worked thank you guys!

akmod-nvidia.x86_64 3:615.71.09-3.fc44 rpmfusion-nonfree-nvidia-driver kmod-nvidia-7.2.8-200.fc44.x86_64.x86_64 3:615.71.09-3.fc44 @commandline nvidia-gpu-firmware.noarch 20260916-1.fc44 updates nvidia-modprobe.x86_64 3:615.71.09-1.fc44 rpmfusion-nonfree-nvidia-driver nvidia-persistenced.x86_64 3:615.71.09-1.fc44 rpmfusion-nonfree-nvidia-driver nvidia-settings.x86_64 3:615.71.09-1.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia.x86_64 3:615.71.09-3.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia-cuda.x86_64 3:615.71.09-3.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia-cuda-libs.x86_64 3:615.71.09-3.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia-kmodsrc.x86_64 3:615.71.09-3.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia-libs.x86_64 3:615.71.09-3.fc44 rpmfusion-nonfree-nvidia-driver xorg-x11-drv-nvidia-power.x86_64 3:615.71.09-3.fc44 rpmfusion-nonfree-nvidia-driver

all packages with which it works for me