CC @michaelpj @mbertolutti @qknight

Is this the right fix? If Konsole does indeed look in XDG_DATA_DIRS then it's just a matter of making sure all the relevant stuff gets linked into the profile, since that already goes in XDG_DATA_DIRS. But that's somewhat tricky, since currently we can only decide to link in subdirs of share in a module.

This will work for this issue, but e.g. if you add other programs that provide data files that konsole uses then it won't pick them up.

The usual mechanism for this is XDG_DATA_DIRS. You're adding the konsole /share output, which will make it pick up the stuff packaged with konsole, but other stuff needs to go in the system XDG_DATA_DIRS for konsole to find it. But if we had that working then we wouldn't need this at all, since the konsole /share files would be picked up in exactly the same way.

So why don't we pick them up? The answer is because we don't (usually) merge in all the subdirectories of /share. So we just ignore the ones that konsole needs. Normally you can only change that with a nixos module. The Plasma module, for example, does so.

Previously I've thought that was good, but increasingly I wonder if we should just link the whole of /share by default. (see #47173)

So I guess this is an okay solution, but we should be aware that konsole may still not work "properly" when you're not running Plasma.

The alternative solution would be to add a programs.konsole module.

So I guess this is an okay solution, but we should be aware that konsole may still not work "properly" when you're not running Plasma.

I'm not running Plasma, so it's certainly not a strict requirement for this to work.

OOI, you say you couldn't make Yakuake work, but have you tried wrapping it so it has access to Konsole's data files? I think it uses a lot of the same code under the hood.

I'm not running Plasma, so it's certainly not a strict requirement for this to work.

I believe the way to fix this problem for all applications is to add this to your configuration.