https://bugs.kde.org/show_bug.cgi?id=401039
Bug ID: 401039
Summary: Wrong flatpak installation instructions, install
fails; at least two problems at same time
Product: krita
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Documentation
Assignee: krita-bugs-n...@kde.org
Reporter: kxk-ocumoatbugs...@lugosys.com
Target Milestone: ---
SUMMARY
Instructions in https://krita.org/en/download/krita-desktop/ for installation
of Krita via Flatpak are wrong. There are at least to problems:
1. Installation command is truncated/incomplete. Missing location causes error:
'LOCATION must be specified'
2. Even if user manages to discover what the "location" is, the installation
command will fail again if the user had done a local flatpak installation:
`Unable to load summary from remote flathub: GPG verification enabled, but no
summary found (check that the configured URL in remote config is correct)`.
This means the bad instructions in the Krita download page assume (and doesn't
say it) that the user necessarily has a global installation (thus missing yet
another piece in the command), generating such confusing error message that's
very difficult for a non flatpak expert to figure out what's wrong.
STEPS TO REPRODUCE FIRST PROBLEM
1. Paste the "official" Flatpak Krita installation command from
https://krita.org/en/download/krita-desktop/ on a Linux/Mac console and press
Enter.
flatpak remote-add --if-not-exists flathub
OBSERVED RESULT FIRST PROBLEM
The following error appears immediately:
'LOCATION must be specified'
STEPS TO REPRODUCE SECOND PROBLEM
2. In a system in which the Flapak installation is local (i.e., *not global*),
paste the above command but fixed by adding with the missing location:
flatpak remote-add --if-not-exists flathub flathub
https://flathub.org/repo/flathub.flatpakrepo
OBSERVED RESULT SECOND PROBLEM
The following error appears immediately:
`Unable to load summary from remote flathub: GPG verification enabled, but no
summary found (check that the configured URL in remote config is correct)`.
EXPECTED RESULT
Installation instructions should be correct, they should work and don't
generate error messages nor send the user into complicated troubleshooting.
ADDITIONAL INFORMATION
1. There is an additional issue that may affect some users. This is not related
with Krita's above instructions, it's a Flatpak issue, but I mention it here
because it's important and nowhere in Krita's documentation I could find any
mention to it:
Once installed, the flatpak version of krita fails to automatically recognize
and/or use any existing Krita resources/configuration folder, and will create
its own, brand new one. This means that users installing krita via flatpak
after having installed and configured krita with a different method, will get a
totally unconfigured installation and big disappointment if the user is not
comfortable making symbolic or hard links, or copying/moving around
configuration folders, and the downsides and risks of the different options.
2. Last, but even **more important** that all above:
These bad instructions have existed there since long time now and I have
notified and provided full details to Krita's team in another report (which is
only indirectly related). Reply was that this was some _other_ team's
responsibility, not Krita (??..that's odd to me...). Since I didn't get
specifics of who, and nothing happened in the mean time, I am opening this
report in the hope that someone responsible from the Krita webpages may know
who should take ownership for this problem or what to do, if anything.
I very much appreciate if -please- this time this problem is not responded
again with a "this is somebody else's problem" type of answer. The time I have
invested in all these issues is *very* significant and it's not acceptable that
such efforts are put down with a procedural/bureaucratic or semantics excuse
without an effort to at least provide a positive acknowledge of this
collaboration.
To be clear: we users, don't really have to or even want to know how a team
handles their internal affairs. If you expect that, you will loose credibility,
loose support, and we all loose: supporters become detractors.
Thanks for kindly understanding this request and taking it positively and
professionally, if that's not asking too much. A no answer is better otherwise.
I do not want to waste more of my time in this type of argumentations, it's a
shame I have been forced to.
--
You are receiving this mail because:
You are watching all bug changes.
