| 22 Nov 2022 |
samueldr | if I run it from the terminal it shows-up, because the environment differs | 22:18:58 |
samueldr | I don't know how it differs yet that matters though | 22:19:06 |
samueldr | how are you launching system settings? | 22:19:35 |
samueldr | for me, custom shortcuts don't show when launched from krunner or from the plasma mobile launcher; but shows up from my custom terminal, which in turn is launched via app-compartmentalization | 22:20:21 |
aktaboot | from the menu | 22:20:27 |
samueldr | how does it fare from krunner (ALT+F2 or ALT+SPACE) | 22:21:43 |
aktaboot | I can go directly to Custom shortcuts | 22:21:46 |
samueldr | * how does it fare from krunner? (ALT+F2 or ALT+SPACE) | 22:21:46 |
aktaboot | In reply to @samueldr:matrix.org how does it fare from krunner? (ALT+F2 or ALT+SPACE) same | 22:22:09 |
samueldr | though I'll also note that a lot more is different when launched through the "app compartmentalized" terminal, e.g. icon theme, or widgets theme | 22:26:04 |
samueldr | QT_QPA_PLATFORM=wayland makes the difference | 22:28:04 |
samueldr | cat /proc/$(pgrep systemsettings)/environ | grep --null-data ^QT_QPA_PLATFORM
| 22:29:24 |
samueldr | * cat /proc/$(pgrep systemsettings)/environ | grep --null-data ^QT_QPA_PLATFORM | xargs -n1 -0 echo
| 22:30:59 |
samueldr | * ~ $ cat /proc/$(pgrep systemsettings)/environ | grep --null-data ^QT_QPA_PLATFORM | xargs -n1 -0 echo
QT_QPA_PLATFORMTHEME=KDE
QT_QPA_PLATFORM=wayland
| 22:31:10 |
samueldr | meanwhile my app compartmentalization drops all the environment only to get the login environment + whatever is imported into systemd | 22:31:36 |
| 25 Nov 2022 |
samueldr | In reply to @samueldr:matrix.org before I bring this up with upstream, anyone would have clues to help figuring out if it's our packaging of Plasma Mobile that makes it so the wallpaper is reset every time it starts? progress, immutability=1 is being set on the "Containment", which seems to reset it at launch... I'm up to the 38th Containment, setting it to 0 in my config keeps the settings on relaunch | 02:51:11 |
samueldr | huh... this is fun
- https://userbase.kde.org/KDE_System_Administration/Configuration_Files
- https://github.com/KDE/kconfig/blob/62cb8e29d7457bb5ac767d29205e547aec668c75/docs/options.md?plain=1
there is a system in place to make global options possible, and even lock them if needed
| 04:44:56 |
samueldr | ... except that for some reason it does not apply to the plasmoid setup on the desktop | 04:45:08 |
samueldr | anyone has tried to make a declarative thing with NixOS for Plasma settings6 | 04:45:38 |
samueldr | * anyone has tried to make a declarative thing with NixOS for Plasma settings? | 04:45:39 |
samueldr | attempts are made, kind of, https://github.com/nix-community/home-manager/issues/607 | 04:48:49 |
samueldr | the file format, though, is simply hostile | 05:45:06 |
samueldr | [Libinput][2][14][ETPS/2 Elantech Touchpad]
NaturalScroll=true
TapToClick=true
| 05:45:17 |
samueldr | I need to look into whatever uses kcminputrc, but I'm assuming from that file that you can't configure "any touchpad" | 05:46:19 |
samueldr | at the very least the identifers are related to the hardware;
15: 0002:000e I8042 isa0060/serio4/i ETPS/2 Elantech Touchpad KEY ABS
0x2 and 0xe → 2, 14
and this matches for another device (18d1:503c →[6353][20540])
| 06:06:31 |
samueldr | AFAICT this doesn't apply to keyboard, but applies to mice, and this means if you change mouse, there are no user-defined defaults... so things like acceleration or left-handedness need to be re-defined? | 06:15:13 |
samueldr | support was added for defaults:
- https://invent.kde.org/plasma/kwin/-/commit/352e92e32f04d80944002a7abf363f1b957ce5b2
| 06:49:19 |
samueldr | but AFAIUI this implies it's not being used
- https://invent.kde.org/plasma/kwin/-/blob/777c2bdb18408b903e7be6e6f9fe5183899b8a24/src/backends/libinput/device.cpp#L403-405
| 06:49:57 |
samueldr | (coupled with the fact it doesn't work) | 06:50:07 |
samueldr | am I understanding that bit right? | 06:50:19 |