Hello, are there any plans to have the Krita for Android app available via F-Droid?
Hi @Lynx3d
Thanks for suggestion.
Just to test, I’ built last 4.3.0 from repository (git 88342ec) with I think, debug symbols (cmake options: -DCMAKE_BUILD_TYPE=Debugand -DKRITA_DEVS=ON)
To test gdb I just started Krita and then, Menu > Quit
And just doing this, I got a segmentation fault:
Thread 1 "krita" received signal SIGSEGV, Segmentation fault.
0x00007ffff49acae5 in KLocalizedString::~KLocalizedString() () from /usr/lib/x86_64-linux-gnu/libKF5I18n.so.5
(gdb) n
Single stepping until exit from function _ZN16KLocalizedStringD2Ev,
which has no line number information.
0x00007ffff60146c0 in KCrash::defaultCrashHandler(int) () from /usr/lib/x86_64-linux-gnu/libKF5Crash.so.5
(gdb) n
Single stepping until exit from function _ZN6KCrash19defaultCrashHandlerEi,
which has no line number information.
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = krita path = /home/grum/Dev/krita_master/install/bin pid = 11982
KCrash: Arguments: /home/grum/Dev/krita_master/install/bin/krita
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__2
Thread 1 "krita" received signal SIGSTOP, Stopped (signal).
0x00007ffff187a720 in __GI___nanosleep (requested_time=0x7fffffffc9a0, remaining=0x7fffffffc9a0) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
28 ../sysdeps/unix/sysv/linux/nanosleep.c: Aucun fichier ou dossier de ce type.
Not sure about how to interpret this and/or if this kind of information can help?
If yes, I’ll try to use this build executed with gdb to grab next crash informations.
(And, finally, not sure that’s normal to have a crash when exiting Krita… 
)
Grum999
Those three commands are really helpful:
bt
^ it shows the backtrace of the current thread
thread apply all bt
^ it shows the backtrace of all threads (since Krita is multithreaded and sometimes, not always, it’s useful to see what other threads were up to)
thread apply all bt full
^ it shows backtraces for all threads but in full version, which means it’s much, much longer 
and tbh I’ve never seen much use to it, but maybe there is.
For Krita it’s best to call the
thread apply all bt
to make sure all the information needed to fix the crash are inside.
Please do that and make a bug report 
Ok thanks for the tips
There’s a lot of information that I’m still not able to understand.
I’m opening a bug, but, there’s choice between 4.3.0-beta1 or git master
But I’ve built the 4.3.0 by myself from git krita/4.3 branch… 
Just download last nightly appimage, and tried gdb but app image doesn’t generate segmentation fault on exit…
So, I open a bug? ‘unspecified’ version is OK, and I add additional information (build options, git hash) as comment?
Grum999
That’s something @sh-zam will need to answer. We were talking about it, that’s for sure, but what have we figured out, that is something I have no idea
Then use “master” or “nightlty build”, just make sure to add the comment with the git hash of what you built You could probably use 4.3.0-beta, it would be easier to find when checking for 4.3.0 regressions.
OK, bug created
https://bugs.kde.org/show_bug.cgi?id=421477
Grum999
YAAAY there is an osX version !
That sounds like an old news? There was an OSX version for Krita 3.0 (4 years ago) and I believe we do make OSX builds for beta versions… Or maybe there weren’t?
Well, yes we certainly do plan to do that. Especially for the nightly releases. But the way things are setup right now, it requires system admin’s help and certainly we need to discuss this again, as, Android improvements have been made in krita/4.2 branch and aren’t in master yet.
1 Like
I actually had access to nightlies which include the new resource features. The problem is I have way too much bug with that so…I was stuck since a while with 4.2.9 or an older nightly
Feeding nightlies to Google Play or F-Droid would probably be too much too often but something like every two weeks might be more reasonable, although I suspect for F-Droid the best approach would be to get in touch with them and have them state how frequently an app can be updated.
Any way we can help with that?
Ahh yes. Could you please make a bug report on bugs.kde.org to make sure that nightly is built for OSX as well? At first it was only for Krita Next because the scripts weren’t trustworthy enough or something, but now that they are, it should be possible to add them to the nightly factory as well. If you make a formal bug report, there is a change we won’t forget about it
KDE hosts its own F-Droid repository. So once we have setup Krita on it (KDE’s repo), all that would be required is to add KDE’s repo link to your F-Droid app and you should be good for regular nightlies
As for the Play Store release, yes they are a bit of a hassle. So, I think we are going to stick with the same release schedule as the desktop app.
Thanks! Android port has a long way to go, we could always use some help. Just hang in there!
1 Like
Did not know about the KDE F-Droid repository! I’ve just added it now. Thank!
1 Like
Yeah I do trust you guys on handling reports !
Are snapshots supposed to save after you close the document? Because they don’t for me.
they’re not supossed to save, as far as I know. It’s because undos in general don’t save…
Dang, that’s a little lame. Kind of thought it could be like some in-file version management system (like incremental saves! but more convenient. so convenient.)
Thank you for clearing that up though.
I see, I touch, I break: https://bugs.kde.org/show_bug.cgi?id=421518
It might just be me and my old dog so can someone check it please?