Re: [GNC] Repeatable Mac crash

[Christoph R]

Hi John,

reading this I instantly created an Automator Shell Script which opens with 
“—nofile” when double clicked and with the file when I drop a file on it. After 
changing the file information too I can now double click on a .gnucash file to 
open it.

What’s the reason that we cannot implement this - or something similar - in the 
standard package?

Cheers,
Christoph

> Am 01.10.2018 um 16:17 schrieb John Ralls  >:
> 
> 
> 
>> On Oct 1, 2018, at 4:02 AM, Robert Kesterson > > wrote:
>> 
>> On 30 Sep 2018, at 9:06, John Ralls wrote:
>> 
 … >
>>> Since you’re running two instances of GnuCash it’s likely that the trace 
>>> file will be garbled, so if you could use the following from the command 
>>> line instead:
>>> /Applications/Gnucash.app/Contents/MacOS/Gnucash --logto=~/gnucash.trace
>>> That will create a separate trace file in your user directory that you can 
>>> also attach to the bug report. You could even add the file path for the 
>>> file you really want to open to the end of that and save yourself the 
>>> “can’t get the lock” drill.
>> 
>> It appears that this works around the issue.  I did as you suggested and 
>> launched with the binary rather than the app package, and I gave it the 
>> alternate log location and specified the path to open on the command line. 
>> Since this is a pretty long command line that I don’t want to type often, I 
>> saved it as an executable shell script, one for each set of books.  Now when 
>> I run them both, they both run.  No crash. Should I still run them the old 
>> way and file a bug?  The workaround seems reliable, and I’m happy…
> 
> I don’t know why you’d want to run the way that causes a crash, but you 
> should file a bug.
> 
> Regards,
> John Ralls
> 
> 
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org 
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user 
> 
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists 
>  for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.




Gruß,
Christoph

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Repeatable Mac crash

[John Ralls]

> On Oct 1, 2018, at 4:02 AM, Robert Kesterson  wrote:
> 
> On 30 Sep 2018, at 9:06, John Ralls wrote:
> 
>>> … >
>> Since you’re running two instances of GnuCash it’s likely that the trace 
>> file will be garbled, so if you could use the following from the command 
>> line instead:
>>  /Applications/Gnucash.app/Contents/MacOS/Gnucash --logto=~/gnucash.trace
>> That will create a separate trace file in your user directory that you can 
>> also attach to the bug report. You could even add the file path for the file 
>> you really want to open to the end of that and save yourself the “can’t get 
>> the lock” drill.
> 
> It appears that this works around the issue.  I did as you suggested and 
> launched with the binary rather than the app package, and I gave it the 
> alternate log location and specified the path to open on the command line.   
> Since this is a pretty long command line that I don’t want to type often, I 
> saved it as an executable shell script, one for each set of books.  Now when 
> I run them both, they both run.  No crash. Should I still run them the old 
> way and file a bug?  The workaround seems reliable, and I’m happy…

I don’t know why you’d want to run the way that causes a crash, but you should 
file a bug.

Regards,
John Ralls


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Repeatable Mac crash

[Robert Kesterson]

On 30 Sep 2018, at 9:06, John Ralls wrote:


… >
Since you’re running two instances of GnuCash it’s likely that the 
trace file will be garbled, so if you could use the following from the 
command line instead:
  /Applications/Gnucash.app/Contents/MacOS/Gnucash 
--logto=~/gnucash.trace
That will create a separate trace file in your user directory that you 
can also attach to the bug report. You could even add the file path 
for the file you really want to open to the end of that and save 
yourself the “can’t get the lock” drill.


It appears that this works around the issue.  I did as you suggested and 
launched with the binary rather than the app package, and I gave it the 
alternate log location and specified the path to open on the command 
line.   Since this is a pretty long command line that I don’t want to 
type often, I saved it as an executable shell script, one for each set 
of books.  Now when I run them both, they both run.  No crash. Should I 
still run them the old way and file a bug?  The workaround seems 
reliable, and I’m happy…

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Repeatable Mac crash

[John Ralls]

> On Sep 30, 2018, at 10:14 AM, Stephen M. Butler  wrote:
> 
> On 09/30/2018 10:07 AM, Michael or Penny Novack wrote:
>> 
 On Sep 29, 2018, at 4:30 AM, Robert Kesterson 
 wrote:
>> 
 
 When I open Gnucash, it opens the last file I had open, which is
 great.  Then I start the second instance from a terminal with “open
 -n /Applications/GnuCash.app” and it starts up.  Since the most
 recent file is already open, it will complain that it can’t get the
 lock and ask what I want to do.  Since there isn’t an “open a
 different file” option ...
>> 
>> But there IS a way to open gnucash for another file. Or rather a way
>> to start gnucash without it opening a file, thus allowing you to
>> specify what file you want to open. The -nofile option << I don't know
>> exactly how to specify that for a mac >>
>> 
>> I am always opening gnucash that way since keeping four sets of books
>> and the last opened is usually not the one I want to open.
>> 
>> Michael
>> 
> 
> I found it easier to just navigate to the file with the file explorer
> (at least on Linux) and double click on the file.  GnuCash then launches
> and opens that file.

That doesn't work on Macs.

Regards,
John Ralls


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Repeatable Mac crash

[Stephen M. Butler]

