| 18 May 2026 |
 K900 | Does that come with custom window decorations? | 19:46:39 |
 aktaboot | it does yea | 19:46:54 |
| K900 | Try turning those off maybe | 19:46:58 |
| aktaboot | heh turning them off also crashed | 19:47:46 |
| K900 | That's a sign of something | 19:47:57 |
| K900 | Possibly | 19:48:00 |
| aktaboot | yeah will try to see if i can reproduce with the breeze ones | 19:48:24 |
| aktaboot | also, how can i check which upstream commit your PR is referencing? | 19:48:46 |
| K900 | Upstream commit of what? | 19:49:10 |
| K900 | Nixpkgs? | 19:49:11 |
| aktaboot | kwin | 19:49:23 |
| K900 | Whatever the 6.6.90 tag is | 19:49:50 |
| aktaboot | okay thanks | 19:50:04 |
| aktaboot | yeah your educated guess was correct! it most definitely seems to be the window decorations! | 20:02:03 |
| K900 | OK, so now the next question | 20:10:48 |
| K900 | Do you know if those decorations are custom code or just aurorae? | 20:10:59 |
| aktaboot | no idea | 20:11:30 |
| aktaboot | they seem to be aurorae | 20:12:08 |
| aktaboot | https://github.com/vinceliuice/Layan-kde/tree/master/aurorae/themes/Layan | 20:12:38 |
| K900 | Yeah OK then we're probably looking at an aurorae bug | 20:12:53 |
| aktaboot | I opened an issue on kde.org, will update the issue with this info then! | 20:16:22 |
| 20 May 2026 |
 Grimmauld (any/all) | cc @K900 :
github.com/NixOS/nixpkgs/issues/513970
Turns out plasma-login-manager currently attempts to load pam modules just by name, no from an absolute path... This is horrible and awful and just randomly exploded due to apparmor assertions, but i am not sure what else may be affected.
I am currently building nixosTests.plasma6 with the paths patched, PR will be up soon, but figured i'd give you a poke here too | 14:47:22 |
| Grimmauld (any/all) | cc @K900 :
https://github.com/NixOS/nixpkgs/issues/513970
Turns out plasma-login-manager currently attempts to load pam modules just by name, no from an absolute path... This is horrible and awful and just randomly exploded due to apparmor assertions, but i am not sure what else may be affected.
I am currently building nixosTests.plasma6 with the paths patched, PR will be up soon, but figured i'd give you a poke here too | 14:47:29 |
| Grimmauld (any/all) | cc @K900 :
https://github.com/NixOS/nixpkgs/issues/513970
Turns out plasma-login-manager currently attempts to load pam modules just by name, not from an absolute path... This is horrible and awful and just randomly exploded due to apparmor assertions, but i am not sure what else may be affected.
I am currently building nixosTests.plasma6 with the paths patched, PR will be up soon, but figured i'd give you a poke here too | 14:47:38 |
| K900 | Uhhh | 14:48:29 |
| Grimmauld (any/all) | That was my reaction too | 14:48:47 |
| K900 | Yeah it does | 14:48:48 |
| K900 | Is that a problem? | 14:48:59 |
| Grimmauld (any/all) | It breaks an assertion we have with apparmor in pam, which is how it was noticed. I didn't dig through pam enough to judge how else it may break. like, custom definitions to pam package? Overrides? does it find the modules at all? (probably does or it'd have exploded earlier, but i don't like this) | 14:50:36 |
| Grimmauld (any/all) | Like, using modules from an explicitly defined absolute path is objectively the correct thing to do, because it is more predictable. Fix will be up once tests passed, and is trivial. | 14:53:08 |
