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

Selecting "Customized Preview Style" causes uncaught exception #8280

Closed
2 tasks done
wujastyk opened this issue Nov 26, 2021 · 1 comment · Fixed by #8293
Closed
2 tasks done

Selecting "Customized Preview Style" causes uncaught exception #8280

wujastyk opened this issue Nov 26, 2021 · 1 comment · Fixed by #8293
Labels
bug Confirmed bugs or reports that are very likely to be bugs entry-preview

Comments

@wujastyk
Copy link

wujastyk commented Nov 26, 2021

JabRef version

Other (please describe below)

Operating system

GNU / Linux

Details on version and operating system

JabRef 5.4--2021-11-25--7aaf5e2 Linux 5.11.0-40-generic amd64 Java 16.0.2 JavaFX 17.0.1+1

Checked with the latest development build

  • I made a backup of my libraries before testing the latest development version.
  • I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

  1. Options / Preferences / Entry Preview /
  2. Select Customized preview style (first "Available" entry)
  3. Tried a random edit, and got this:

image

I can reproduce this reliably.

  1. Select any "Available" journal style
  2. click the XML window below
  3. go back to the journal style window and click on another style name
  4. the uncaught exception window pops up.

Appendix

...

Log File
java.lang.NullPointerException: Cannot invoke "org.jabref.logic.preview.PreviewLayout.getDisplayName()" because "this.layout" is null
	at [email protected]/org.jabref.gui.preview.PreviewViewer.lambda$update$6(Unknown Source)
	at [email protected]/org.jabref.gui.util.DefaultTaskExecutor.lambda$getJavaFXTask$3(Unknown Source)
	at [email protected]/com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(Unknown Source)
	at [email protected]/com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(Unknown Source)
	at [email protected]/com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(Unknown Source)
	at [email protected]/com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Unknown Source)
	at [email protected]/com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Unknown Source)
	at [email protected]/com.sun.javafx.event.EventUtil.fireEventImpl(Unknown Source)
	at [email protected]/com.sun.javafx.event.EventUtil.fireEvent(Unknown Source)
	at [email protected]/javafx.event.Event.fireEvent(Unknown Source)
	at [email protected]/javafx.concurrent.EventHelper.fireEvent(Unknown Source)
	at [email protected]/javafx.concurrent.Task.fireEvent(Unknown Source)
	at [email protected]/javafx.concurrent.Task.setState(Unknown Source)
	at [email protected]/javafx.concurrent.Task$TaskCallable.lambda$call$0(Unknown Source)
	at [email protected]/com.sun.javafx.application.PlatformImpl.lambda$runLater$10(Unknown Source)
	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
	at [email protected]/com.sun.javafx.application.PlatformImpl.lambda$runLater$11(Unknown Source)
	at [email protected]/com.sun.glass.ui.InvokeLaterDispatcher$Future.run(Unknown Source)
	at [email protected]/com.sun.glass.ui.gtk.GtkApplication._runLoop(Native Method)
	at [email protected]/com.sun.glass.ui.gtk.GtkApplication.lambda$runLoop$11(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)

@Siedlerchr Siedlerchr added bug Confirmed bugs or reports that are very likely to be bugs entry-preview labels Nov 27, 2021
@Siedlerchr
Copy link
Member

I could reproduce this as well following your instructions, but one has to first click into the Edit field...

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 entry-preview
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants