# JabRef 5.8 Release **URL:** \ **Category:** News\ **Created:** [December 19, 2022, 5:31pm UTC](https://discourse.jabref.org/t/jabref-5-8-release/3671 "2022-12-19T17:31:29Z")\ **Posts on this page:** 8\ **Page:** 1

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\ **Post date:** [December 19, 2022, 5:31pm UTC](https://discourse.jabref.org/t/jabref-5-8-release/3671/1 "2022-12-19T17:31:29Z")

We are proud to announce the release of version 5.8 of our favorite citation manager JabRef, just in time for the holidays! And a huge welcome to [@ThiloTe](https://github.com/ThiloteE) in our team of maintainers and as the new community manager! ## Notable Changes and New Features The most considerable change is the new 3-Way-Merge feature that was created by our [GSoC](https://summerofcode.withgoogle.com/) mentee [@HoussemNasri](https://github.com/HoussemNasri). This now allows you to easily review and edit changes when merging entries and cleaning up your database. Another huge advantage of this feature is the ability to merge groups, keywords, comments and files when merging entries. It will also display a warning if the authors are the same but just formatted differently. The External changes resolver dialog now also shows the preview of the entry and the option to merge entries using the new 3-Way-Merge feature. Another massive improvement under the hood is the reworked backup and saving feature of JabRef. JabRef will now regularly create automatic backups (up to 10) in the [user’s app dir](https://github.com/harawata/appdirs#supported-directories). In case an existing newer backup was found at startup, JabRef now provides a direct link to the backup folder to review the backup files. Additionally, the rework fixed many bugs related to saving and detecting changes in the library. We have improved the loading performance of large libraries. Especially Mac users with an Arm64 CPU (Apple M1) will now profit from a massive performance increase, as we now provide native builds for macOS on Arm64. Besides that, this release also contains several UI improvements (e.g wording, titles, styling) of dialogs, improved the contrast of the color scheme for highlighting search results and fixed a bug where JabRef would display the wrong group tree after opening more than one library. Another notable bug fix is the correct rendering of the fields, `issue`, `number`, `eid` and `pages` fields in the entry preview. A big thanks to [@ThiloTe](https://github.com/ThiloteE) for analyzing this complex issue, showing that the word “issue” can have multiple meanings, and providing a solution rationale! Be aware that if you have not yet configured a file directory, the global default directory for storing PDFs is now the documents folder in the user’s home. The fallback directory of the file folder is the general file directory. As we updated the full-text search engine to [Lucene](https://lucene.apache.org/) 9.4, JabRef will recreate the search index in the background on start. Switching back and forth between the current version and any older version will make JabRef repeat this process every time. As this will take some time for a huge databases with many linked files you can always choose to disable full text indexing. For a complete list of all our changes, take a look at the [Changelog](https://github.com/JabRef/jabref/blob/main/CHANGELOG.md#changelog). **You can get JabRef as free software from [FOSShub](https://www.fosshub.com/JabRef.html).** In case you notice any bugs or problems, please browse through our [bug tracker](https://github.com/JabRef/jabref/issues) and consider submitting a new bug report if nobody else has been reporting the failure before. ## Special Thanks The [JabRef Maintainers](https://github.com/JabRef/jabref/blob/main/MAINTAINERS) would like to give special thanks to all new and old contributors. We are delighted to see contributors opening pull requests and making translations or simply answering questions in our [support forum](https://discourse.jabref.org/). As we all work on JabRef in our leisure time, we feel honored that people share our enthusiasm for free software and work together to make research easier. A big thanks also to all our donators! Especially we would like to thank our GSoC mentee @HoussemNasri for his extensive work on JabRef and Google for providing the scholarship for his project in GSoC. We also want to thank all universities [including JabRef in their academic teaching](https://devdocs.jabref.org/teaching). Finally, we would like to thank all the users who are constantly testing the latest snapshots and giving feedback! The JabRef Maintainers wish everyone to explore the wide world of possibilities that literature management provides during the upcoming holidays with inner peace and joy! _**You like it? Foster JabRef development with [Knowledge](https://help.jabref.org/en/FAQcontributing) or [Money](https://donations.jabref.org).**_ ---

---

**Author:** ![gooksin](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@gooksin](https://discourse.jabref.org/u/gooksin)\ **Post date:** [December 20, 2022, 5:58pm UTC](https://discourse.jabref.org/t/jabref-5-8-release/3671/3 "2022-12-20T17:58:43Z")

Thank you for the new release! I encountered a problem trying to install the debian package (on a Debian 11, bullseye): ```auto dpkg-deb: error: archive 'jabref_5.8_amd64.deb' uses unknown compression for member 'control.tar.zst', giving up dpkg: error processing archive jabref_5.8_amd64.deb (--install): dpkg-deb --control subprocess returned error exit status 2 Errors were encountered while processing: jabref_5.8_amd64.deb ``` I could solve it by repackaging with these set of instructions: ```auto ar x jabref_5.8_amd64.deb zstd -d < control.tar.zst | xz > control.tar.xz zstd -d < data.tar.zst | xz > data.tar.xz ar -m -c -a sdsd jabref_5.8_amd64_repackaged.deb debian-binary control.tar.xz data.tar.xz rm debian-binary control.tar.* data.tar.* sudo dpkg -i jabref_5.8_amd64_repackaged.deb ``` Cheers, – gooksin ---

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\ **Post date:** [December 20, 2022, 6:13pm UTC](https://discourse.jabref.org/t/jabref-5-8-release/3671/4 "2022-12-20T18:13:14Z")

Thanks for the kind wors and the feedback, indeed you were not the only one having problems with the deb file: Seems like the compression algorithm is not supported by Debian. Here are some more details > > > \### JabRef version > > 5.8 (latest release) > > \### Operating system > > GNU / Linu…x > > \### Details on version and operating system > > Debian 11 Bullseye > > \### Checked with the latest development build > > \- \[X\] I made a backup of my libraries before testing the latest development version. > \- \[X\] I have tested the latest development version and the problem persists > > \### Steps to reproduce the behaviour > > Deb file of v. 5.8 is not installable due to \*\*unknown compression\*\*. Here is the steps to reproduce and the log: > > 1. \`sudo apt -f install ./jabref\_5.8\_amd64.deb\` > 2. > \`\`\` Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Note, selecting 'jabref' instead of './jabref\_5.8\_amd64.deb' > The following NEW packages will be installed: > jabref > 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. > Need to get 0 B/187 MB of archives. > After this operation, 227 MB of additional disk space will be used. > Get:1 ~/Scaricati/App/jabref\_5.8\_amd64.deb jabref amd64 5.8.60000 \[187 MB\] > dpkg-deb: error: archive '~/Scaricati/App/jabref\_5.8\_amd64.deb' uses unknown compression for member 'control.tar.zst', giving up dpkg: error processing archive ~/Scaricati/App/jabref\_5.8\_amd64.deb > (--unpack): > dpkg-deb --control subprocess returned error exit status 2 > Errors were encountered while processing: > ~/Scaricati/App/jabref\_5.8\_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > \`\`\` > > Many thanks in advance, > > \### Appendix > > \ > > \Log File\ > > \`\`\` > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Note, selecting 'jabref' instead of './jabref\_5.8\_amd64.deb' > The following NEW packages will be installed: > jabref > 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. > Need to get 0 B/187 MB of archives. > After this operation, 227 MB of additional disk space will be used. > Get:1 ~/Scaricati/App/jabref\_5.8\_amd64.deb jabref amd64 5.8.60000 \[187 MB\] > dpkg-deb: error: archive '~/Scaricati/App/jabref\_5.8\_amd64.deb' uses unknown compression for member 'control.tar.zst', giving up dpkg: error processing archive ~/Scaricati/App/jabref\_5.8\_amd64.deb > (--unpack): > dpkg-deb --control subprocess returned error exit status 2 > Errors were encountered while processing: > ~/Scaricati/App/jabref\_5.8\_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > \`\`\` > > \ ---

**Author:** ![schroer-berlin](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/schroer-berlin/32/1532_2.png) [@schroer-berlin](https://discourse.jabref.org/u/schroer-berlin)\ **Post date:** [December 22, 2022, 1:52pm UTC](https://discourse.jabref.org/t/jabref-5-8-release/3671/5 "2022-12-22T13:52:44Z")

“JabRef-5.8.msi” startet bei mir nicht. ---

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\ **Post date:** [December 22, 2022, 3:32pm UTC](https://discourse.jabref.org/t/jabref-5-8-release/3671/6 "2022-12-22T15:32:35Z")

Hi, gibt es eine Fehlermeldung oder Ähnliches? Wir bräuchten ein bisschen mehr Kontext dazu damit wir helfen können ---

**Author:** ![gooksin](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@gooksin](https://discourse.jabref.org/u/gooksin)\ **Post date:** [December 22, 2022, 3:55pm UTC](https://discourse.jabref.org/t/jabref-5-8-release/3671/7 "2022-12-22T15:55:27Z")

Thank you! I’m sorry I failed to notice that an issue was already opened. ---

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\ **Post date:** [January 16, 2023, 9:20pm UTC](https://discourse.jabref.org/t/jabref-5-8-release/3671/8 "2023-01-16T21:20:13Z")