Just so you know, boosters may have to go because of this change in glibc:
https://sourceware.org/bugzilla/show_bug.cgi?id=24323
It has been reverted in Sailfish OS:
https://git.sailfishos.org/mer-core/glibc/commit/df05690
but at some point boosters may get replaced with simple fork() wrappers.
They should still start your app, though.
Cheers,
-Slava
I think the qt5 booster is a no-op, but im sure someone with more
knowledge can correct me. The regular booster will try and load the
app as a shared library so it will need to be compiled a certain way.
Depends how your app is written. Anything based on the sdk templates
should be fine.
On Tue, 14 Apr 2020 at 12:19, Julien Blanc <julien.bl...@tgcm.eu> wrote:
Le mardi 14 avril 2020 à 11:27 +0100, Adam Pigg a écrit :
Have you tried using invoker to launch it?
[nemo@Sailfish ~]$ invoker --type silica-qt5 harbour-kontroller
invoker: Invoking execution: '/usr/bin/harbour-kontroller'
invoker: error: Can't send signal 11 to application [24388]: No such
process
Segmentation fault
[nemo@Sailfish ~]$ invoker --type qt5 harbour-kontroller
invoker: Invoking execution: '/usr/bin/harbour-kontroller'
--> app launches correctly.
So that’s indeed a difference, and i can fix the .desktop file
accordingly. Thanks for the tip.
But what is the difference between silica-qt5 and qt5 ? Why would it
cause an app crash ?
Regards,
Julien
On Tue, 14 Apr 2020 at 11:18, Julien Blanc <julien.bl...@tgcm.eu>
wrote:
Finally found something relevant in the logs :
Apr 14 12:15:42 Sailfish mapplauncherd[5363]: Boosted process
(pid=16324) was terminated due to signal 11
So apparently, my app segfaults, but only when launched from
applauncherd. This is somewhat good news. I can start to track the
issue adding some debug traces.
I'm still puzzled as what's the difference between launching from
lipstick and from a terminal.
Regards,
Julien
Le mardi 14 avril 2020 à 07:35 +0200, Julien Blanc a écrit :
There it is :
[Desktop Entry]
Type=Application
X-Nemo-Application-Type=silica-qt5
Icon=harbour-kontroller
Exec=harbour-kontroller
Name=Kontroller
# translation example:
# your app name in German locale (de)
#
# Remember to comment out the following line, if you do not want
to
use
# a different app name in German locale (de).
#Name[de]=kontroller
The whole source code is available here:
https://github.com/Julien-Blanc-tgcm/kontroller
I changed a lot of things from v0.6, so tracking which particular
change triggers the problem is not an easy task. I’d rather have
a
way
to get more traces from lipstick than reverting every single
change i
made.
THanks for your help,
Regards,
Julien
Le lundi 13 avril 2020 à 19:57 +0300, Андрей Кожевников a écrit :
Hello. You're right. Show us your .desktop file to judge
пн, 13 апр. 2020 г. в 19:12, Julien Blanc <julien.bl...@tgcm.eu
:
Hi,
I’m running into a pretty annoying issue with lipstick not
launching
the application i develop anymore (occurs with 3.3, but
occurs
after i
made some changes which should not be relevant).
The application launch fine from a terminal, launch fine from
the
sdk,
but launching it from lipstick, it never gets launched and
the
process
does not show up when running top/ps & co.
This seems like there could be something wrong with my
.desktop
file,
but it didn't change between version 0.6 which was working
fine
with
3.3 and the dev version, which is not (i could not test dev
version
with 3.2 yet).
journalctl does not show anything. There must be something
wrong
with
my app, since it is the only one showing this behaviour (and
it
didn't
before), but i'm puzzled as how to debug this. Any pointer
would
be
greatly appreciated.
Regards,
Julien
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
