Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash on "Show Comms" button press #4747

Closed
MDutro opened this issue Nov 25, 2019 · 6 comments

Comments

@MDutro
Copy link

@MDutro MDutro commented Nov 25, 2019

Observed behaviour

Game crashes to desktop when I press "Show Comms" button on UI.

Expected behaviour

See comms.

Steps to reproduce

Start new game (any start), press "Show Comms"

My pioneer version (and OS):
Latest version for Linux 64-bit (downloaded today). OS - Manjaro Gnome

@MDutro

This comment has been minimized.

Copy link
Author

@MDutro MDutro commented Nov 25, 2019

Just for fun, I downloaded the Flatpak version. It works just fine, so it's possible that I didn't have some dependency or other?

@Web-eWorks

This comment has been minimized.

Copy link
Member

@Web-eWorks Web-eWorks commented Nov 25, 2019

Without a stacktrace, output.txt or any other detailed log of the error, we cannot diagnose or even attempt to fix the error. Please remember to follow the bug reporting guide when opening a crash bug.

@MDutro

This comment has been minimized.

Copy link
Author

@MDutro MDutro commented Nov 25, 2019

@Web-eWorks

This comment has been minimized.

Copy link
Member

@Web-eWorks Web-eWorks commented Nov 26, 2019

That's weird... the log shows that you do not have libpng12 installed - every time it tries to load an image, it attempts to load libpng12 and fails. This is likely the source of your crash. The flatpack version is bundled with all needed dependencies and therefore does not exhibit this behavior.

I'm not sure why the Manjaro repos don't link in libpng correctly, but if you install that version of libpng it should stop crashing. I'd appreciate it if you could test that and let us know how it goes.

As an addendum, could you capture a stacktrace using GDB of pioneer when it crashes? If you have the system 'core dumps' option enabled, running gdb /path/to/pioneer /path/to/dump/.12345 will allow you to print a stacktrace of the moment it crashed.

@mike-f1

This comment has been minimized.

Copy link
Contributor

@mike-f1 mike-f1 commented Nov 26, 2019

There's an old and closed issue with a long message chain which may help in order to have a background about libpng:

#3959

@Web-eWorks

This comment has been minimized.

Copy link
Member

@Web-eWorks Web-eWorks commented Dec 6, 2019

Closing as downstream issue; to my knowledge Pioneer builds against the system libpng version, which should be libpng16 for distros which only ship, well... libpng16.

@MDutro please test the steps outlined above; if that does not fix the issue please re-open with a new output.txt captured with a properly installed libpng12.

@Web-eWorks Web-eWorks closed this Dec 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.