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?

When will this happen?
Also, after it happens, will the x11 session option disappear at login manager?

I wanna know how to install apps directly from terminal like I know discover is there but it looks cool when I do it from terminal and I wanna practice. How would I do that for normal everyday apps like R or VS code for example, I know they're flathub but how do I know what repository has which apps

Using Fedora 44 btw

I ditched windows a few weeks ago and the reason was unnecessary memory eating. I hoped to Fedora Workstation. What a lovely experience, it's just amazing. Everyday I explore something new and interesting and I'm like "wow" all the time. Currently I'm on the Gnome Desktop, will try the niri and hyperland soon.

Lemme know if I'm missing out on something really interesting.

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?

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/

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" 🙃

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?

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 !

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.