You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The latest develop release throws a SIGSEGV when starting Degate.
To Reproduce
Steps to reproduce the behavior:
Build degate with Qt 6.5.2 GCC 64bit
Launch the newly built executable in build/out/bin
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.
The text was updated successfully, but these errors were encountered:
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
Describe the bug
The latest develop release throws a SIGSEGV when starting Degate.
To Reproduce
Steps to reproduce the behavior:
Possible fix
In
MainWindow.cc
the callQGuiApplication::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.
The text was updated successfully, but these errors were encountered: