Flatpak install broken on AlmaLinux 9.1 and Fedora 37: CudaText 1.176.0.0, linux-aarch64-qt5, fpc 3.2.2
See original GitHub issueFully functional on AlmaLinux 9.1: CudaText 1.176.0.0, linux-x86_64-qt5, fpc 3.2.2
Fully functional on Fedora 37: CudaText 1.176.0.0, linux-x86_64-qt5, fpc 3.2.2
Broken on AlmaLinux 9.1: CudaText 1.176.0.0, linux-aarch64-qt5, fpc 3.2.2
Broken on Fedora 37: CudaText 1.176.0.0, linux-aarch64-qt5, fpc 3.2.2
When starting CudaText on AlmaLinux 9.1 and Fedora37: CudaText 1.176.0.0, linux-aarch64-qt5, fpc 3.2.2
Loaded session: "history session.json", 0ms, 2 file(s)
Startup: 165190ms, plugins: 0ms ()
Plugins menu does not work, themes are not being applied on startup. If I reapply the themes they take effect. Plugins are not working.
The previous flatpak version was working on AlmaLinux 9.0 and AlmaLinux 9.1 linux-aarch64 yesterday and this morning.
(before I updated the CudaText flatpak today).
So this particular issue only applies to aarch64
and not x86_64
.
Issue Analytics
- State:
- Created 10 months ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
All Flatpak Apps broken : r/Fedora - Reddit
Hey folks, after my last reboot this morning all applications installed via flatpak are broken. I did not do anything specific to flatpak...
Read more >Install cudatext on Fedora using the Snap Store - Snapcraft
It is open source project and can be used free of charge, even for business. It starts quite fast: ~0.3 sec with ~30...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I found the bug - fixed, update the python-for-lazarus package from the last release. tested on RPi 4.
It is known issue on aarch64! #4489