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

SIGSEGV on launch develop version #21

Closed
Fusion86 opened this issue Sep 4, 2023 · 3 comments
Closed

SIGSEGV on launch develop version #21

Fusion86 opened this issue Sep 4, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@Fusion86
Copy link
Contributor

Fusion86 commented Sep 4, 2023

Describe the bug
The latest develop release throws a SIGSEGV when starting Degate.

To Reproduce
Steps to reproduce the behavior:

  1. Build degate with Qt 6.5.2 GCC 64bit
  2. Launch the newly built executable in build/out/bin
  3. Critical error message.
Build ABI: 'x86_64-little_endian-lp64'
Kernel type: 'linux'
kernel version: '5.4.0-159-generic'
Current CPU architecture: 'x86_64'
Build CPU architecture: 'x86_64'
Product type: 'ubuntu'
Pretty product name: 'Ubuntu 20.04.6 LTS'
Product version: '20.04'
Degate version: '2.1.0-alpha.1'
Degate version type: 'nightly'
Degate release date: 'unreleased'
An unexpected error occurred. Error message:

'A SIGSEGV occurred (11).'

Possible fix
In MainWindow.cc the call QGuiApplication::screenAt(this->pos()) returns a nullptr on my machine. Not sure why, but it does. If I comment out that line (or add nullptr checks) the application starts just fine.
Possible fix -> Fusion86@0017bcb

Just reporting this here for completeness sake. I fixed my own issue, so feel free to close this if this doesn't belong here.

@DorianBDev DorianBDev added the bug Something isn't working label Sep 4, 2023
@DorianBDev
Copy link
Member

Hello, thanks for the bug report (and identifying the source). This seems to be related to #19 (Qt6 migration), something may have changed in Qt6. I will merge a fix in the next few minutes

@DorianBDev
Copy link
Member

@Fusion86 This should be fixed now with 3dc2861, can you confirm? Also thank you for other contributions related to deprecation warnings

@Fusion86
Copy link
Contributor Author

Fusion86 commented Sep 4, 2023

Yes, this fixes the issue for me. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants