Fiji will not quit

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Fiji will not quit

Knecht, David
I ran into a problem today where Fiji will not quit (Mac OSX Mavericks).  It is not frozen, because it works fine before or after I tell it to quit.  Neither Command-Q nor the File/Quit work.  The only way I have been able to get it to quit is using force-quit. Standard ImageJ and other programs work fine.   Has anyone seen this behavior?  Dave

David Knecht, Ph.D.
Professor and Head of Core Microscopy Facility
Department of Molecular and Cell Biology
U-3125
91 N. Eagleville Rd.
University of Connecticut
Storrs, CT 06269
860-486-2200
860-486-4331 (fax)






--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html
Reply | Threaded
Open this post in threaded view
|

Re: Fiji will not quit

Michael Schell-2
Yes, I have been getting that for a couple of weeks now.  Same OS, etc.  Sometimes when I can’t quit via the Dock, I can still do it via the menu.  Other times, only force-quit works.


On Jan 3, 2014, at 3:52 PM, Knecht, David <[hidden email]> wrote:

> I ran into a problem today where Fiji will not quit (Mac OSX Mavericks).  It is not frozen, because it works fine before or after I tell it to quit.  Neither Command-Q nor the File/Quit work.  The only way I have been able to get it to quit is using force-quit. Standard ImageJ and other programs work fine.   Has anyone seen this behavior?  Dave
>
> David Knecht, Ph.D.
> Professor and Head of Core Microscopy Facility
> Department of Molecular and Cell Biology
> U-3125
> 91 N. Eagleville Rd.
> University of Connecticut
> Storrs, CT 06269
> 860-486-2200
> 860-486-4331 (fax)
>
>
>
>
>
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html
Reply | Threaded
Open this post in threaded view
|

Re: Fiji will not quit

Graeme Ball-2
In reply to this post by Knecht, David
I've notice the same thing recently, and I'm still running OS X 10.7.5.

I just tried to attach some console output, but LISTSERV seemed to reject
this, so here it is on pastebin:-
  http://pastebin.com/YT7wy7jt

Starting Fiji gives the first stack trace, and the lot after 22:16:50 comes
from trying to Quit from the menu.

Graeme




On Fri, Jan 3, 2014 at 8:52 PM, Knecht, David <[hidden email]>wrote:

> I ran into a problem today where Fiji will not quit (Mac OSX Mavericks).
>  It is not frozen, because it works fine before or after I tell it to quit.
>  Neither Command-Q nor the File/Quit work.  The only way I have been able
> to get it to quit is using force-quit. Standard ImageJ and other programs
> work fine.   Has anyone seen this behavior?  Dave
>
> David Knecht, Ph.D.
> Professor and Head of Core Microscopy Facility
> Department of Molecular and Cell Biology
> U-3125
> 91 N. Eagleville Rd.
> University of Connecticut
> Storrs, CT 06269
> 860-486-2200
> 860-486-4331 (fax)
>
>
>
>
>
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html
Reply | Threaded
Open this post in threaded view
|

Re: Fiji will not quit

Knecht, David
In addition,double click and file drag and drop no longer works when dragging to the dock icon.  I can only open by File/Open. Dave

On Jan 3, 2014, at 5:29 PM, Graeme Ball <[hidden email]<mailto:[hidden email]>> wrote:

I've notice the same thing recently, and I'm still running OS X 10.7.5.

I just tried to attach some console output, but LISTSERV seemed to reject
this, so here it is on pastebin:-
 http://pastebin.com/YT7wy7jt

Starting Fiji gives the first stack trace, and the lot after 22:16:50 comes
from trying to Quit from the menu.

Graeme




On Fri, Jan 3, 2014 at 8:52 PM, Knecht, David <[hidden email]<mailto:[hidden email]>>wrote:

I ran into a problem today where Fiji will not quit (Mac OSX Mavericks).
It is not frozen, because it works fine before or after I tell it to quit.
Neither Command-Q nor the File/Quit work.  The only way I have been able
to get it to quit is using force-quit. Standard ImageJ and other programs
work fine.   Has anyone seen this behavior?  Dave

David Knecht, Ph.D.
Professor and Head of Core Microscopy Facility
Department of Molecular and Cell Biology
U-3125
91 N. Eagleville Rd.
University of Connecticut
Storrs, CT 06269
860-486-2200
860-486-4331 (fax)






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


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

David Knecht, Ph.D.
Professor and Head of Core Microscopy Facility
Department of Molecular and Cell Biology
U-3125
91 N. Eagleville Rd.
University of Connecticut
Storrs, CT 06269
860-486-2200
860-486-4331 (fax)






--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html
Reply | Threaded
Open this post in threaded view
|

Re: Fiji will not quit

Niko Ehrenfeuchter
In reply to this post by Knecht, David
Hi all,

On 03.01.2014 21:52, Knecht, David wrote:
> I ran into a problem today where Fiji will not quit (Mac OSX
> Mavericks).  It is not frozen, because it works fine before or after
> I tell it to quit.  Neither Command-Q nor the File/Quit work.  The
> only way I have been able to get it to quit is using force-quit.
> Standard ImageJ and other programs work fine.   Has anyone seen this
> behavior?  Dave

we do experience the same thing here, on Linux (Ubuntu) and Windows 7
(both 64 bit). After running e.g. the Stitcher, Fiji would ignore all
attempts to close it.