On 09/30/2018 10:07 AM, Michael or Penny Novack wrote:
>
>>> On Sep 29, 2018, at 4:30 AM, Robert Kesterson 
>>> wrote:
>
>>>
>>> When I open Gnucash, it opens the last file I had open, which is
>>> great.  Then I start the second instance from a terminal with “open
>>> -n /Applications/GnuCash.app” and it starts up.  Since the most
>>> recent file is already open, it will complain that it can’t get the
>>> lock and ask what I want to do.  Since there isn’t an “open a
>>> different file” option ...
>
> But there IS a way to open gnucash for another file. Or rather a way
> to start gnucash without it opening a file, thus allowing you to
> specify what file you want to open. The -nofile option << I don't know
> exactly how to specify that for a mac >>
>
> I am always opening gnucash that way since keeping four sets of books
> and the last opened is usually not the one I want to open.
>
> Michael
>

I found it easier to just navigate to the file with the file explorer
(at least on Linux) and double click on the file.  GnuCash then launches
and opens that file.
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.


-- 
Stephen M Butler, PMP, PSM
stephen.m.butle...@gmail.com
kg...@arrl.net
253-350-0166
---
GnuPG Fingerprint:  8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Repeatable Mac crash

[Michael or Penny Novack]

On Sep 29, 2018, at 4:30 AM, Robert Kesterson  wrote:




When I open Gnucash, it opens the last file I had open, which is great.  Then I 
start the second instance from a terminal with “open -n 
/Applications/GnuCash.app” and it starts up.  Since the most recent file is 
already open, it will complain that it can’t get the lock and ask what I want 
to do.  Since there isn’t an “open a different file” option ...


But there IS a way to open gnucash for another file. Or rather a way to 
start gnucash without it opening a file, thus allowing you to specify 
what file you want to open. The -nofile option << I don't know exactly 
how to specify that for a mac >>


I am always opening gnucash that way since keeping four sets of books 
and the last opened is usually not the one I want to open.


Michael

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Repeatable Mac crash

[John Ralls]

> On Sep 29, 2018, at 4:30 AM, Robert Kesterson  wrote:
> 
> I’ve been using GnuCash forever, running the 2.x series up until a couple of 
> months ago on Mac High Sierra.  I routinely have two instances of Gnucash 
> running — one personal and one business.  A couple of months ago I updated to 
> GnuCash 3.2.  Since then I have a 100% repeatable crash scenario that I 
> wonder if anyone knows how to solve.
> 
> When I open Gnucash, it opens the last file I had open, which is great.  Then 
> I start the second instance from a terminal with “open -n 
> /Applications/GnuCash.app” and it starts up.  Since the most recent file is 
> already open, it will complain that it can’t get the lock and ask what I want 
> to do.  Since there isn’t an “open a different file” option, I hit the button 
> to create a new file.  Gnucash opens.  Then I pull down the recent files menu 
> and select my other file (for example, if personal is open, I select the 
> business file).  Gnucash will ask if I want to save the empty set of accounts 
> it created a moment ago.  I say no, and it reads my second file.
> 
> The moment the second file finishes reading (the progress bar moves all the 
> way across), Gnucash crashes.  This is 100% repeatable — happens this way 
> every single time, no matter which file I have open first or second.
> 
> I can then run the second instance again, and the other file will have now 
> moved to the position of most recent file opened, and it will open 
> automatically.  It will complain that it is locked (since it crashed without 
> removing it), and I tell it to ignore it and it will run fine.
> 
> Again, this is 100% repeatable.  If there is a known fix, I’d love to hear 
> it.  If not, what can I do to help track this down so it can get fixed?

Please open a bug report and attach (don’t paste it into a comment!) the crash 
report you’ll find by opening Applications:Utilities:Console and selecting User 
Reports on the sidebar. You can control-click on a report and select “show in 
finder” to get its location.

Since you’re running two instances of GnuCash it’s likely that the trace file 
will be garbled, so if you could use the following from the command line 
instead:
  /Applications/Gnucash.app/Contents/MacOS/Gnucash --logto=~/gnucash.trace
That will create a separate trace file in your user directory that you can also 
attach to the bug report. You could even add the file path for the file you 
really want to open to the end of that and save yourself the “can’t get the 
lock” drill.

Regards,
John Ralls


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

[GNC] Repeatable Mac crash

[Robert Kesterson]

I’ve been using GnuCash forever, running the 2.x series up until a 
couple of months ago on Mac High Sierra.  I routinely have two instances 
of Gnucash running — one personal and one business.  A couple of 
months ago I updated to GnuCash 3.2.  Since then I have a 100% 
repeatable crash scenario that I wonder if anyone knows how to solve.


When I open Gnucash, it opens the last file I had open, which is great.  
Then I start the second instance from a terminal with “open -n 
/Applications/GnuCash.app” and it starts up.  Since the most recent 
file is already open, it will complain that it can’t get the lock and 
ask what I want to do.  Since there isn’t an “open a different 
file” option, I hit the button to create a new file.  Gnucash opens.  
Then I pull down the recent files menu and select my other file (for 
example, if personal is open, I select the business file).  Gnucash will 
ask if I want to save the empty set of accounts it created a moment ago. 
 I say no, and it reads my second file.


The moment the second file finishes reading (the progress bar moves all 
the way across), Gnucash crashes.  This is 100% repeatable — happens 
this way every single time, no matter which file I have open first or 
second.


I can then run the second instance again, and the other file will have 
now moved to the position of most recent file opened, and it will open 
automatically.  It will complain that it is locked (since it crashed 
without removing it), and I tell it to ignore it and it will run fine.


Again, this is 100% repeatable.  If there is a known fix, I’d love to 
hear it.  If not, what can I do to help track this down so it can get 
fixed?

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.