Fiji not starting up?

[Rebecca Keller]

Anyone having trouble starting up Fiji? I am on a win7 64-bit machine, just
had it going, restarted and updated, and now cannot start it--the Fiji logo
comes up, then nothing happens. Not good....

JPK

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[Saalfeld, Stephan]

Hi JPK,

please try to restart your computer, and then try to start Fiji.  The
Fiji process occasionally stays alive silently (which is a bug),
preventing a new instance from starting.  Restarting the PC would kill
this defunct instance, allowing a new instance to start.  You could also
find and kill it through the task manager if you find it there.

If that doesn't cure the problem, something serious is wrong.  Please
let us know.

Best,
Stephan



On Sun, 2014-12-21 at 22:40 -0500, Rebecca Keller wrote:
> Anyone having trouble starting up Fiji? I am on a win7 64-bit machine, just
> had it going, restarted and updated, and now cannot start it--the Fiji logo
> comes up, then nothing happens. Not good....
>
> JPK
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[Rebecca Keller]

Yes, I had already tried both task mgr and restarting, to no avail.​ But I
guess no one else is having a problem? Also, the task mgr registers a short
instance of FIJI, but then it goes away immediately.

Jacob

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[Richard Fetter]

I had exactly the same problem after my last update of an existing Fiji
installation.  I eventually solved the problem by downloading the most
recent Fiji for Windows (I'm using Win7), copied over the additional
plugins, and am now functional again.  Only issue is the icon is the ImageJ
icon, but I can live with that.

HTH,
Rick

On Mon, Dec 22, 2014 at 7:12 AM, Rebecca Keller <[hidden email]>
wrote:

> Yes, I had already tried both task mgr and restarting, to no avail.​ But I
> guess no one else is having a problem? Also, the task mgr registers a short
> instance of FIJI, but then it goes away immediately.
>
> Jacob
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[Seth Kasowitz]

Jacob,

I saw this happening on a Win7 64-bit machine this Friday. An updated
version of Fiji would put up the logo briefly and disappear. A separate
ImageJ folder and an un-updated copy on another computer both launched
without issue. I have not gotten to look at the specific issue yet, but you
are not the only one affected. I will try to look for a fix today.


Seth

On Mon, Dec 22, 2014 at 7:12 AM, Rebecca Keller <[hidden email]>
wrote:

> Yes, I had already tried both task mgr and restarting, to no avail.​ But I
> guess no one else is having a problem? Also, the task mgr registers a short
> instance of FIJI, but then it goes away immediately.
>
> Jacob
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[John Minter]

Rebecca and Rick,

I had the same experience and had tried Rick's solution. It worked for me
as well. I keep the Fiji Icon hanging around for such occasions...

On Mon, Dec 22, 2014 at 7:32 AM, Richard Fetter <[hidden email]>
wrote:

> I had exactly the same problem after my last update of an existing Fiji
> installation.  I eventually solved the problem by downloading the most
> recent Fiji for Windows (I'm using Win7), copied over the additional
> plugins, and am now functional again.  Only issue is the icon is the ImageJ
> icon, but I can live with that.
>
> HTH,
> Rick
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[Jens Bosse]

same issue here on a Mac. Updated last Friday.

Jens

> On Dec 22, 2014, at 9:33 AM, John Minter <[hidden email]> wrote:
>
> Rebecca and Rick,
>
> I had the same experience and had tried Rick's solution. It worked for me
> as well. I keep the Fiji Icon hanging around for such occasions...
>
> On Mon, Dec 22, 2014 at 7:32 AM, Richard Fetter <[hidden email]>
> wrote:
>
>> I had exactly the same problem after my last update of an existing Fiji
>> installation.  I eventually solved the problem by downloading the most
>> recent Fiji for Windows (I'm using Win7), copied over the additional
>> plugins, and am now functional again.  Only issue is the icon is the ImageJ
>> icon, but I can live with that.
>>
>> HTH,
>> Rick
>>
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[Jan Eglinger]

Dear all,

On 22.12.14 13:12, Rebecca Keller wrote:
> Yes, I had already tried both task mgr and restarting, to no avail.​ But I
> guess no one else is having a problem? Also, the task mgr registers a short
> instance of FIJI, but then it goes away immediately.

To see the cause for this, it might be a good idea to run Fiji from the
command line and look at the output. If you share it on this list,
someone might be able to provide more specific help.

In general, you can try to delete the "update" folder within ./Fiji.app/
and it might also help to delete ij-updater-core-*.jar and
ij-ui-swing-updater-*.jar depending on what state your Fiji installation
was *before* the last update [1]. This will trigger a new download of
the updater upon starting Fiji.

Hope that helps,
Jan


[1]: http://fiji.sc/Fix_non-functional_ImageJ_after_Update

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[ctrueden]

Hi everyone,

> it might be a good idea to run Fiji from the command line and look at
> the output. If you share it on this list, someone might be able to
> provide more specific help.

I second Jan's suggestion. In addition, it would be great if someone could
zip up an affected installation and post it online somewhere, for study.
Having a broken installation would be helpful to understand what went
wrong, and put safeguards in place to prevent it happening again.

Regards,
Curtis

On Mon, Dec 22, 2014 at 9:45 AM, Jan Eglinger <[hidden email]>
wrote:

>
> Dear all,
>
> On 22.12.14 13:12, Rebecca Keller wrote:
>
>> Yes, I had already tried both task mgr and restarting, to no avail.​ But I
>> guess no one else is having a problem? Also, the task mgr registers a
>> short
>> instance of FIJI, but then it goes away immediately.
>>
>
> To see the cause for this, it might be a good idea to run Fiji from the
> command line and look at the output. If you share it on this list, someone
> might be able to provide more specific help.
>
> In general, you can try to delete the "update" folder within ./Fiji.app/
> and it might also help to delete ij-updater-core-*.jar and
> ij-ui-swing-updater-*.jar depending on what state your Fiji installation
> was *before* the last update [1]. This will trigger a new download of the
> updater upon starting Fiji.
>
> Hope that helps,
> Jan
>
>
> [1]: http://fiji.sc/Fix_non-functional_ImageJ_after_Update
>
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[Rebecca Keller]

Here's my bad installation.

https://www.dropbox.com/s/j0xacahjedk2q5z/Fiji.app.zip?dl=0

Jacob



On Mon, Dec 22, 2014 at 10:51 AM, Curtis Rueden <[hidden email]> wrote:

> Hi everyone,
>
> > it might be a good idea to run Fiji from the command line and look at
> > the output. If you share it on this list, someone might be able to
> > provide more specific help.
>
> I second Jan's suggestion. In addition, it would be great if someone could
> zip up an affected installation and post it online somewhere, for study.
> Having a broken installation would be helpful to understand what went
> wrong, and put safeguards in place to prevent it happening again.
>
> Regards,
> Curtis
>
> On Mon, Dec 22, 2014 at 9:45 AM, Jan Eglinger <[hidden email]>
> wrote:
> >
> > Dear all,
> >
> > On 22.12.14 13:12, Rebecca Keller wrote:
> >
> >> Yes, I had already tried both task mgr and restarting, to no avail.​
> But I
> >> guess no one else is having a problem? Also, the task mgr registers a
> >> short
> >> instance of FIJI, but then it goes away immediately.
> >>
> >
> > To see the cause for this, it might be a good idea to run Fiji from the
> > command line and look at the output. If you share it on this list,
> someone
> > might be able to provide more specific help.
> >
> > In general, you can try to delete the "update" folder within ./Fiji.app/
> > and it might also help to delete ij-updater-core-*.jar and
> > ij-ui-swing-updater-*.jar depending on what state your Fiji installation
> > was *before* the last update [1]. This will trigger a new download of the
> > updater upon starting Fiji.
> >
> > Hope that helps,
> > Jan
> >
> >
> > [1]: http://fiji.sc/Fix_non-functional_ImageJ_after_Update
> >
> >
> > --
> > ImageJ mailing list: http://imagej.nih.gov/ij/list.html
> >
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[ctrueden]

Hi Jacob,

> Here's my bad installation.

Thank you very much. I can confirm that there is a bug in the ImageJ
Updater on Windows, which causes it to hose installations. It downloads
only a subset of the updated files. I fear that any Windows users who
update will be stuck with a non-working installation.

I am investigating the best way to fix things, but the best options for
Windows users at the moment are: A) do not update; or B) download a fresh
installation from http://imagej.net/Downloads.

Regards,
Curtis

On Mon, Dec 22, 2014 at 10:20 AM, Rebecca Keller <[hidden email]>
wrote:

>
> Here's my bad installation.
>
> https://www.dropbox.com/s/j0xacahjedk2q5z/Fiji.app.zip?dl=0
>
> Jacob
>
>
>
> On Mon, Dec 22, 2014 at 10:51 AM, Curtis Rueden <[hidden email]> wrote:
>
> > Hi everyone,
> >
> > > it might be a good idea to run Fiji from the command line and look at
> > > the output. If you share it on this list, someone might be able to
> > > provide more specific help.
> >
> > I second Jan's suggestion. In addition, it would be great if someone
> could
> > zip up an affected installation and post it online somewhere, for study.
> > Having a broken installation would be helpful to understand what went
> > wrong, and put safeguards in place to prevent it happening again.
> >
> > Regards,
> > Curtis
> >
> > On Mon, Dec 22, 2014 at 9:45 AM, Jan Eglinger <[hidden email]>
> > wrote:
> > >
> > > Dear all,
> > >
> > > On 22.12.14 13:12, Rebecca Keller wrote:
> > >
> > >> Yes, I had already tried both task mgr and restarting, to no avail.​
> > But I
> > >> guess no one else is having a problem? Also, the task mgr registers a
> > >> short
> > >> instance of FIJI, but then it goes away immediately.
> > >>
> > >
> > > To see the cause for this, it might be a good idea to run Fiji from the
> > > command line and look at the output. If you share it on this list,
> > someone
> > > might be able to provide more specific help.
> > >
> > > In general, you can try to delete the "update" folder within
> ./Fiji.app/
> > > and it might also help to delete ij-updater-core-*.jar and
> > > ij-ui-swing-updater-*.jar depending on what state your Fiji
> installation
> > > was *before* the last update [1]. This will trigger a new download of
> the
> > > updater upon starting Fiji.
> > >
> > > Hope that helps,
> > > Jan
> > >
> > >
> > > [1]: http://fiji.sc/Fix_non-functional_ImageJ_after_Update
> > >
> > >
> > > --
> > > ImageJ mailing list: http://imagej.nih.gov/ij/list.html
> > >
> >
> > --
> > ImageJ mailing list: http://imagej.nih.gov/ij/list.html
> >
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[ctrueden]

Hi everyone,

> I am investigating the best way to fix things, but the best options
> for Windows users at the moment are: A) do not update; or B) download
> a fresh installation from http://imagej.net/Downloads.

