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

Xiphos 4.2.1.7 crashes whenever I open it #1117

Closed
chriswadams opened this issue Oct 26, 2022 · 2 comments
Closed

Xiphos 4.2.1.7 crashes whenever I open it #1117

chriswadams opened this issue Oct 26, 2022 · 2 comments

Comments

@chriswadams
Copy link

Every time I try to open Xiphos 4.2.1.7, on openSuSe Leap 15.4, it crashes with the following error message:

[CODE]BUG! Xiphos is about to crash due to a "STRDUP" error.
Please report this error to the Xiphos team with:

/home/abuild/BUILD/xiphos-4.2.1.7/src/main/display.cc:1067 "%s %s

'[/CODE]

This appears to be the same problem as issue #523, closed Feb 29, 2016. In the thread for that issue, Karl Kleinpaste wrote: "the specific bug mentioned here was actually fixed long ago and that fix is already present in 4.0.0. but testing for your report uncovered another bug, a sort of ancillary bug, which has now also been fixed, and will be part of our next release."

I've tried updating both SuSe and Xiphos, but the crashes still happen. Karl also mentioned that there are builds for Ubuntu and Fedora, but nothing specifically for SuSe. I could try changing my OS to one of those two, if that's my only option, but I'd like to know if there are other possibilities before going down that road. Any help would be appreciated.

Thanks!
-chriswadams

@Crissium
Copy link

Actually I can recall that years ago when I was on Leap 15.2 (?), something similar happened to me.

I created a list of parallel modules, and when I restarted, I got the same error. Then I removed all xiphos config files (not necessarily deleted, just moved away) and it started up without error again.

Hope this can help you.

@chriswadams
Copy link
Author

Success! Thank-you for the advice, Crissium!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants