New user experience with Fedora 43 KDE

Couple of notes and issues seen by me and my girlfriend, while setting her up on Fedora (and Linux) for the first time.

I’ve went with the KDE spin, even though I normally use Xfce, for a more polished desktop experience, but still familiar to someone coming from Windows.

Anaconda installer, and installation process

I remember reading about certain changes made to the installer, though those obviously were mostly non visual.

I consider it a big miss, that still on the installation screen the real estate isn’t used in a better way to onboard the new users to the system. The KDE welcome splash screen would work better embedded on this screen, because it took around 15 minutes to do the installation on the old laptop.

I’d like to see the option of bypassing password setting for the user account. Somehow I couldn’t proceed without setting a password, even if an encrypted disk was configured. (To me it feels that empty passwords and an “auto-login” checkbox make sense here.)

First boot notes

The laptop took around 2½ minutes to boot up. (tpm related systemd timeouts which I’ve disabled, and a PITA to fix due to LLM gaslighting)

The fact that it defaults to a 10pt font for the desktop is something… I don’t know if only young users are the intended audience, but that should be generally bumped up to 12pt at the very least!

I know the screen of this laptop sucks, but doesn’t look as washed out as Fedora made it seem on start. (tried different color profiles) Which weren’t a problem, but in the new Plasma I don’t see any gamma correction slider. (I’ve switched the system back to X11, just because I could hack something up with xrandr.) (I’ve read about wlrandr after the fact.)

Happy to see that with Plasma now single-click doesn’t open things by default. Always such an unusual default to get used to.

Day to day KDE usage notes

Whoever made the decision to switch updates to run at boot, made a bad call. Happy to find a way to turn those off, and I hope the option stays there in the future. When a user starts up their computer I’m pretty sure they want to use the computer!

Most of her daily usage can be surmised as internet browsing and photo management across different external media.

Windows partitioned disk in an external usb-connected enclosure is mounted read-only. I don’t know yet if this is something that can be changed through configuration or I’ll have to setup custom udev scripts to have it mounted properly.

What is the protocol over which digital cameras are mounted in Kde? (similar to smartphones MTP protocol?) Whatever it is, it opens up in a way that is hard (if not impossible) to share files directly from this “mount” (a camera: prefix if I recall correctly), but worse is the fact that thumbnails don’t seem to get generated in this mode.

Is there anything in the works in the KDE land to globally get a grip with deletion requests on different disks? I think it’s a very bad experience to have someone try to manage their photos on an SDCard, through Gwenview, and get random error messages about the trash folder when trying to delete a file, and then having to teach them to change their muscle memory to shift+del.


Might be worth raising some of these UX issues upstream in KDE and Fedora?

Encrypted disk is for security when the system is powered off.
Account password is for security while the system is running.

Having an encrypted disk does not imply a password is not requited,
that is a users decision.

Thanks for the reply Barry. I’m aware of the distinction. Not being given a choice to go “password-free”, in some way or another, goes against what a user decision might be in a casual user setup.

There is a choice, though obviously not at install.

The AI of Google says:
"To log in to Fedora without a password, enable automatic login via GNOME Settings (Users > Automatic Login ON) or edit /etc/gdm/custom.conf to include AutomaticLoginEnable=true and AutomaticLogin=username. Alternatively, you can set an empty user password using the passwd -d username command. "

Thank you Uwe for trying to help. Do note that KDE uses sddm (at least until plasma-login-manager becomes the norm) and not gdm, and that is the way I sorted it out before.

Could you let the rest of us know how you did that, so we all might benefit from it. Thank you.

That’s always the first thing I change after an install: set 1-click to open files and folders. I really hate that nervously double-clicking. I do this already from around 1991 when I started with Windows 3.1.

1 Like

That would be in KDE’s “System Settings” under “Software update”.


Since I’m posting about workarounds, for the TPM related issue I was seeing these errors within the logs

Jan 31 15:26:31 fedora kernel: Non-volatile memory driver v1.3
Jan 31 15:26:31 fedora kernel: Linux agpgart interface v0.103
Jan 31 15:26:31 fedora kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xcd958000-0xcd958fff flags 0x200] vs cd958000 4000
Jan 31 15:26:31 fedora kernel: tpm_crb MSFT0101:00: error -EBUSY: can't request region for resource [mem 0xcd958000-0xcd958fff]
Jan 31 15:26:31 fedora kernel: tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16

Jan 31 15:27:16 fedora systemd[1]: dev-tpm0.device: Job dev-tpm0.device/start timed out.
Jan 31 15:27:16 fedora systemd[1]: Timed out waiting for device dev-tpm0.device - /dev/tpm0.
Jan 31 15:27:16 fedora systemd[1]: dev-tpm0.device: Job dev-tpm0.device/start failed with result 'timeout'.
Jan 31 15:27:16 fedora systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start timed out.
Jan 31 15:27:16 fedora systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.
Jan 31 15:27:16 fedora systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start failed with result 'timeout'.

Masking those device units didn’t disable the tpm check issue, and instead I had to change my Kernel commandline to include systemd.tmp2_wait=false and regenerate grub with sudo grub2-mkconfig -o /boot/grub2/grub.cfg