Closed rolandog closed 4 years ago
Thanks for your report. It would be helpful if you could tell us which key pattern you have defined for the entry type or if you are using the default pattern
Hi @Siedlerchr ! Thanks for your reply!
I don't think I have modified the defaults;
If I click on the 'reset' button on the entry, a value of [auth][year]
appears, instead of a blank value... but the behaviour is the same: the entry's generated key still contains null
.
This may or may not be helpful, but I noticed that most of the "corporate" authors are not displayed properly; here's a screenshot on how the column is displayed for the author {Commission on Isotopic Abundances and Atomic Weights}
:
I don't think I have any odd settings on the 'Entry Table' settings:
Just to be on the safe side, I reset all my preferences, restarted JabRef, modified the entry's key, re-generated it and got the same results; also the same problem was present with the format of the corporate author's name in the author's column.
Tomorrow morning I'll try uninstalling, removing configuration files, and see if there are any different results.
Thanks for your feedback! Resetting preferences was enough as clarification. Looks really like a bug,
I can take a look at this?
@k3KAW8Pnf7mkmdSMPHz27 Sure go ahead
Thanks to @k3KAW8Pnf7mkmdSMPHz27 this should be fixed in the latest development version. Could you please check the build from http://builds.jabref.org/master/. Thanks! Please remember to make a backup of your library before trying-out this version.
JabRef version JabRef 5.0--2020-03-06--2e6f433 on Ubuntu 19.10
Steps to reproduce the behavior:
Sample Bibliography
Log File
No events were generated in the event log, even though I followed procedure according to [the docs](https://docs.jabref.org/general/commandline), and I ran both the `.deb` and Portable versions (the latter I ran with the following options: `./JabRef --console --debug`). This was the output on the terminal: ``` ERROR StatusLogger Unrecognized format specifier [d] ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [thread] ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [level] ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [logger] ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [msg] ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [n] ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [d] ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [thread] ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [level] ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [logger] ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [msg] ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern. ERROR StatusLogger Unrecognized format specifier [n] ERROR StatusLogger Unrecognized conversion specifier [n] starting at position 56 in conversion pattern. (java:20862): Gdk-WARNING **: 18:01:46.992: XSetErrorHandler() called with a GDK error trap pushed. Don't do that. ```