Skip to content

Document Wayland/XWayland requirement for JabRef on Linux #606

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.

Sign up for GitHub

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

Closed
abilashini593 wants to merge 3 commits into from
+8 −0
Closed

Document Wayland/XWayland requirement for JabRef on Linux #606

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e531406
Update linux.md
abilashini593 Dec 26, 2025
d81a805
Update Wayland startup instructions for JabRef
abilashini593 Dec 26, 2025
0c1b682
Update newentryfromplaintext.md
abilashini593 Dec 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions en/collect/newentryfromplaintext.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,15 @@
Different parsers will lead to different results. It is strongly recommended to fact-check all conversions, regardless of parser choice. All of them can confabulate. For comparison, [adding entries using an ID](add-entry-using-an-id.md) is much more reliable and accurate.
{% endhint %}

The following example shows how a plain reference text can be pasted and converted into a BibTeX entry.

Example:

```

Check failure on line 15 in en/collect/newentryfromplaintext.md

View workflow job for this annotation

GitHub Actions / lint

Fenced code blocks should have a language specified [Context: "```"] 

en/collect/newentryfromplaintext.md:15 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
O. Kopp, A. Armbruster, und O. Zimmermann, "Markdown Architectural Decision Records: Format and Tool Support", in 10th ZEUS Workshop, 2018.
```

1. Click Library and select "New entry from plain text..." Alternatively, you can press Ctrl+Shift+N.

Check failure on line 19 in en/collect/newentryfromplaintext.md

View workflow job for this annotation

GitHub Actions / lint

Spaces after list markers [Expected: 1; Actual: 2] 

en/collect/newentryfromplaintext.md:19:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]

<div align="left"><figure><picture><source srcset="../.gitbook/assets/Bild 1 - dark mode.jpg" media="(prefers-color-scheme: dark)"><img src="../.gitbook/assets/Bild 1.png" alt=""></picture><figcaption></figcaption></figure></div>
2. The "Plain Reference Parser" window opens
Expand Down
6 changes: 6 additions & 0 deletions en/faq/linux.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,3 +31,9 @@ In the background, JabRef uses [JavaFX](https://en.wikipedia.org/wiki/JavaFX). A
## Where can I find JabRef's log files?

A: On Linux, the path to the log files is `~/.local/share/jabref/logs/$version/`

## JabRef does not start on Wayland (Sway, Wayland GNOME, etc). What should I do?

JabRef uses JavaFX for its user interface. Currently, JavaFX requires [XWayland](https://wayland.freedesktop.org/xserver.html) to run on Wayland-based systems. If XWayland is not installed, JabRef may fail to start. Installing XWayland usually resolves this issue.


Loading