Summary: | Falkon won't launch because it's missing kf5-locale-gen | ||
---|---|---|---|
Product: | [Applications] Falkon | Reporter: | techxgames |
Component: | general | Assignee: | David Rosca <nowrep> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | craffop, desertclaw16, hrwy, kde, m.larborg, neon-bugs, samopn, sitter, white.tw.tw |
Priority: | NOR | ||
Version: | 3.1.0 | ||
Target Milestone: | --- | ||
Platform: | Snap | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
techxgames
2019-08-30 16:25:55 UTC
*** Bug 411535 has been marked as a duplicate of this bug. *** Same issue for me. Falkon won't launch because of of the following: /snap/falkon/60/kf5-launch: line 209: /snap/falkon/60/kf5-locale-gen: No such file or directory Other than subfolders (.cache, .config, .icons and .local) there's nothing in that folder. the .local folder is also empty. I can confirm. I get the same error when trying to launch falkon. snap run falkon /snap/falkon/60/kf5-launch: line 209: /snap/falkon/60/kf5-locale-gen: No such file or directory *** Bug 422297 has been marked as a duplicate of this bug. *** Actually, it might be an idea to change this report to be against Ubuntu and not Mint. Mint recently announced that they won't support snaps by default: https://blog.linuxmint.com/?p=3906 My guess is that going forward that if you install Falkon on Mint it will be a deb and likely not produce this issue. Let's file it against platform "snap" instead. SUMMARY Snap hasn't 3.0.1, 3.0.0 channel !! All 'latest' channels can't be launched because of this bug File that needed: https://invent.kde.org/graphics/krita/-/blob/adbe90fd47dc81173a3442c0d920dcc2dddd4a75/packaging/linux/snap/scripts/kf5-locale-gen Let's change also importance to high/critical. Affected all machines with OS elementary OS 5.1.7 Hera. please add last line to snapcraft.yaml launcher: plugin: dump source: . organize: ... kf5-locale-gen: bin/kf5-locale-gen Any updates? Candidate branch doesn't work either. Did comment 9 work? *** This bug has been marked as a duplicate of bug 414014 *** |