I added a workaround on the remote server side which avoids the bug in the
ImageJ Updater. So it should be feasible to update installations on Windows
now. Unfortunately, installations which have already been rendered
non-functional will still not start up. In that case, downloading a new
copy is your best bet.

Regards,
Curtis

On Mon, Dec 22, 2014 at 4:34 PM, Curtis Rueden <[hidden email]> wrote:

>
> Hi Jacob,
>
> > Here's my bad installation.
>
> Thank you very much. I can confirm that there is a bug in the ImageJ
> Updater on Windows, which causes it to hose installations. It downloads
> only a subset of the updated files. I fear that any Windows users who
> update will be stuck with a non-working installation.
>
> I am investigating the best way to fix things, but the best options for
> Windows users at the moment are: A) do not update; or B) download a fresh
> installation from http://imagej.net/Downloads.
>
> Regards,
> Curtis
>
> On Mon, Dec 22, 2014 at 10:20 AM, Rebecca Keller <[hidden email]>
> wrote:
>>
>> Here's my bad installation.
>>
>> https://www.dropbox.com/s/j0xacahjedk2q5z/Fiji.app.zip?dl=0
>>
>> Jacob
>>
>>
>>
>> On Mon, Dec 22, 2014 at 10:51 AM, Curtis Rueden <[hidden email]>
>> wrote:
>>
>> > Hi everyone,
>> >
>> > > it might be a good idea to run Fiji from the command line and look at
>> > > the output. If you share it on this list, someone might be able to
>> > > provide more specific help.
>> >
>> > I second Jan's suggestion. In addition, it would be great if someone
>> could
>> > zip up an affected installation and post it online somewhere, for study.
>> > Having a broken installation would be helpful to understand what went
>> > wrong, and put safeguards in place to prevent it happening again.
>> >
>> > Regards,
>> > Curtis
>> >
>> > On Mon, Dec 22, 2014 at 9:45 AM, Jan Eglinger <[hidden email]>
>> > wrote:
>> > >
>> > > Dear all,
>> > >
>> > > On 22.12.14 13:12, Rebecca Keller wrote:
>> > >
>> > >> Yes, I had already tried both task mgr and restarting, to no avail.​
>> > But I
>> > >> guess no one else is having a problem? Also, the task mgr registers a
>> > >> short
>> > >> instance of FIJI, but then it goes away immediately.
>> > >>
>> > >
>> > > To see the cause for this, it might be a good idea to run Fiji from
>> the
>> > > command line and look at the output. If you share it on this list,
>> > someone
>> > > might be able to provide more specific help.
>> > >
>> > > In general, you can try to delete the "update" folder within
>> ./Fiji.app/
>> > > and it might also help to delete ij-updater-core-*.jar and
>> > > ij-ui-swing-updater-*.jar depending on what state your Fiji
>> installation
>> > > was *before* the last update [1]. This will trigger a new download of
>> the
>> > > updater upon starting Fiji.
>> > >
>> > > Hope that helps,
>> > > Jan
>> > >
>> > >
>> > > [1]: http://fiji.sc/Fix_non-functional_ImageJ_after_Update
>> > >
>> > >
>> > > --
>> > > ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>> > >
>> >
>> > --
>> > ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>> >
>>
>> --
>> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>>
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html