jabref-5.5.60000-1.x86_64 or JabRef-5.5-portable_linux.tar.gz on CentOS-7 x86_64: free(): invalid pointer: 0x00002b19113d2c80 #8579
Comments
|
with the latest development version (jabref-5.6.98-1.x86_64,rpm): but a GUI appears with the above messages. |
|
Same progress with the portable version |
|
the error for version 5.5 looks like the same one reported at https://discourse.jabref.org/t/5-2-1-problems-under-centos-7-2-2009/2554/4 for version 5.2.1 |
|
Thanks, I think I found the issue. Related to the fulltxt index directory. As a workaround, you can manually create the directory |
Siedlerchr
added a commit
that referenced
this issue
Mar 17, 2022
|
thx, that has removed the error for the current dev. version: nothing changed (as expected )for the 5.5 issue. |
Siedlerchr
added a commit
that referenced
this issue
Mar 17, 2022
Siedlerchr
pushed a commit
that referenced
this issue
Mar 26, 2022
* Design the preference section for adding custom SSL certificates * Inject custom certificates FXML views into the controller * Delete unused import * Allow for enabling or disabling custom certificates * Use LocalDate instead of LocalDateTime for tracking certificate validity * Populate CustomCertificateViewModel with data from SSLCertificate - Added a method to map X509Certificate to SSLCertificate * Setup cell factory and populate the table with dummy data * Add '.cer' to StandardFileType * Open file explorer on 'Add certificate' clicked * Copy JDK 17 truststore into project resources * Bump JavaFX from 17.0.2 to 18 (#8577) * Bump JavaFX from 17.0.2 to 18 * Remove mac os hack for maintable Copy Preview content and not entry Co-authored-by: Siedlerchr <[email protected]> * Fix missing search index dir (#8581) Fixes #8579 * Log user added certificates information * Add an alias property to SSLCertificate that is generated randomly - A keystore contains a list of certificate entries, each of which is identified by a unique alias. For now, I'll generate aliases at random, but in the future, it would be better if users entered them. * Create TrustStoreManager for truststore manipulation * Add SSLPreferences * Set custom certificate preferences defaults * Persist 'useCustomCertificate' boolean preference * Use certificate thumbprint as an alias For the alias to be useful it has to be unique, I thought about using the serial number, but it is only unique for the CA, so I created a hash of all fields in the certificate * Delete dummy certificates and use real imported certificate information * Move certificate version formatting logic to the view * Move TrustStoreManager from GUI to Logic * Use Integer to store version instead of primitive int * Persist thumbprint, version, validFrom and validTo columns * Use localized strings * Fix failing test * Persist all certificate columns * Load truststore path from preferences * Deprecate bypassSSLVerification() and delete its usage - I didn't delete it because users might want to enable ssl bypassing from SSL configuration * Set truststore path at startup * Store truststore path in preference * Update CHANGELOG.md * Add an icon to 'Add certificate' button * Update truststore file on save preference * Clear all custom certificates from the truststore at preference reset * Use truststore as the single source of truth * Show warning dialog on attempting to add a duplicate certificate - Minor refactoring - Added certificate deletion to UI - i18n * Stop allowing for toggling custom certificates usage * Delete SSL certificates * Fix failing test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JabRef version
5.5 (latest release)
Operating system
GNU / Linux
Details on version and operating system
CentOS-7 x86_64 updated as of 2022/03/17
Checked with the latest development build
Steps to reproduce the behaviour
Appendix
The text was updated successfully, but these errors were encountered: