Bug 501948 - kf5-core24: command-chain/locale-gen: No such file or directory when launching snaps
Summary: kf5-core24: command-chain/locale-gen: No such file or directory when launchin...
Status: REOPENED
Alias: None
Product: neon
Classification: KDE Neon
Component: Snaps (other bugs)
Version First Reported In: unspecified
Platform: Snap Linux
: NOR normal
Target Milestone: ---
Assignee: Scarlett Moore
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-24 17:41 UTC by Furgo
Modified: 2025-12-18 15:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Furgo 2025-03-24 17:41:05 UTC
### Bug Description

While [upgrading the FreeCAD snap to `core24`](https://github.com/FreeCAD/FreeCAD-snap/pull/169), and after the latest `kde-neon` fixes (https://github.com/canonical/snapcraft/pull/5261), the snap builds and runs successfully, but outputs quite a few warnings and an error on the terminal as detailed below.

Those don't seem to affect running FreeCAD, but I thought I'd file an issue just in case. At least the missing `command-chain/locale-gen` error sounds like a genuine bug.

### To Reproduce

1. Install the FreeCAD snap available for testing as an [artifact on the last workflow run page](https://github.com/furgo16/FreeCAD-snap/actions/runs/13558406862).
2. Run `freecad` on the terminal and watch the output while starting the app.

### Environment

Snapcraft on Ubuntu 24.04 LTS, snap built on GitHub CI using destructive mode

### snapcraft.yaml

```yaml
https://github.com/FreeCAD/FreeCAD-snap/blob/37d742422ea3f4240a7acf8ce3725e48bde328a6/snap/snapcraft.yaml
```

### Relevant log output

```shell
update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/gtk2/Materia-compact /snap/freecad/x1/data-dir/themes/Materia-compact-2 none bind,ro 0 0): cannot write to "/snap/gtk-common-themes/1535/share/gtk2/Materia-compact" because it would affect the host in "/snap"
update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/gtk2/Materia-dark-compact /snap/freecad/x1/data-dir/themes/Materia-dark-compact-2 none bind,ro 0 0): cannot write to "/snap/gtk-common-themes/1535/share/gtk2/Materia-dark-compact" because it would affect the host in "/snap"
update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/gtk2/Yaru-MATE-dark /snap/freecad/x1/data-dir/themes/Yaru-MATE-dark-2 none bind,ro 0 0): cannot use "/snap/gtk-common-themes/1535/share/gtk2/Yaru-MATE-dark" as bind-mount source: not a directory
update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/gtk2/Yaru-MATE-light /snap/freecad/x1/data-dir/themes/Yaru-MATE-light-2 none bind,ro 0 0): cannot use "/snap/gtk-common-themes/1535/share/gtk2/Yaru-MATE-light" as bind-mount source: not a directory
/snap/freecad/x1/kf5/snap/command-chain/desktop-launch: line 23: /snap/freecad/x1/snap/command-chain/locale-gen: No such file or directory
ERROR: /snap/freecad/x1/snap/command-chain/locale-gen exited abnormally with status 127
```

### Additional context

- We're using the snapcraft `edge` channel to have the changes in https://github.com/canonical/snapcraft/pull/5261 to the `kde-neon` extension available.
- ScarlettGatelyMoore mentions: "locale-gen is no longer needed in core24, looks like I need to fix kf5 in snapcraft-desktop-integration. The mount errors I am not sure of."
Comment 1 Scarlett Moore 2025-03-24 18:59:12 UTC
Yes Locale-gen still needs removed. This is freetime work and I don't have any right now ( working on qt6 with time I do have.). Those mount errors are snapd and thus needs to be reported on launchpad.
Comment 2 Furgo 2025-03-26 07:37:31 UTC
Is there anything I can do to help?

Happy to attempt to fix it, I just need some pointers about where to look at and where to submit an MR or PR to. Thanks!
Comment 3 Furgo 2025-12-18 15:16:32 UTC
This appears to have been fixed, thus closing.
Comment 4 Furgo 2025-12-18 15:17:49 UTC
Actually, I'm using kf6-core24, and I realized this bug was for kf5-core24. Reopening then, sorry for the noise.