Cheers
Niko

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html
Reply | Threaded
Open this post in threaded view
|

Re: Fiji will not quit

dscho
In reply to this post by Knecht, David
Hi David,

On Sat, 4 Jan 2014, Knecht, David wrote:

> On Jan 3, 2014, at 5:29 PM, Graeme Ball <[hidden email]<mailto:[hidden email]>> wrote:
>
> > On Fri, Jan 3, 2014 at 8:52 PM, Knecht, David <[hidden email]<mailto:[hidden email]>>wrote:
> >
> > > I ran into a problem today where Fiji will not quit (Mac OSX
> > > Mavericks).  It is not frozen, because it works fine before or after
> > > I tell it to quit.  Neither Command-Q nor the File/Quit work.  The
> > > only way I have been able to get it to quit is using force-quit.
> > > Standard ImageJ and other programs work fine.   Has anyone seen this
> > > behavior?  Dave I've notice the same thing recently, and I'm still
> > > running OS X 10.7.5.
> >
> > I just tried to attach some console output, but LISTSERV seemed to
> > reject this, so here it is on pastebin:- http://pastebin.com/YT7wy7jt
> >
> > Starting Fiji gives the first stack trace, and the lot after 22:16:50
> > comes from trying to Quit from the menu.
>
> In addition,double click and file drag and drop no longer works when
> dragging to the dock icon.  I can only open by File/Open. Dave

Please note that this top-posting business makes it pretty inconvenient to
reconstruct the conversation after a couple of days, in particular if one
has to keep track of multiple conversations (as the people you ask for
help invariably do).

Next time, you might want to spend a little more time to quote the mail
you respond to properly so that the possibly thousands of readers of your
mail *save* time.

With the outstanding help of Mark Hiner, I believe I addressed this issue
and uploaded a new ij-core.jar that I uploaded to the update site.

Please test and report back,
Johannes

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html
Reply | Threaded
Open this post in threaded view
|

Re: Fiji will not quit

Graeme Ball-2
Looks good: quits fine, no errors (OS X 10.7.5, java 6). Thanks Johannes &
Mark :-)

Graeme

PS. how would you prefer this sort of problem to be reported? Help->Report
a Bug?


On Mon, Jan 6, 2014 at 6:03 PM, Johannes Schindelin <
[hidden email]> wrote:

> Hi David,
>
> On Sat, 4 Jan 2014, Knecht, David wrote:
>
> > On Jan 3, 2014, at 5:29 PM, Graeme Ball <[hidden email]
> <mailto:[hidden email]>> wrote:
> >
> > > On Fri, Jan 3, 2014 at 8:52 PM, Knecht, David <[hidden email]
> <mailto:[hidden email]>>wrote:
> > >
> > > > I ran into a problem today where Fiji will not quit (Mac OSX
> > > > Mavericks).  It is not frozen, because it works fine before or after
> > > > I tell it to quit.  Neither Command-Q nor the File/Quit work.  The
> > > > only way I have been able to get it to quit is using force-quit.
> > > > Standard ImageJ and other programs work fine.   Has anyone seen this
> > > > behavior?  Dave I've notice the same thing recently, and I'm still
> > > > running OS X 10.7.5.
> > >
> > > I just tried to attach some console output, but LISTSERV seemed to
> > > reject this, so here it is on pastebin:- http://pastebin.com/YT7wy7jt
> > >
> > > Starting Fiji gives the first stack trace, and the lot after 22:16:50
> > > comes from trying to Quit from the menu.
> >
> > In addition,double click and file drag and drop no longer works when
> > dragging to the dock icon.  I can only open by File/Open. Dave
>
> Please note that this top-posting business makes it pretty inconvenient to
> reconstruct the conversation after a couple of days, in particular if one
> has to keep track of multiple conversations (as the people you ask for
> help invariably do).
>
> Next time, you might want to spend a little more time to quote the mail
> you respond to properly so that the possibly thousands of readers of your
> mail *save* time.
>
> With the outstanding help of Mark Hiner, I believe I addressed this issue
> and uploaded a new ij-core.jar that I uploaded to the update site.
>
> Please test and report back,
> Johannes
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html
Reply | Threaded
Open this post in threaded view
|

Re: Fiji will not quit

dscho
Hi Graeme,

On Mon, 6 Jan 2014, Graeme Ball wrote:

> Looks good: quits fine, no errors (OS X 10.7.5, java 6).

Thanks for the feedback. For context: the test refers to the issue where
an update of ImageJ2 broke quitting Fiji, reported by David Knecht.

> Thanks Johannes & Mark :-)

I Cc:ed him so he won't miss it.

> PS. how would you prefer this sort of problem to be reported?
> Help->Report a Bug?

Help>Report a Bug provides information that is easy to forget to provide,
so it is a very good way to report bugs.

But an email is also fine. The important part is to understand that it is
much easier to report a bug than to fix it. So whatever you can do to make
it easier on the poor guy stuck with the task may be a good idea to do
(provide context, if possible provide a macro to reproduce the issue
easily, when responding to mails, quote them properly and only the parts
you are responding to, so that somebody like myself who has to juggle a
couple of email conversations in parallel does not have to spend more time
to figure out the context than it takes to craft the reply, things like
that).

Ciao,
Johannes

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