Bug 477221

Summary:	The program kasts fails to launch. It crashes.
Product:	[Applications] kasts	Reporter:	Mark Grieveson <markgrieveson>
Component:	general	Assignee:	bart
Status:	RESOLVED DOWNSTREAM
Severity:	crash
Priority:	NOR
Version:	23.08.3
Target Milestone:	---
Platform:	postmarketOS
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Mark Grieveson 2023-11-19 05:40:40 UTC

The program crashed.
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
(gdb) run
Starting program: /usr/bin/kasts

Program received signal SIGILL, Illegal instruction

0x0000fffffdae000 in ?? ()
       from /lib/libcrypto.so.3

STEPS TO REPRODUCE
1. enter "gdb kasts" in the terminal
2. then at the prompt, type "run" -->  (gdb) run
3. the result will be as I typed it above

OBSERVED RESULT
(gdb) run
Starting program: /usr/bin/kasts

Program received signal SIGILL, Illegal instruction

0x0000fffffdae000 in ?? ()
       from /lib/libcrypto.so.3



EXPECTED RESULT
I expected the program to run rather than crash.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
This is on a Pinephone Pro running postmarketOS Edge.  
The kernel:  6.6.0
OS:  postmarketOS edge aarch64
Shell:  ash
Resolution:  720x1440
wm:  dwc

Comment 1 bart 2023-11-19 22:12:50 UTC

Is this happening with the postmarketOS Kasts package, or with a manually compiled version?  If it's the official package, could you report this bug with postmarketOS, please?

These kinds of faults tend to happen when a library that Kasts depends on gets updated without Kasts itself getting recompiled.  Then you can end up with an instruction that has changed in the underlying lib without Kasts knowing about this, leading to a crash.  So, I would think it's simply a matter of recompiling the package.

If that still doesn't help, then please let me know, and so we can futher debug this.

Comment 2 Mark Grieveson 2023-11-23 12:37:52 UTC

(In reply to bart from comment #1)
> Is this happening with the postmarketOS Kasts package, or with a manually
> compiled version?  If it's the official package, could you report this bug
> with postmarketOS, please?
> 
> These kinds of faults tend to happen when a library that Kasts depends on
> gets updated without Kasts itself getting recompiled.  Then you can end up
> with an instruction that has changed in the underlying lib without Kasts
> knowing about this, leading to a crash.  So, I would think it's simply a
> matter of recompiling the package.
> 
> If that still doesn't help, then please let me know, and so we can futher
> debug this.

Hello.  Thank you for your feedback.  Yes, this is happening with the postmarketOS Kasts package.  I'm not sure where exactly I should report this to, but I did mention it on the [postmarketOS Lemmy site](https://lemmy.ca/post/9914444); so, hopefully someone from there will be made aware of it.

Thanks again for your feedback.  I appreciate all the work that people are doing to provide open source alternatives to us.

Comment 3 bart 2023-11-23 12:55:36 UTC

I directly contacted one of the pmOS devs and it seems they are already aware and have opened an internal bugreport (actually on alpine linux).  So I hope it gets addressed soon.  I will close this ticket now, since it's pretty clear that it's an alpine packaging problem.

https://gitlab.alpinelinux.org/alpine/aports/-/issues/15496