Document app freeze with wrong password prompt integration.

[heyitsdross]

Closes #11766

Document freezes in preferences panel resulting from improper password prompter integration on dev machine for developers.

Mandatory checks

• Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
• Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• Screenshots added in PR description (for UI changes)
• Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
• Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

[Siedlerchr]

Thanks!
PS: I can recommend markdown lint for VsCode https://marketplace.visualstudio.com/items?itemName=DavidAnson.vscode-markdownlint

[github-actions]

You modified Markdown (*.md) files and did not meet JabRef's rules for consistently formatted Markdown files.
To ensure consistent styling, we have markdown-lint in place.
Markdown lint's rules help to keep our Markdown files consistent within this repository and consistent with the Markdown files outside here.

You can check the detailed error output by navigating to your pull request, selecting the tab "Checks", section "Tests" (on the left), subsection "Markdown".

[heyitsdross]

@Siedlerchr I'm using IntelliJ, in which there seems to be no plugin for markdownlint. There's a ruby gem and a node package, but I'm unsure if I can run either locally against the project and have it work.

[Siedlerchr]

Yeah here as well but that's why I edit the markdown stuff with VsCode

[heyitsdross]

@Siedlerchr Sensible, sensible. Apparently there's a plugin for neovim or something, I'll get that up and running at some point, but to be honest, it's kind of sad that there's no command line utility written in Rust or C or something which can perform the linting.

[subhramit]

@Siedlerchr Sensible, sensible. Apparently there's a plugin for neovim or something, I'll get that up and running at some point, but to be honest, it's kind of sad that there's no command line utility written in Rust or C or something which can perform the linting.

You can also always use the github web vscode editor (and install the markdown-lint extension on the fly). Just press "." in the PR when you want to edit. You can also preview the markdown while editing that way.

[koppor]

@Siedlerchr I'm using IntelliJ, in which there seems to be no plugin for markdownlint.

What about https://github.com/Strajk/intellij-plugin-markdownlint?

It is said to be slow (Strajk/intellij-plugin-markdownlint#4), but could work?

[koppor]

but to be honest, it's kind of sad that there's no command line utility written in Rust or C or something which can perform the linting.

Smalltalk: https://github.com/0xpayne/gpt-migrate on https://github.com/DavidAnson/markdownlint 🤣🤣

Note that one can use npx markdownlint. Then, npx installs the latest version of the package and runs it. OK, still some NodeJS is required ^^.

[koppor]

Is it possible to detail "Ensure that these are working properly"? Maybe, giving an example?

[heyitsdross]

We could detail what some of the desired states would be, ie. If everything works, a password prompt will appear as the program starts, given the keyring your OS uses hasn't already been unlocked.

The trouble is, it depends on OS what the exact implementation being used is, and therefore how to configure it will vary. I don't have Windows or MacOS personally, so I can only speak for Linux users and state that their xdg-desktop-portal settings need to refer to active and valid portal implementations they have installed. And that may not be the whole story; my lack of knowledge means I'd need to do further research to confirm or deny that.

[koppor]

I think, even these sentences help.

What do you think of:

To clarify, in an ideal scenario, a password prompt should appear when the program starts, provided the keyring your OS uses has not already been unlocked. However, the implementation details vary depending on the operating system, which makes troubleshooting more complex.

For Windows and macOS users, specific configurations may differ based on the password management tools and settings used, so ensure your OS's password management system is properly set up and functioning.

For Linux users, ensure that your `xdg-desktop-portal` settings refer to active and valid portal implementations installed on your system. However, there might be other factors involved, so additional research or guidance specific to your distribution may be necessary.

[heyitsdross]

Looks good to me, we can always change the description if we learn more later.

Should I reopen the issue, or just make a PR for the same issue? Or rather document the change in a new issue?

[Siedlerchr]

just make another PR, e.g. follow up to ###