I’ve been distributing my app as a .deb which will prob only let it install on kubuntu i guess. So I’m trying to go flatpak.
I have many questions - answering just one wil make me love you forever (probably not a thing you want, but anyway)
Should i target org.kde//5.15-23.08 or org.kde//6.6 ??? Most apps on flathub.org seem to tartget 5.15. My app compiles fine under either qt 5 or 6 so it doesn’t matter to me. kubuntu itself won’t do qt6 till 24.10 it’s looking like. Is 6.6 not yet stable? Most apps seem to target 5.15 and pick all 3 socket= for wayland, fallback to x, and x??? When I submit my app they say pick either x or wayland with x fallback. That still doesn’t tell me what to target. Which should I target? Why is targetting 6.6 so rare?
My flatpak’d app has scaling issues. When I look at my .conf file where i save the window position and size, the x,y positions look totally fine. But the width and height are much smaller than I’d think they should be. The icons and graphics look jaggy as if they’ve been scaled up from lo res. when my app is full screen, it’s width and height should be pretty close to 1920x1080 (regular hd monitor). But I have size=@Size(1536 835). That’s not ok. How can I fix this?
Can flatpak include an x86 and arm64 runtime? I currently have a .deb for raspi and my kubuntu. I think I read references to this being possible. But I’m not having any luck finding out how. Have I just not read all the docs? I thought I did… I could be wrong tho.
If you’re a flatpak developer, where do you ask your questions? here? stackoverflow seems SUPER sparse. on reddit? github has a bunch of bugfix threads that are helpful but completely disorganized.
ok. thanks for any help you can throw my way. I’m thinkin’ I should write up how to develop a flatpak app in qt cuz the docs just seem super sparse and I’m not sure how anyone can find their way. I certainly need help
If your app works on Qt6 then you should use a Qt6 runtime. I imagine a lot of the apps still using Qt5 are tied to KDE, but now KDE Plasma 6 is near at hand.
Similarly, if you app works using the Wayland backend, then it should have --socket=wayland and --socket=fallback-x11. The latter allows X11 usage only in an X session. The apps that also include --socket=x11 do so for compatibility with ancient flatpak versions. fallback-x11 takes precedence, so this has no effect on modern flatpak installations.
That sounds like what happens in GNOME when using an X11 app on Wayland with fractional scaling mode enabled. I understand that behavior to be configurable in KDE.
If that’s what’s happening, the solution would be to ensure that the app is using Wayland.
If your manifest builds the app from source, then you’ll automatically get x86_64 and aarch64 builds unless you opt out. For binary assets, you can provide separate ones for each arch using only-arches, but building from source is preferred.
In addition to this forum, there are Flatpak and Flathub rooms on Matrix.
I’ve found the people on here helpful and when building the app initially and trying to make it publishable - the error feedback from the experts Hubert Figuière, Bartłomiej Piotrowski and Nick Richards was extraordinarily helpful. There aim is very clearly to help you create another Flatpak!
(This is in stark contrast with other (unmentionable) packaging systems where the experts seem more interested in scoring points and emphasising their superiority.)
