| 19 Jun 2025 |
 Adam Neverwas | Thnakz | 09:26:10 |
|  FliegendeWurst (@GPN23) changed their display name from FliegendeWurst to FliegendeWurst (@GPN23). | 12:29:23 |
| 21 Jun 2025 |
 Khalil Santana | Anybody here uses KDENLIVE + AMD GPU? Does GPU-accelerated rendering work well? It seems to only use ~60% of the encode/decode of the GPU according to nvtop. It's not terribly slow but I'm wondering if that is normal. (~18min 1080@30fps x264 .mp4 as input, and trying to output to the VAAPI profile results in an encode time of ~2:30minutes). My hardware is an RX7600 dGPU + R7 7800X3D CPU, storage is NVME. | 23:55:45 |
| 23 Jun 2025 |
 Sandro 🐧 | Can it be, that kdeconnect file sharing does not work with nat64? | 09:07:16 |
|  asshall joined the room. | 09:19:34 |
| asshall | Frankly I both a noob with KDE stuff and nix so what follow might be painful ^^
I'm trying to get kde mobile up to date and for now what I've started to do is replicate /nixos/modules/services/x11/desktop-managers/plasma5.nix modularity into /nixos/modules/services/desktop-managers/plasma6.nix. Issue is I frankly have no idea what configuration is strictly needed for mobile/desktop. Is there some tool/documentation that could help with that, or should I do it the painful way and remove stuff one by one ? (which really doesn't seem like a good idea) | 09:27:14 |
 K900 | No, there really isn't | 09:28:22 |
| asshall | While I'm at it i'll rapid fire questions and excuse myself for the spam in advance
1:
I see there are pkgs.plasma5Packages, pkgs.kdePackages, pkgs.libForQt5 sets, I'm unsure where those are created, but anyways my point is the pkgs.plasma5Packages.plasmaMobileGear (even though I can't find it trough repl) seems useful. Should I be replicated for plasma6 ?
2:
Should plasma common configuration (talking about plasma5 module's desktop/mobile/bigscreen configs) be the lightest it can be ? My rational is that for mobile devices with hardware constraints it seems beneficial. However it could be a lot of work ^^
3:
Seeing the CONTRIBUTING.md file in nixpkgs repo, it says commit should be atomic, so should the first commit simply add the mobile options and install mobile only apps. And next commits clean the common configuration ?
4:
I'm seeing pkgs/kde/generated/dependencies.json is this generated using an external tool or is it a part of nixpkgs I'm not aware of ?
I'll stop there for my own sanity an you folks ^^
| 09:39:08 |
| asshall | So how did you manage ? A lot of build-vm and patience ? | 09:39:33 |
| K900 | 1) No, there is no Plasma Mobile Gear set in 6.x
2) Can't answer, need to decide on a case by case basis
3) You can have any order you want as long as it doesn't break things, though I'd maybe even consider putting the mobile bits into an entirely separate module
4) It's generated by the scripts in maintainers/scripts/kde/ | 09:49:07 |
| K900 | There's packaging guidelines for Plasma Desktop | 09:49:14 |
| K900 | https://community.kde.org/Distributions/Packaging_Recommendations | 09:50:35 |
| asshall |
- What would be the rationale ? I'm blissfully unaware of plasma inner working but from what I gather on the plasma mobile repo is that It's a superset of plasma desktop, shouldn't nix config should more or less be desktop config (minus graphical apps that don't scale) plus mobile apps ?
services.xserver.desktopManager.plasma6.mobile seems like an adequate enough option ?
| 09:56:35 |
| K900 | It's not a superset, no | 09:57:12 |
| K900 | It's built on much of the same tech, but it's not a strict superset | 09:57:35 |
| asshall | Or it might just be I didn't understand you answer, but creating a new module would mean having something like services.xserver.desktopManager.plasma6-mobile right ? | 09:57:37 |
| K900 | Not necessarily | 09:57:46 |
| K900 | The option naming isn't directly related to the module layout | 09:57:54 |
| asshall | So then I'll need to read a bit more on the module system, to at least get it working on my end, I'll try to replicate plasma5 module as to not complicate things for me I think. | 10:00:22 |
| 24 Jun 2025 |
| K900 | https://kde.org/announcements/changelogs/plasma/6/6.4.0-6.4.1/ | 12:00:39 |
| K900 | Gonna get this going in maybe 30 minutes | 12:00:48 |
| K900 | https://github.com/NixOS/nixpkgs/pull/419554 | 12:51:33 |
| 28 Jun 2025 |
|  Michalis joined the room. | 19:50:19 |
| Michalis | How would one go about packaging a (python) krunner plugin for nix? I'm trying to package this to use with home-manager https://github.com/mpardalos/KRunner-SSH. Is there any examples I can follow? | 20:06:20 |
| Michalis | What I tried so far is here: https://github.com/mpardalos/KRunner-SSH/tree/nix | 20:13:46 |
| K900 | Yeah none of that is correct basically | 20:27:44 |
| K900 | You want to install to $out/share | 20:27:47 |
| K900 | And you want fully qualified paths everywhere | 20:27:54 |
| K900 | Nothing like $PWD | 20:28:04 |
| K900 | And you have external dependencies | 20:28:26 |
