Document Wayland/XWayland requirement for JabRef on Linux

[abilashini593]

User description

Added a Linux FAQ entry explaining that JabRef uses JavaFX and requires XWayland on Wayland-based systems.
This documents the solution discussed in issue #11489.

---

PR Type

Documentation

---

Description

• Added FAQ entry documenting Wayland/XWayland requirement

• Explains JavaFX dependency and XWayland necessity

• Provides solution for startup failures on Wayland systems

---

Diagram Walkthrough

flowchart LR
  A["Linux FAQ"] -->|"Add new section"| B["Wayland startup issue"]
  B -->|"Explains"| C["JavaFX requires XWayland"]
  C -->|"Solution"| D["Install XWayland"]

Loading

File Walkthrough

	Relevant files
Documentation	linux.md Add Wayland/XWayland FAQ entry                                                      en/faq/linux.md Added new FAQ section addressing Wayland startup failures Explains that JabRef uses JavaFX which requires XWayland Documents that missing XWayland causes startup failures Provides solution: install XWayland to resolve the issue +11/-0

---

[qodo-free-for-open-source-projects]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-free-for-open-source-projects]

PR Code Suggestions ✨

No code suggestions found for the PR.

[abilashini593]

Hi!
This PR documents the Wayland/XWayland startup issue discussed in #11489 by adding a short Linux FAQ entry.
Please let me know if you’d like the wording adjusted or the entry placed elsewhere.
Thanks!

[koppor]

The sentences should form a paragraph. Remove the empty lines inbetween.

Is there a nice link to xwayland which can be put?

[abilashini593]

Hi, this PR documents the Wayland/XWayland requirement discussed in #11489.
Kindly review when you have time. Thanks!

[subhramit]

Hi, this PR documents the Wayland/XWayland requirement discussed in #11489. Kindly review when you have time. Thanks!

You are not assigned to the issue. Please go through our contributing guidelines.

[koppor]

@abilashini593 look at this and fix it

[abilashini593]

Hi, thanks for the review.
I’ve updated newentryfromplaintext.md to clarify the explanation before the example.
Please let me know if further changes are needed.

[koppor]

AI incoming 😢