×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

kstars segmentation fault in Fedora 33

  • Posts: 22
  • Thank you received: 0
Hello-

I am experiencing an instant segmentation fault when I try to start kstars on a Fedora 33 system. Both stable and bleeding packages have this issue. I am attaching a backtrace log file. Please let me know if there is anything further I can do to help.

Thank you.

File Attachment:

File Name: kstars_f33...race.log
File Size:4 KB
3 years 6 months ago #61609
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 535
  • Thank you received: 109
I think the issue was investigated here: bugzilla.redhat.com/show_bug.cgi?id=1881915, I have yet to test the change to the build as I have not installed F33 anywhere yet. I will work on that.

Jim
3 years 6 months ago #61611

Please Log in or Create an account to join the conversation.

  • Posts: 535
  • Thank you received: 109
There is a new package being created now for you to try. You can watch its progress here: copr.fedorainfracloud.org/coprs/xsnrg/ks...eding/build/1707405/

When (if) it builds successfully, you can do a `sudo dnf upgrade kstars --refresh` to make sure you get the latest package, assuming you have enabled the Copr.

Jim
Last edit: 3 years 6 months ago by Jim.
3 years 6 months ago #61613

Please Log in or Create an account to join the conversation.

  • Posts: 22
  • Thank you received: 0
Wow! That's cool. Thanks for the quick response. I'll install as soon as it's ready and report back. And yes, I'm using that repo.
3 years 6 months ago #61615

Please Log in or Create an account to join the conversation.

  • Posts: 22
  • Thank you received: 0
Unfortunately still crashing in F33. See gdb log file. I did have to add the stellarsolve repo for a new dependency.

File Attachment:

File Name: backtrace_...0-14.log
File Size:4 KB
3 years 6 months ago #61627
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 535
  • Thank you received: 109
Line 80 is quite basic stuff.... start the app:
QApplication app(argc, argv);

Investigating... will report back
3 years 6 months ago #61629

Please Log in or Create an account to join the conversation.

  • Posts: 22
  • Thank you received: 0
Ok. Keep in mind I only installed debuginfo rpms for kstars and indi. Not the QT libraries. So if the problem is in how kstars interacts with QT, I'm guessing my backtrace won't help you .
3 years 6 months ago #61630

Please Log in or Create an account to join the conversation.

  • Posts: 535
  • Thank you received: 109
I am suspecting that it is just something missing in the runtime that needs to be included in the spec file. I am going to try to build a F33 container to play with in a bit. Installing kstars should have forced some Qt5 packages to be installed with it if they were not already installed, so will see what the container does. If you want to pollute your system to get more information about the crash, I think `sudo dnf --enablerepo=fedora-debuginfo install qt5-qtbase-debuginfo` may be enough to fill in some blank spots.
3 years 6 months ago #61637

Please Log in or Create an account to join the conversation.

  • Posts: 22
  • Thank you received: 0
Thanks for that dnf suggestion. Here's the backtrace log with those rpms installed.

File Attachment:

File Name: backtrace.log
File Size:4 KB


Incidentally, I'm using the following to create the logs:
gdb
> run
# program crashes
> set logging file backtrace.log
> set logging on
> thread apply all bt full
> set logging off
> quit

This is from here: fedoraproject.org/wiki/StackTraces
3 years 6 months ago #61640
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 535
  • Thank you received: 109
Thanks for the updated backtrace. It did fill in a few gaps, so will have to look more at it. In the meantime I think I have a Dockerfile that should work to try to reproduce your error:
from amd64/fedora:33
USER root
RUN dnf upgrade -y --refresh
RUN dnf install -y dnf-utils
RUN dnf copr enable -y xsnrg/stellarsolver-bleeding
RUN dnf copr enable -y xsnrg/kstars-bleeding
RUN dnf install -y stellarsolver kstars
RUN kstars
3 years 6 months ago #61648

Please Log in or Create an account to join the conversation.

  • Posts: 535
  • Thank you received: 109
Spinning the Docker image up now and trying some things. From an initial look, everything seems to be available on the system. That rules out the quick easy stuff, unfortunately.

Here is an updated Dockerfile to play with for anyone else wanting to try:
from amd64/fedora:33
USER root
RUN dnf upgrade -y --refresh
RUN dnf install -y dnf-utils
RUN dnf copr enable -y xsnrg/stellarsolver-bleeding
RUN dnf copr enable -y xsnrg/kstars-bleeding
RUN dnf copr enable -y xsnrg/libindi-bleeding 
RUN dnf install -y stellarsolver kstars xeyes
RUN which kstars
RUN useradd user -G wheel
RUN echo "user	ALL=(ALL)	NOPASSWD: ALL" >> /etc/sudoers
USER user
CMD ["/bin/bash"]

Build:
sudo podman build -t fedora33 .

Run:
sudo podman run -ti -e DISPLAY --rm -v ~/.Xauthority:/root/.Xauthority:Z --net=host fedora33

substitute "docker" for "podman" in the above commands depending on your system
3 years 6 months ago #61659

Please Log in or Create an account to join the conversation.

  • Posts: 535
  • Thank you received: 109
Back to looking at this, I am able to reproduce it with the Docker container, and it does seem to be the error mentioned in the Fedora bug report in my initial response. I thought I had implemented the work-around in the latest build, but it did not work, so there are a couple other options to check. Will report back.

Jim
3 years 6 months ago #61666

Please Log in or Create an account to join the conversation.

Time to create page: 0.239 seconds