SUMMARY * QA Notice: Package triggers severe warnings which indicate that it * may exhibit random runtime failures. * /var/tmp/portage/sci-astronomy/kstars-3.6.7/work/kstars-3.6.7/kstars/fitsviewer/fpackutil.c:1333:46: warning: passing argument 4 of ‘ffomem’ from incompatible pointer type [-Wincompatible-pointer-types] * /var/tmp/portage/sci-astronomy/kstars-3.6.7/work/kstars-3.6.7/kstars/fitsviewer/fpackutil.c:1334:35: warning: passing argument 2 of ‘ffimem’ from incompatible pointer type [-Wincompatible-pointer-types] strip: x86_64-pc-linux-gnu-strip --strip-unneeded -N __gentoo_check_ldflags__ -R .comment -R .GCC.command.line -R .note.gnu.gold-version /usr/lib64/libhtmesh.a x86_64-pc-linux-gnu-strip: /var/tmp/portage/sci-astronomy/kstars-3.6.7/image/usr/lib64/stjYmeTx/mocs_compilation.cpp.o: plugin needed to handle lto object /usr/bin/kstars STEPS TO REPRODUCE un-installed and re-installed OBSERVED RESULT seg. fault EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.14 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.7.1-gentoo-r1-x86_64 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4080/PCIe/SSE2 ADDITIONAL INFORMATION
Please provide a backtrace from the crash so the developers can identify and action the problem. There are instructions on how to do so here: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Backtraces
Created attachment 165856 [details] attachment-665600-0.html I sorry forgot to run gdb -q /usr/bin/kstars I just did and it produced nothing. I've no idea why. Then I had a thought, my box is running the gcc option "flto=auto". So I put the kstars in my noltobuild as per Gentoo instructions. This has now allowed kstars as normal. On Fri, Feb 16, 2024, 5:58 a.m. Ben Bonacci <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=481270 > > Ben Bonacci <ben@benbonacci.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > Resolution|--- |BACKTRACE > CC| |ben@benbonacci.com > > --- Comment #1 from Ben Bonacci <ben@benbonacci.com> --- > Please provide a backtrace from the crash so the developers can identify > and > action the problem. > There are instructions on how to do so here: > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Backtraces > > -- > You are receiving this mail because: > You reported the bug.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!