-
Notifications
You must be signed in to change notification settings - Fork 801
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
Segmentation fault in LTO build #2790
Comments
I can confirm this is an issue on Ubuntu 20.04 as well (apt package and AppImage) though I don't have any idea how to obtain this log with gdb. I also experience the same thing with the Telegram desktop client but haven't found a corresponding issue yet. |
Is there still no fix or even a workaround in sight? 😞 |
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
The bug still exists on my Ubuntu 20.04 LTS installation, so I don't see a reason to close it. |
|
Still occurring with 3.1.3 on Debian sid. |
Ok I tried the packaged version that comes with Ubuntu 20.04 and that version seemed to work till I ran the AppImage or 3.2.0rc3 (which on its own runs smooth). If I try to go back to the packaged version the version start and is doing is thing for 20s or so and afterwards displays the segmentation fault (core dumped) again. It's getting even more confusing by now.... |
@Toorero That is because the sync database of 3.2.0-rc3 and 3.1.3 are incompatible. In general it is not supported to downgrade. To recover from that you need to delete the sync database while the client is not running. The sync database are the files beginning with |
Ah ok so then the bug is fixed (at least for me) and the testing just destroyed the sync-base. I can live with that. |
Still present with 3.2.0 on Debian sid. Sadly the test-suite passes now with 3.2.0, cause the version test does not fail anymore on a |
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you! |
Still an issue with 3.6.1 on Debian sid. |
Still an issue with 3.9.1 |
Still an issue with 3.12.6 |
How to use GitHub
Expected behaviour
functional program
Actual behaviour
Segmentation fault
Steps to reproduce
-flto
nextcloud --version
Client configuration
Client version: 3.1.1
Operating system: Debian sid
OS language: en
Qt version used by client package (Linux only, see also Settings dialog): 5.15.2
Client package (From Nextcloud or distro) (Linux only): adopted Debian package
Installation path of client: /usr/bin/nextcloud
Logs
gdb stacktrace:
Probably related to https://gitlab.com/wireshark/wireshark/-/issues/17040
The text was updated successfully, but these errors were encountered: