| 24 Mar 2026 |
 Winter | like... 2w ago? | 14:20:13 |
 K900 | Hmm | 14:22:02 |
| K900 | Sus | 14:22:03 |
| 26 Mar 2026 |
|  @meadow_weasel:matrix.org left the room. | 15:04:35 |
| 27 Mar 2026 |
|  smoothie_one joined the room. | 13:08:29 |
| 31 Mar 2026 |
|  Michaili K joined the room. | 16:41:39 |
| 3 Apr 2026 |
|  Hadi changed their display name from Hadi Chokr to Hadi. | 17:50:30 |
| 6 Apr 2026 |
|  Eli Saado changed their profile picture. | 10:36:29 |
| Eli Saado changed their profile picture. | 10:42:24 |
| Eli Saado changed their profile picture. | 11:03:15 |
| Eli Saado changed their profile picture. | 11:04:10 |
| Eli Saado changed their profile picture. | 11:05:03 |
 mr-qubo | Is anyone else trying to use Firefox. On my machine it works very bad. Sometimes freezes for a few minutes and it also slows down entire desktop. Restarting Firefox helps so I have to reatart Firefox every 1-2 dayd. I wonder if it's Nixos or KDE specific issue or these are general problems with Firefox? | 13:54:59 |
| mr-qubo | * | 14:00:31 |
| mr-qubo | * | 14:02:41 |
| K900 | No issues here | 14:03:56 |
 whispers [& it/fae] | if it's specifically the browser chrome freezing that's a bug fixed in tomorrow's release that affects more than just kde | 14:07:08 |
| whispers [& it/fae] | * if it's specifically the browser chrome/menu bar freezing that's a bug fixed in tomorrow's release that affects more than just kde | 14:07:30 |
| whispers [& it/fae] | * | 14:16:00 |
| mr-qubo | Nope, entire browser. KDE makes the window grayed out. | 14:29:37 |
 shapr | In the KDE settings for "Wi-Fi & Internet" does the connection priority value also affect which interface is the default for network traffic?
My laptop has Wi-Fi and Ethernet, and "Wired Connection" had priority -100 while the Wi-Fi had priority -1.
If I change the Ethernet priority to the highest, will it handle traffic by default? | 14:55:25 |
| K900 | No | 15:05:49 |
| K900 | It only affects autoconnect priority | 15:05:52 |
| K900 | Not route metric | 15:05:53 |
| shapr | Thank you! | 15:18:06 |
| 8 Apr 2026 |
|  @bmanuel:matrix.org left the room. | 03:11:20 |
| 10 Apr 2026 |
| Eli Saado | In kscreenlocker (not PLM/SDDM), when configuring PAM-u2f, the required rules get automatically added to /etc/pam.d/kde-fingerprint and it simply works. However, when the user completes the u2f UV/UIF, kscreenlocker shows an additional "unlock" screen with a single button that says "unlock", which when pressed, unlocks the session.
The fix for this according to the arch wiki (https://wiki.archlinux.org/title/Universal_2nd_Factor, under SDDM/KDE) is to use /etc/pam.d/kde-fingerprint instead of pam.d/kde (or possibly /etc/pam.d/kde-smartcard according to a reddit thread).
Is there a Nix native way of managing the /etc/pam.d/kde-fingerprint file? | 16:29:57 |
| K900 | Those should be configured correctly by default | 16:32:41 |
| K900 | https://github.com/NixOS/nixpkgs/blob/nixos-unstable/nixos/modules/services/desktop-managers/plasma6.nix#L344 | 16:33:22 |
| Eli Saado | right, but they are only set if fprintd or p11 are enabled, even though u2f can do biometric things without fprintd.
though reading that source did help me find a solution (so thank you <3),
services.kde.u2fAuth = false;
services.kde-fingerprint.u2fAuth = true;
(disabling u2f in the kde service is needed as it has priority over the u2f in the kde-fingerprint service) | 16:56:40 |
