Fix a core dump on startup and warning on rexexp search for version number #707
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added libxcb-cursor-dev to correct startup error: Could not load the Qt platform plugin "xcb" in "" even though it was found. ...and its resulting core dump.
Fixes warning on startup.
Use raw string for regex
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request type
Please check the type of change your PR introduces:
What is the current behavior?
Performed a virgin install of Lubuntu 24.04 LTS and followed the steps in INSTALLATION.md to create the python3 virtual environment. Starting nanovna-saver app resulted in core dump. Seems the culprit is a missing installation of libxcb-cursur-dev. Once that installed, nanovna-saver app start and runs.
Notices a warning in checking for updates. Fixed my regexp search as well.
Issue Number: N/A
What is the new behavior?
Application run starts up and runs without core dumping or emitting warning about regexp.
Does this introduce a breaking change?
Other information