All I could find is how to make a list, and reinstall flatpaks from that list, as well as backup app data, however all of that assumes I want to do updates.
Meanwhile what I want is akin to extracting APK of a stable version of some app, backing it up and using it for years to come. For example that’s how I joined these 2 screenshots, using JointPics from 2014 which isn’t even on Play Store anymore, and targets API so low that it has to be installed via ADB. (Yeah, I am too dumb for GIMP)
As for the regression, you can see. On left is older Flatpak, on right is version from Arch repo. The Flatpak I originally installed as a hotfix for update that broke it completely at one point on Arch.
You can see the older version nicely fits the screen, splitting up text into columns.
Meanwhile the new version just does smaller page in middle of screen that doesn’t even work properly with Breeze Dark theme, causing different background for text sections.
The only improvement is ability to flip pages rather than use arrows, but that’s minimum.
Well, and maybe the progress keeping got fixed, but I didn’t test that much.
Don’t pay attention to the taskbar. I wish it could flip to vertical with different screen orientation. Yeah, the icons’ clickability is a dice roll of what you tap.
You can use the Warehouse app to do this: https://flathub.org/apps/io.github.flattool.Warehouse
Wouldn’t recommend doing it with the CLI, they don’t make it easy.
If you already have the correct version of the flatpak installed, you can try
flatpak build-bundle.flatpak build-bundle LOCATION FILENAME NAMEwhereLOCATIONis the path of the repo on disk. Runflatpak info -l org.kde.arianna, and copy the part before/appFILENAMEis the output file name, preferably.flatpak. Eg:arianna.flatpakNAMEis the name of the app, hereorg.kde.arianna
The generated file can be installed with a double-click, or with
flatpak install <file>This is the equivalent of an Android
.apk. It contains the app but depends on a runtime. If you want to install it in a few years, odds are the runtime will no longer be available. You can backup the runtime the same way with the--runtimeoption.flatpak build-bundle --runtime LOCATION FILENAME NAMEwhereLOCATIONsame as earlierFILENAMEegarianna-runtime.flatpakNAMEis the name of the runtime, which you can get withflatpak info --show-runtime org.kde.arianna
This takes a while, for some reason. Maybe it’s compressing stuff?
The runtime is installed the same way as the app: double click or
flatpak install.
Note: I only did this once, and not specifically on Arianna. Hope it works.
Are you sure not just the defaults changed? Or isn’t it a problem on your end? On the project page the screenshot looks like the old version: https://invent.kde.org/graphics/arianna
Have you contacted the developers? They have a matrix chat. Maybe you found a bug, and it would help others if you would report it.
It still looks like that, aside from the datk mode issue, but only in landscape orientation.
Are you sure it’s not a you problem? Or isn’t it a you problem? Go read the docs.
Have you contacted the devs? Reporting a bug would be helpful.
Sorry to be so rude, but you really hit a nerve. It isn’t even your fault.
Anyway, rant time:
KDE and bug reports. They always come to you like "Hey, bug reports are so really importsnt to us! And we’ll guide you through it. Here’s our lovely oh-so-helpful wizard!
Except it ain’t lovely. Nor helpful. The only thing it does is pop up whenever a KDE app has an aneurysm and asks you for a backtrace. And then… backtrace is declsred useless.
Why even bother people with the stupid popup if in 90% of cases it’s declared as useless. Why not do the backtrace silently and then annoy the user only once you declare the bug “useful”.
Last instance of this: I was using my KDE desktop. For some reason, Plasma seems to really hate me, because I need to fix default apps every few weeks. For some reason, jpegs and pngs open in Krita by default.
So, wanting to close Krita, becuse I don’t need an entire editor to look at a photo, with tools taking up 25% of the screen, when it asked me about the import resolution, I pressed 0. Krita proceeded to crash and open the report bug dialog.
Not having seen the KDE report wizard for quite some time, I felt inclined to go fill out the report. Got through the first few pages just fine. Then came the backtrace. Sure, do it. I’d like whoever debugs this not snooping through a data dump containing god knows what, but sure. Then it gets called useless. AFTER you’ve taken 30-ish seconds of my life on preliminary questions.
Look, if you’re gonna ask people for input and discard said input if something unrelated happens, at least ask after the something unrelated decided it’s not gonna be yeeted away. No need for the “Oh, wait, we don’t really need this, it’ll take too much time to play detective” after the user already passed three screens of interrogation.
Anyway, the point is:
KDE clearly doesn’t care about bug reports. Because if they did, the guide on installing backtrace-enabled packages once the inevitable verdict of “useless” wouldn’t be a wiki page with the generaal message of “find backtrace-enabled packages, you buffoon” when you could point to them.
Another problem with this is: when a bug happens without backtraceable packages, how is the user supposed to recreate it if they don’t know how?
And besides, my bug is very recreateable. Open an image in Krita (preferably from Dolphin, after Plasma mangled the defaults, again and again). When prompted for some integer, enter “0”. Instead of a generic error message, see the entire app sink into oblivion.
Anyway, if anyone feels like reporting the totally useless report with totally unrecreateable conditions, feel free. I won’t. Just too much work, for it to be discarded just like that by some wizard no one even thought through.
And why would I contact the devs? Or rather, where could I do that? They’re worse than government agencies, for god’s sake. The right person or place just doesn’t exist. Wherever you go to or ask, it’s someone else’s responsibility or your fault. And the wizard, that true single point of contact - refuses any contact just as consistently.
So tell people to call the devs. Tell them it’s their fault. Tell them to make a bug report. Say it just might help not just you, but someone else when all hell will freeze over before anything like that becomes even a remote possibility.
Talk about adding insult to injury.
Wtf man, developers are also people. Most of them doing this for free in their free time. You are the kind of entitled user who makes foss devs burn out. Never thought I will find one in the wild.
I use krita frequently and never met your bug so it’s not as recreatable or important as you think.
Noone forces you to use krita. If it doesn’t fit your workflow or if you think developers are deliberately sabotaging your work, you can switch to another free or paid alternative. If you would switch to a paid one, you could speak to a manager.
In op’s case I’m not sure it’s a you problem. In your case I’m sure it is.
Look, I get it. But I’m also burned out.
Noone forces you to use krita.
Krita’s devs specifically? No. I respect devs by default. I don’t doubt many of Krita’s devs love what they develop. I also use Krita. I don’t have it installed because I don’t need it.
The problem that I keep running into is my (Plasma) defaults being changed for (some) reason. Krita usually gets the defsult for photos. Rhythmbox for audio and MPV for video. I prefer using Pix for photos and VLC for AV.
Noone forces you to use krita.
Plasma, kind of - does.
99% of people do not want a photo editor to be their defsult app for opeing photos. Some artists? Sure. But me? No.
Again, it’s nor a Krita thing specifically - Plasma fucks with my defaults. It’s a Plasma/KDE thing. Krita is just the unfortunate app to have become Plasma’s senseless-default victm.
If it doesn’t fit your workflow or if you think developers are deliberately sabotaging your work
Oh, Krita fits my workflow quite well. Personally am in the process of switxhing to it from GIMP. I know I wrote up a huge wall of mostly garbled text in a passionate rage, but reading just the first part of my rant should’ve made that clear.
I use krita frequently and never met your bug so it’s not as recreatable as you think.
Of course you didn’t. Because who in their right mind enters “0” as the target resolution? That’s right - on one! Except for me, apparently. It’s a stupid bug. One which doesn’t mean anything. It opens no attack surface. It doesn’t cause random crashes. It doesn’t interfere with anyone’s work.
However, you clearly haven’t read my essay. Which is fine with me. It isn’t quality reading material by any sensible metric. But, were you to have read it and tried to recreate the bug, you probably would’ve succeeded.
With that out of the way, my main point was how no - devs (especially KDE, and very transparently so) don’t value your feedback as much as one might think.
Which is - understandable.
As you said, many keep FOSS software alive in their free time for nothing other than the moral gratification. Which is much more than merely commendable. And please, do not try to tell me I don’t respect that when I do.
Where would devs be if they only replied to stupid questions from new users? That’s right - in a tech support hub!
Which is obviously a waste of their time. The fact they don’t do that isn’t anything negative.
The problem, as always is - documentation. My little beef with KDE’s crash wizard is but one example of this deeply-rooted problem.
As is seen in our (both mine and your) example, reading is hard. Writing - harder still. Were I able to read and fully comprehend the ill-fated link on the KDE wizard’s “fuck you” page, you probably wouldn’t be rading this. But alas, I am a human whose reading comprehension skills aren’t top-notch.
Another, equally deeply rooted problem in FOSS is lack of general design thinking and logic. Am I calling KDE devs stupid? Of course not! But any UI (including the KDE crash wizard) should have a few eyes to assess it first. Then research on a batch of test users should be done. And then feedback from the general user population should be listened to. Is that a hard ask? Yes. Step 2 is expensive and as such out of reach of most FOSS projects, and not even Big Tech bothers with step 3.
But am I wrong in calling the KDE modal annoying and badly designed (“stupid”) even, when it has already wasted my time in the same way on 15 occasions? Maybe not. I am angry and it may have been irrational. But I feel my perspective is at least understandable even if the wording isn’t.
In the end, users can’t live without developers and developing user-facing applications makes little sense without users. I’m not in the Linux community because I don’t like FOSS, Linux or KDE. I’m percisely here to support them. However, sometimes issues arrise, and having a good community to help with fixing issues (because the devs can’t (obviously) handle all that load themselves) is good.
Having a community where the answer to a simple, begginer question is basically “bother the devs, they have a Matrix”, “it’s probably your fault” isn’t an answer. It’s a fuck you. And once they find out they’ve been mislead (not even intentionally perhaps), they might go back to Big tech.
Saying to me that I don’t support FOSS, that I don’t like it and that I can go back to Big Tech (when I haven’t been there for over 4 years now), is an even bigger one.
I like FOSS. Saying I don’t respect them wben I truly do is an insult. I merely don’t understand some of their decisions. Probably due to a lack of context and knowledge, which is on me.
But does giving a rant about, what are tiny problems in the running of a huge machine known as My Computer, spurred on by someone’s unhelpful advice, given in hopes of starting a discussion and the wholly implausible odds of the issue at hand given as an example being fixed due to it call flr the reply “Go to Big Tech, there’s clearly no room for you here”?
I’d hope not.
There are plenty other DE or WM “fishies” out there.
deleted by creator
