imagej / imagej/ImageJ

Unresponsive menu "install plugin"

Open
#264 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
786
Forks
267
PR merge metrics
No merged PRs in 30d

Description

in FIJI, when I hit the submenu "Install plugin..." in order to browse the available plugins for installation, nothing happens. No error messages, no warnings or log recording, no events as far as I can tell... Untiltwo days ago, when I hit this submenu in the original interface of FIJI, I could get a dialog that allowed me to manage the plugins and unistall or install at wish, Now nothing happens.
It all started after I installed (from that dialog) a plugin for allowing to work with Excel files.
As I didn't find a clue, I opted to uninstall (delete folder) FIJI and download the last version, which I installed right away.
To no avail.

I found that FIJI was using Java 1.8.0_322 while my system (Windows11 64bit) is using 1.8.0_431. Then I found in internet that by renaming the "java" folder I could force FIJI to turn to my system's java version, which worked in terms of changing java version (ImageJ2 2.14.0/1.54f; Java 1.8.0_431 [amd64]), but was of no help in terms of the functionality of the menu.

I would like to see if there is a solution or workaround.

BTW I checked for the menu in other computer that has Java 1.8.0_421 but Fiji is 1.8.0_172 (ImageJ2 2.14.0/1.54f; Java 1.8.0_172 [amd64]). The menu does not work there either.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the unresponsive "Install plugin..." submenu in FIJI on the reported Java versions and compare the behavior with the plugin-management dialog described in the report. Inspect the menu action and its logging or event behavior; done means identifying the failure or a reproducible workaround and documenting the result.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.