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

Exception in opening bib file #3342

Closed
sambo57u opened this issue Oct 24, 2017 · 2 comments
Closed

Exception in opening bib file #3342

sambo57u opened this issue Oct 24, 2017 · 2 comments
Labels
bug Confirmed bugs or reports that are very likely to be bugs

Comments

@sambo57u
Copy link

At some point during the 4.1dev development this started to happen. The problem is not there with 4.0
and was not there with 4.1dev until a couple of weeks ago.

It is unusual in that the exception only occurs when giving a bib file to jabref e.g.

java -jar /usr/share/jabref VU_bibtex_master.bib

When you just start jabref via "java -jar /usr/share/jabref" it starts and then I can open the bib file fine.
It does not depend on the name or content of the bib file. I tried java 1.8.0_151 or _152. The error is:

=======================
12:10:20.060 [AWT-EventQueue-0] INFO org.jabref.logic.importer.OpenDatabase - Opening: VU_bibtex_master.bib
File: grouptree.fxml not found, attempting with camel case
File: grouptree.css not found, attempting with camel case
12:10:21.285 [AWT-EventQueue-0] ERROR org.jabref.FallbackExceptionHandler - Uncaught exception occurred in Thread[AWT-EventQueue-0,6,main]
java.lang.NullPointerException: null
at org.jabref.gui.util.FileUpdateMonitor.addListenerForFile(FileUpdateMonitor.java:75) ~[jabref:?]
at org.jabref.collab.DatabaseChangeMonitor.lambda$new$0(DatabaseChangeMonitor.java:40) ~[jabref:?]
at java.util.Optional.ifPresent(Optional.java:159) ~[?:1.8.0_162-ea]
at org.jabref.collab.DatabaseChangeMonitor.(DatabaseChangeMonitor.java:38) ~[jabref:?]
at org.jabref.gui.BasePanel.(BasePanel.java:231) ~[jabref:?]
at org.jabref.gui.JabRefFrame.addTab(JabRefFrame.java:1598) ~[jabref:?]
at org.jabref.gui.JabRefFrame.addParserResult(JabRefFrame.java:1301) ~[jabref:?]
at org.jabref.JabRefGUI.openWindow(JabRefGUI.java:134) ~[jabref:?]
at org.jabref.JabRefGUI.(JabRefGUI.java:63) ~[jabref:?]
at org.jabref.JabRefMain.lambda$start$1(JabRefMain.java:150) ~[jabref:?]
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311) ~[?:1.8.0_162-ea]
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758) ~[?:1.8.0_162-ea]
at java.awt.EventQueue.access$500(EventQueue.java:97) ~[?:1.8.0_162-ea]
at java.awt.EventQueue$3.run(EventQueue.java:709) ~[?:1.8.0_162-ea]
at java.awt.EventQueue$3.run(EventQueue.java:703) ~[?:1.8.0_162-ea]
at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_162-ea]
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80) ~[?:1.8.0_162-ea]
at java.awt.EventQueue.dispatchEvent(EventQueue.java:728) ~[?:1.8.0_162-ea]
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205) [?:1.8.0_162-ea]
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) [?:1.8.0_162-ea]
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) [?:1.8.0_162-ea]
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) [?:1.8.0_162-ea]
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) [?:1.8.0_162-ea]
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82) [?:1.8.0_162-ea]
^C$ export JAVA_HOME=/usr/java/jdk1.8.0;java -jar /usr/share/jabref VU_bibtex_master.bib
12:19:40.295 [AWT-EventQueue-0] INFO org.jabref.logic.importer.OpenDatabase - Opening: VU_bibtex_master.bib
File: grouptree.fxml not found, attempting with camel case
File: grouptree.css not found, attempting with camel case
12:19:41.395 [AWT-EventQueue-0] ERROR org.jabref.FallbackExceptionHandler - Uncaught exception occurred in Thread[AWT-EventQueue-0,6,main]
java.lang.NullPointerException: null
at org.jabref.gui.util.FileUpdateMonitor.addListenerForFile(FileUpdateMonitor.java:75) ~[jabref:?]
at org.jabref.collab.DatabaseChangeMonitor.lambda$new$0(DatabaseChangeMonitor.java:40) ~[jabref:?]
at java.util.Optional.ifPresent(Optional.java:159) ~[?:1.8.0_162-ea]
at org.jabref.collab.DatabaseChangeMonitor.(DatabaseChangeMonitor.java:38) ~[jabref:?]
at org.jabref.gui.BasePanel.(BasePanel.java:231) ~[jabref:?]
at org.jabref.gui.JabRefFrame.addTab(JabRefFrame.java:1598) ~[jabref:?]
at org.jabref.gui.JabRefFrame.addParserResult(JabRefFrame.java:1301) ~[jabref:?]
at org.jabref.JabRefGUI.openWindow(JabRefGUI.java:134) ~[jabref:?]
at org.jabref.JabRefGUI.(JabRefGUI.java:63) ~[jabref:?]
at org.jabref.JabRefMain.lambda$start$1(JabRefMain.java:150) ~[jabref:?]
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311) ~[?:1.8.0_162-ea]
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758) ~[?:1.8.0_162-ea]
at java.awt.EventQueue.access$500(EventQueue.java:97) ~[?:1.8.0_162-ea]
at java.awt.EventQueue$3.run(EventQueue.java:709) ~[?:1.8.0_162-ea]
at java.awt.EventQueue$3.run(EventQueue.java:703) ~[?:1.8.0_162-ea]
at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_162-ea]
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80) ~[?:1.8.0_162-ea]
at java.awt.EventQueue.dispatchEvent(EventQueue.java:728) ~[?:1.8.0_162-ea]
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205) [?:1.8.0_162-ea]
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) [?:1.8.0_162-ea]
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) [?:1.8.0_162-ea]
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) [?:1.8.0_162-ea]
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) [?:1.8.0_162-ea]
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82) [?:1.8.0_162-ea]

@sambo57u
Copy link
Author

PS: Using Linux x86_64

@Siedlerchr Siedlerchr added the bug Confirmed bugs or reports that are very likely to be bugs label Oct 24, 2017
@Siedlerchr
Copy link
Member

Thanks for your report, I could reproduce the issue under Win and prepared a fix. Will be in the next dev version, as soon as #3343 is merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs
Projects
None yet
Development

No branches or pull requests

2 participants