NixOS KDE | 206 Members | |
| 54 Servers |
| Sender | Message | Time |
|---|---|---|
| 4 Mar 2026 | ||
| (are we getting zero-dayed?) | 20:13:38 | |
| 5 Mar 2026 | ||
| From my Security Analysis the PDF seems to be safe. But why would somebody post this? | 11:15:34 | |
| There are URIs which lead to a bank and an insurance company. SO either these are phising sites or a just a badly confused person. | 11:17:55 | |
| There are URIs which lead to a bank and an insurance company. One belonging to a Goverment. | 11:19:06 | |
| There are URIs which lead to a bank and an insurance company. One belonging to a Goverment. So it seems like a legit legal document... but why? | 11:26:18 | |
| I assume they tried to send it to another room | 12:24:28 | |
| But yeah it looks innocuous | 12:24:44 | |
| 6 Mar 2026 | ||
| 11:58:12 | ||
| Good morning :) I'm a NixOS Asahi user, using plasma6. Occaisonally when booting, SDDM fails to start, it happens about 50% of the time. When I use an external display over HDMI, it happens 100% of the time. I've recently come across plasma-login-manager, and I love it, it never fails to start on boot... except when I have an HDMI device plugged in. The systemd service keeps running, but the inner kwin process seems to crash. Since I'm using Asahi, which means that most of the hardware support is reverse engineered, I'm not excluding that this is a hardware issue, but @K900 mentioned that there might still be use in me posting the logs here. I've collected my log journal from a boot where I have HDMI plugged in. What happens on screen is that plasma-login-manager starts, renders the screen on my main (laptop) display, and then quits (it seems to crash), there are no coredumps in /tmp nor in coredumpctl.These are the logs from boot, including those from the apple-dcp module: https://gist.githubusercontent.com/elisaado/b0a471ab0ed9b669ff631723250ce309/raw/dbe418f975f5f5c2e06740db6040543ee5e936fe/gistfile1.txt I hope these logs are useful to anyone, and feel free to reach out if I can help debug or test something <3 | 12:11:52 | |
| That's very interesting | 12:13:11 | |
| Maybe post this in #Plasma Development | 12:13:15 | |
| will do, my poor homeserver jumped to 2GB of RAM usage joining that room do you think simply copy pasting my message is fine? | 12:16:12 | |
| Yes | 12:16:28 | |
| if anyone else stumbles upon this issue, Add an override to plasmalogin with the following content This can be easily done in Nix with | 13:59:24 | |
| 13:59:28 | |
| I don't think that's generally accurate | 14:01:00 | |
Because systemd-modules-load only force-loads modules that are set up in the config | 14:01:15 | |
| It does not handle hotplug | 14:01:20 | |
| hmm true, maybe appledrm is slow to load or reinitializes the /dev/card during loading? | 14:01:58 | |
| 8 Mar 2026 | ||
| 10:08:11 | ||
| 10:08:17 | ||
| 9 Mar 2026 | ||
| 00:47:45 | ||
| 10 Mar 2026 | ||
| 01:46:40 | ||
| 16:42:32 | ||
| 16:43:20 | ||
| 16:43:23 | ||
| Anybody else has/uses KDE Plasma Wayland with SDDM set to autologin + Kscreenlocker set to lock on startup? (Config file bellow). If I use it normally it works fine, but if I try to log-out to login into a another account for example it locks up and doesn't react to anything except CTRL+ALT+F1/2/3 or SSH. | 18:47:33 | |
| * Anybody else has/uses KDE Plasma Wayland with SDDM set to autologin + Kscreenlocker set to lock on startup? (Config file bellow). If I use it normally it works fine, but if I try to log-out to login into a another account for example it locks up and doesn't react to anything except CTRL+ALT+F1/2/3 or SSH.
| 18:47:56 | |
| Is this expected behaviour (ie, me setting incompatible settings) or it should work? | 18:48:41 | |
| Could be some SDDM thing | 18:50:24 | |