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

Segmentation Fault when creating and deleting unsaved entries (specific steps) #4084

Closed
guihkx opened this issue Jan 3, 2020 · 7 comments
Closed
Assignees

Comments

@guihkx
Copy link
Contributor

guihkx commented Jan 3, 2020

Expected Behavior

No SEGFAULT

Current Behavior

SEGFAULT

Steps to Reproduce

  1. Create a new entry, pick any title and click OK.
  2. Now delete the recently created entry.
  3. Create another entry, pick any title, but now you click Cancel instead.
  4. A dialog will pop up, asking you to: Save, Discard or Cancel.
  5. Choose: Discard.
  6. KeePassXC will crash with segfault

Debug Info

KeePassXC - Version 2.5.1
Revision: 0fd8836

Qt 5.14.0
Debugging mode is disabled.

Operating system: Arch Linux
CPU architecture: x86_64
Kernel: linux 5.4.7-zen1-1-zen

Enabled extensions:

  • Auto-Type
  • Browser Integration
  • SSH Agent
  • KeeShare (signed and unsigned sharing)
  • YubiKey
  • Secret Service Integration

Cryptographic libraries:
libgcrypt 1.8.5

@guihkx guihkx added the bug label Jan 3, 2020
@droidmonkey
Copy link
Member

This is fixed in 2.5.2 releasing tomorrow.

@guihkx
Copy link
Contributor Author

guihkx commented Jan 6, 2020

Just updated to 2.5.2, still can reproduce this.

@guihkx
Copy link
Contributor Author

guihkx commented Jan 6, 2020

Found out this is only reproducible if you've disabled the recycle bin in your database.

@droidmonkey
Copy link
Member

Good to know!!

@guihkx
Copy link
Contributor Author

guihkx commented Jan 7, 2020

I've tried capturing a trace with gdb. Hope it's helpful:

gdb.txt

@droidmonkey
Copy link
Member

Yes it is helpful and points to exactly what I suspected the problem was. It is directly related to the bug I reported yesterday: #4093

@droidmonkey
Copy link
Member

This has been fixed in 2.6

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

No branches or pull requests

2 participants