[GNC] Gnucash Version: 3.3 Build ID: 3.3+ (2018-09-29)

[GNC] Gnucash Version: 3.3 Build ID: 3.3+ (2018-09-29)

Hi,

I have recently upgraded my Gnucash to Version: 3.3 Build ID: 3.3+ (2018-09-29) on my Mac running macOS High Sierra version 10.13.6. When I open my file and while updating my file, I often receive a message:

Once this happens, I will choose the “open anyway” option, and once opened, I close it and reopen. This is a work around, however, I am continually saving my work, as it will crash while updating.

Re: [GNC] Gnucash Version: 3.3 Build ID: 3.3+ (2018-09-29)

Sorry to hear you're having crash problems. (I just had one myself on 3.4 reported in another thread)

The image didn’t come through, but from your text I can tell you’re getting the file-lock warning. You are getting this warning because GnuCash sets a file-lock so you can’t unintentionally edit the file simulatenously with someone else. (not supported at this time)

When GnuCash exits normally, it deletes the lock-file. But because it crashed, the lock-file is still there.

So since you know this was a crash, you can simply choose to Open Anyway.

However, if you are repeatedly getting crashes, you should report them here so someone can help. (I don’t think clicking the button on the crash report window to “Send to Apple” does any good because it isn’t an Apple application)

If you can manage to *make* it crash intentionally following the same steps with regularity, that is even better. (easier to figure out the actual cause so it can get fixed faster)

Regards,
Adrien

> On Jan 24, 2019, at 5:29 PM, DOLORES HORTON via gnucash-user <[hidden email]> wrote:
>
> Hi,
>
> I have recently upgraded my Gnucash to Version: 3.3 Build ID: 3.3+ (2018-09-29) on my Mac running macOS High Sierra version 10.13.6. When I open my file and while updating my file, I often receive a message:
>
>
>
>
> Once this happens, I will choose the “open anyway” option, and once opened, I close it and reopen. This is a work around, however, I am continually saving my work, as it will crash while updating.
>
> Your advice here please.
>
> Many thanks,
> Dolores

Re: [GNC] Gnucash Version: 3.3 Build ID: 3.3+ (2018-09-29)

> On Jan 25, 2019, at 11:14 PM, Adrien Monteleone <[hidden email]> wrote:
>
> However, if you are repeatedly getting crashes, you should report them here so someone can help. (I don’t think clicking the button on the crash report window to “Send to Apple” does any good because it isn’t an Apple application)

It doesn't, but pasting the top part into a bug report or an email to here (as you did on your crash email earlier) is immensely helpful to me, much more so than screen shots of error messages.

Those crash reports are available in /Applications/Utilities/Console by selecting "User Reports" in the sidebar.

What I need from it is the header starting at "Date/Time" through the end of the stack trace labelled "Thread [x] Crashed"; x is almost always 0.

Re: [GNC] Gnucash Version: 3.3 Build ID: 3.3+ (2018-09-29)

For posterity...

Then you don’t need the section concerning Binary Images or System Profile?

Do you need the entire thread list, or just the beginning of the stack? I see there is also a section immediately after the full thread list showing “Thread x Crashed with Thread State:”. Need that too?

If this isn’t already on the wiki, I’d like to document it there.

Regards,
Adrien

> On Jan 26, 2019, at 10:31 AM, John Ralls <[hidden email]> wrote:
>
>
>
>> On Jan 25, 2019, at 11:14 PM, Adrien Monteleone <[hidden email]> wrote:
>>
>> However, if you are repeatedly getting crashes, you should report them here so someone can help. (I don’t think clicking the button on the crash report window to “Send to Apple” does any good because it isn’t an Apple application)
>
> It doesn't, but pasting the top part into a bug report or an email to here (as you did on your crash email earlier) is immensely helpful to me, much more so than screen shots of error messages.
>
> Those crash reports are available in /Applications/Utilities/Console by selecting "User Reports" in the sidebar.
>
> What I need from it is the header starting at "Date/Time" through the end of the stack trace labelled "Thread [x] Crashed"; x is almost always 0.
>
> Regards,
> John Ralls
>
>

Re: [GNC] Gnucash Version: 3.3 Build ID: 3.3+ (2018-09-29)

As a side note, it would be very nice of Apple if these crash reports could instead or also be sent to the app developer. Not sure how that would be accommodated for however or if they’d allow developers to specify this in the packaging itself. But I can see it certainly possible for anything in the AppStore. (I’m well aware GnuCash isn’t listed there though.)

Regards,
Adrien

> On Jan 26, 2019, at 10:41 AM, Adrien Monteleone <[hidden email]> wrote:
>
> For posterity...
>
> Then you don’t need the section concerning Binary Images or System Profile?
>
> Do you need the entire thread list, or just the beginning of the stack? I see there is also a section immediately after the full thread list showing “Thread x Crashed with Thread State:”. Need that too?
>
> If this isn’t already on the wiki, I’d like to document it there.
>
> Regards,
> Adrien
>
>> On Jan 26, 2019, at 10:31 AM, John Ralls <[hidden email]> wrote:
>>
>>
>>
>>> On Jan 25, 2019, at 11:14 PM, Adrien Monteleone <[hidden email]> wrote:
>>>
>>> However, if you are repeatedly getting crashes, you should report them here so someone can help. (I don’t think clicking the button on the crash report window to “Send to Apple” does any good because it isn’t an Apple application)
>>
>> It doesn't, but pasting the top part into a bug report or an email to here (as you did on your crash email earlier) is immensely helpful to me, much more so than screen shots of error messages.
>>
>> Those crash reports are available in /Applications/Utilities/Console by selecting "User Reports" in the sidebar.
>>
>> What I need from it is the header starting at "Date/Time" through the end of the stack trace labelled "Thread [x] Crashed"; x is almost always 0.
>>
>> Regards,
>> John Ralls
>>
>>
>

Re: [GNC] Gnucash Version: 3.3 Build ID: 3.3+ (2018-09-29)

Sorry, one more question for the wiki documentation:

Is it preferred to post crash reports to -user, -dev, or attach to a bug?

Regards,
Adrien

> On Jan 26, 2019, at 10:44 AM, Adrien Monteleone <[hidden email]> wrote:
>
> As a side note, it would be very nice of Apple if these crash reports could instead or also be sent to the app developer. Not sure how that would be accommodated for however or if they’d allow developers to specify this in the packaging itself. But I can see it certainly possible for anything in the AppStore. (I’m well aware GnuCash isn’t listed there though.)
>
> Regards,
> Adrien
>
>> On Jan 26, 2019, at 10:41 AM, Adrien Monteleone <[hidden email]> wrote:
>>
>> For posterity...
>>
>> Then you don’t need the section concerning Binary Images or System Profile?
>>
>> Do you need the entire thread list, or just the beginning of the stack? I see there is also a section immediately after the full thread list showing “Thread x Crashed with Thread State:”. Need that too?
>>
>> If this isn’t already on the wiki, I’d like to document it there.
>>
>> Regards,
>> Adrien
>>
>>> On Jan 26, 2019, at 10:31 AM, John Ralls <[hidden email]> wrote:
>>>
>>>
>>>
>>>> On Jan 25, 2019, at 11:14 PM, Adrien Monteleone <[hidden email]> wrote:
>>>>
>>>> However, if you are repeatedly getting crashes, you should report them here so someone can help. (I don’t think clicking the button on the crash report window to “Send to Apple” does any good because it isn’t an Apple application)
>>>
>>> It doesn't, but pasting the top part into a bug report or an email to here (as you did on your crash email earlier) is immensely helpful to me, much more so than screen shots of error messages.
>>>
>>> Those crash reports are available in /Applications/Utilities/Console by selecting "User Reports" in the sidebar.
>>>
>>> What I need from it is the header starting at "Date/Time" through the end of the stack trace labelled "Thread [x] Crashed"; x is almost always 0.
>>>
>>> Regards,
>>> John Ralls
>>>
>>>
>>
>

Re: [GNC] Gnucash Version: 3.3 Build ID: 3.3+ (2018-09-29)

As long as it's GnuCash.app from our download sites I already know what are the binary images. The only system information that's useful is the MacOS version, and that's up top.

Crashes are bugs and it's a lot easier to track them--including reporting on them in release notes--if they're in bugzilla. Once can either paste the useful part of the crash report into the bug description (that actually helps bugzilla detect duplicates, it knows how to compare stack traces), but that requires some knowledge on the user's part to understand what's the useful part. I usually tell users to go to Console, find the crash report, control-click on it and select "show in Finder". That makes it easy for them to navigate to it from bugzilla's "choose file" button.

Regards,
John Ralls

> On Jan 26, 2019, at 8:41 AM, Adrien Monteleone <[hidden email]> wrote:
>
> For posterity...
>
> Then you don’t need the section concerning Binary Images or System Profile?
>
> Do you need the entire thread list, or just the beginning of the stack? I see there is also a section immediately after the full thread list showing “Thread x Crashed with Thread State:”. Need that too?
>
> If this isn’t already on the wiki, I’d like to document it there.
>
> Regards,
> Adrien
>
>> On Jan 26, 2019, at 10:31 AM, John Ralls <[hidden email]> wrote:
>>
>>
>>
>>> On Jan 25, 2019, at 11:14 PM, Adrien Monteleone <[hidden email]> wrote:
>>>
>>> However, if you are repeatedly getting crashes, you should report them here so someone can help. (I don’t think clicking the button on the crash report window to “Send to Apple” does any good because it isn’t an Apple application)
>>
>> It doesn't, but pasting the top part into a bug report or an email to here (as you did on your crash email earlier) is immensely helpful to me, much more so than screen shots of error messages.
>>
>> Those crash reports are available in /Applications/Utilities/Console by selecting "User Reports" in the sidebar.
>>
>> What I need from it is the header starting at "Date/Time" through the end of the stack trace labelled "Thread [x] Crashed"; x is almost always 0.
>>
>> Regards,
>> John Ralls
>>
>>
>
>
> _______________________________________________
> gnucash-user mailing list
> [hidden email]> 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] Gnucash Version: 3.3 Build ID: 3.3+ (2018-09-29)

Thanks! I think that covers everything.

Regards,
Adrien

> On Jan 26, 2019, at 12:15 PM, John Ralls <[hidden email]> wrote:
>
> As long as it's GnuCash.app from our download sites I already know what are the binary images. The only system information that's useful is the MacOS version, and that's up top.
>
> Crashes are bugs and it's a lot easier to track them--including reporting on them in release notes--if they're in bugzilla. Once can either paste the useful part of the crash report into the bug description (that actually helps bugzilla detect duplicates, it knows how to compare stack traces), but that requires some knowledge on the user's part to understand what's the useful part. I usually tell users to go to Console, find the crash report, control-click on it and select "show in Finder". That makes it easy for them to navigate to it from bugzilla's "choose file" button.
>
> Regards,
> John Ralls
>
>> On Jan 26, 2019, at 8:41 AM, Adrien Monteleone <[hidden email]> wrote:
>>
>> For posterity...
>>
>> Then you don’t need the section concerning Binary Images or System Profile?
>>
>> Do you need the entire thread list, or just the beginning of the stack? I see there is also a section immediately after the full thread list showing “Thread x Crashed with Thread State:”. Need that too?
>>
>> If this isn’t already on the wiki, I’d like to document it there.
>>
>> Regards,
>> Adrien
>>
>>> On Jan 26, 2019, at 10:31 AM, John Ralls <[hidden email]> wrote:
>>>
>>>
>>>
>>>> On Jan 25, 2019, at 11:14 PM, Adrien Monteleone <[hidden email]> wrote:
>>>>
>>>> However, if you are repeatedly getting crashes, you should report them here so someone can help. (I don’t think clicking the button on the crash report window to “Send to Apple” does any good because it isn’t an Apple application)
>>>
>>> It doesn't, but pasting the top part into a bug report or an email to here (as you did on your crash email earlier) is immensely helpful to me, much more so than screen shots of error messages.
>>>
>>> Those crash reports are available in /Applications/Utilities/Console by selecting "User Reports" in the sidebar.
>>>
>>> What I need from it is the header starting at "Date/Time" through the end of the stack trace labelled "Thread [x] Crashed"; x is almost always 0.
>>>
>>> Regards,
>>> John Ralls
>>>
>>>
>>
>>
>> _______________________________________________
>> gnucash-user mailing list
>> [hidden email]>> 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.
>
>

This is a public mailing list of users and volunteers where anyone may be able to help.

First and foremost, keeping the discussion public means others can offer assistance, and others can benefit from the discussion. (now or in the future)

I’m just a user like you. I can’t promise any special help, though I’m glad to do so where I can.

Specifically to your current issue, I don’t print checks. I’ve never used that facility of GnuCash, and I don’t currently have a working printer so I can’t even test any possible solutions for you.

I couldn’t be of further assistance with any specificity, but I can offer a few suggestions:

Exactly, what do you mean by “it kicks me out”? Does GnuCash crash? Does it just go away, or is there an error message or crash report on screen?

Have you tested printing reports? Do you get the same result?

Do you have a ‘virtual printer’ such as PDF or XPS installed? (most Windows systems have a virtual XPS printer installed by default, and you can easily add a free PDF printer)

Using a virtual printer, do you still get a crash? Can you use the ‘print to file’ option?

The reason I ask these questions is to narrow down the trigger to the problem.

If some things can print in GnuCash, but not others, or if successful using a virtual printer rather than an actual physical printer, then this can help narrow down where the problem is occurring.

While I wouldn’t be able to help you beyond that, someone else reading this thread might have enough info to point you in the right direction.

Regards,
Adrien

> On Jan 26, 2019, at 1:03 PM, Lester and Joanna <[hidden email]> wrote:
>
> Hi Adrian,
>
> Please forgive me for contacting you. I am a newbie with Gnucash. I have been using Quicken for 12 years but would now like to use Gnucash if I can make it work for me. I am using Windows 10 with Gnucash 3.4. I have set up an account but when I try to print a check (with Print checks) all goes well through check set up, and to the printer (showing the printer is ready) but when I push print it kicks me out of Gnucash. Also, it kicks me out of Gnucash when I try to print an “Account Summary” using Ctrl-Print. I have two printers. An HP Lazer Jet 477, and a Brother MFC 795 CW. What am I doing wrong?
>
> I have tried printing parts of the Gnucash tutorial with both printers and they Print fine.
>
> Lester
>

Re: [GNC] Printer Problems

> On Jan 26, 2019, at 10:59 AM, Lester and Joanna <[hidden email]> wrote:
>
> Hi John,
>
> Please forgive me for contacting you. I am a newbie with Gnucash. I have been using Quicken for 12 years but would now like to use Gnucash if I can make it work for me. I am using Windows 10 with Gnucash 3.4. I have set up an account but when I try to print a check (with Print checks) all goes well through check set up, and to the printer (showing the printer is ready) but when I push print it kicks me out of Gnucash. Also, it kicks me out of Gnucash when I try to print an “Account Summary” using Ctrl-Print. I have two printers. An HP Lazer Jet 477, and a Brother MFC 795 CW. What am I doing wrong?
>
> I have tried printing parts of the Gnucash tutorial with both printers and they Print fine.
>

Lester,

No forgiveness. Use the mailing list. After all, I'm probably the last person you want to ask about using Windows, I'm a Mac person.

Re: [GNC] Printer Problems

Hmm...

A nearly identical message was posted by that address an hour later to the list, then about an hour after that, I get one sent only to me identical this one below.

Regards,
Adrien

> On Jan 27, 2019, at 12:10 AM, John Ralls <[hidden email]> wrote:
>
>
>
>> On Jan 26, 2019, at 10:59 AM, Lester and Joanna <[hidden email]> wrote:
>>
>> Hi John,
>>
>> Please forgive me for contacting you. I am a newbie with Gnucash. I have been using Quicken for 12 years but would now like to use Gnucash if I can make it work for me. I am using Windows 10 with Gnucash 3.4. I have set up an account but when I try to print a check (with Print checks) all goes well through check set up, and to the printer (showing the printer is ready) but when I push print it kicks me out of Gnucash. Also, it kicks me out of Gnucash when I try to print an “Account Summary” using Ctrl-Print. I have two printers. An HP Lazer Jet 477, and a Brother MFC 795 CW. What am I doing wrong?
>>
>> I have tried printing parts of the Gnucash tutorial with both printers and they Print fine.
>>
>
> Lester,
>
> No forgiveness. Use the mailing list. After all, I'm probably the last person you want to ask about using Windows, I'm a Mac person.
>
> Regards,
> John Ralls
>
> _______________________________________________
> gnucash-user mailing list
> [hidden email]> 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] Printer Problems

>
> Hmm...
>
> A nearly identical message was posted by that address an hour later to the list, then about an hour after that, I get one sent only to me identical this one below.
>
>
> Regards,
> Adrien
>
> > On Jan 27, 2019, at 12:10 AM, John Ralls <[hidden email]> wrote:
> >
> >
> >
> >> On Jan 26, 2019, at 10:59 AM, Lester and Joanna <[hidden email]> wrote:
> >>
> >> Hi John,
> >>
> >> Please forgive me for contacting you. I am a newbie with Gnucash. I have been using Quicken for 12 years but would now like to use Gnucash if I can make it work for me. I am using Windows 10 with Gnucash 3.4. I have set up an account but when I try to print a check (with Print checks) all goes well through check set up, and to the printer (showing the printer is ready) but when I push print it kicks me out of Gnucash. Also, it kicks me out of Gnucash when I try to print an “Account Summary” using Ctrl-Print. I have two printers. An HP Lazer Jet 477, and a Brother MFC 795 CW. What am I doing wrong?
> >>
> >> I have tried printing parts of the Gnucash tutorial with both printers and they Print fine.
> >>
> >
> > Lester,
> >
> > No forgiveness. Use the mailing list. After all, I'm probably the last person you want to ask about using Windows, I'm a Mac person.
> >
> > Regards,
> > John Ralls
> >
> > _______________________________________________
> > gnucash-user mailing list
> > [hidden email]> > 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.
>
>
> _______________________________________________
> gnucash-user mailing list
> [hidden email]> 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] Printer Problems

Regarding your underlying question, GnuCash has been playing catch-up with
printer support in Windows for years. Releases in the 2.6 series sometimes
had issues in Windows 7.

I am still using Windows 7 on one of my computers but I prefer to run
GnuCash on one of my Linux machines.

I would suggest either setting up a virtual computer with a recent Linux
version such as Ubuntu 16.04 or 18.04, or acquiring an older machine from a
computer recycler and putting Linux on it for GnuCash as well as other
basic compuer needs.

> And me, someone who doesn't understand how support mailing lists are
> supposed to work I think.
>
> Coin
>
> On Sun, 27 Jan 2019 at 06:58, Adrien Monteleone
> <[hidden email]> wrote:
> >
> > Hmm...
> >
> > A nearly identical message was posted by that address an hour later to
> the list, then about an hour after that, I get one sent only to me
> identical this one below.
> >
> >
> > Regards,
> > Adrien
> >
> > > On Jan 27, 2019, at 12:10 AM, John Ralls <[hidden email]> wrote:
> > >
> > >
> > >
> > >> On Jan 26, 2019, at 10:59 AM, Lester and Joanna <[hidden email]>
> wrote:
> > >>
> > >> Hi John,
> > >>
> > >> Please forgive me for contacting you. I am a newbie with Gnucash. I
> have been using Quicken for 12 years but would now like to use Gnucash if I
> can make it work for me. I am using Windows 10 with Gnucash 3.4. I have
> set up an account but when I try to print a check (with Print checks) all
> goes well through check set up, and to the printer (showing the printer is
> ready) but when I push print it kicks me out of Gnucash. Also, it kicks
> me out of Gnucash when I try to print an “Account Summary” using
> Ctrl-Print. I have two printers. An HP Lazer Jet 477, and a Brother MFC
> 795 CW. What am I doing wrong?
> > >>
> > >> I have tried printing parts of the Gnucash tutorial with both
> printers and they Print fine.
> > >>
> > >
> > > Lester,
> > >
> > > No forgiveness. Use the mailing list. After all, I'm probably the last
> person you want to ask about using Windows, I'm a Mac person.
> > >
> > > Regards,
> > > John Ralls
> > >
> > > _______________________________________________
> > > gnucash-user mailing list
> > > [hidden email]> > > 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.
> >
> >
> > _______________________________________________
> > gnucash-user mailing list
> > [hidden email]> > 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.
> _______________________________________________
> gnucash-user mailing list
> [hidden email]> 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] Printer Problems

On 2019-01-27 06:45, David Carlson wrote:
> ....
>
> I would suggest either setting up a virtual computer with a recent Linux
> version such as Ubuntu 16.04 or 18.04, or acquiring an older machine from a
> computer recycler and putting Linux on it for GnuCash as well as other
> basic compu[t]er needs.
>
>
> David C

I don't know if this will help anyone, but if anyone is running Windows
10 x64, there is a new feature addition to Windows 10 called "Windows
Subsystem for Linux" ("WSL") that you can enable, & then install (free)
Linux distributions from the Microsoft Store:
https://docs.microsoft.com/en-us/windows/wsl/install-win10

The install is absolutely trivial. Ubuntu 16.04 & 18.04 distributions
are available, but I've installed Debian, & run some fairly complex bash
scripts without a problem.

All that having been said, I have no idea if WSL supports printing. I
doubt it, but I thought I'd throw this out as a possible alternative to
running a VM. WSL is much more "lightweight" than a VM, but takes a LOT
less resources.

Re: [GNC] Printer Problems

My understanding is that the new preferred method if you want a GUI linux distribution running on Windows 10 is to install Ubuntu (or whatever else is available) from the Windows store. This will install a VM using the built-in Hyper-V.

Otherwise, you could use Virtualbox or Vmware as noted. Using WSL to install GUI apps is definitely an ‘at your own risk’ proposition at present.

Regards,
Adrien

> On Jan 27, 2019, at 12:27 PM, Dean Gibson <[hidden email]> wrote:
>
> On 2019-01-27 06:45, David Carlson wrote:
>> ....
>>
>> I would suggest either setting up a virtual computer with a recent Linux
>> version such as Ubuntu 16.04 or 18.04, or acquiring an older machine from a
>> computer recycler and putting Linux on it for GnuCash as well as other
>> basic compu[t]er needs.
>>
>>
>> David C
>
> I don't know if this will help anyone, but if anyone is running Windows 10 x64, there is a new feature addition to Windows 10 called "Windows Subsystem for Linux" ("WSL") that you can enable, & then install (free) Linux distributions from the Microsoft Store: https://docs.microsoft.com/en-us/windows/wsl/install-win10>
> The install is absolutely trivial. Ubuntu 16.04 & 18.04 distributions are available, but I've installed Debian, & run some fairly complex bash scripts without a problem.
>
> That having been said, WSL is supported & primarily intended for running command-line programs, although some have been able to run a Linux GUI on it: https://askubuntu.com/questions/993225/whats-the-easiest-way-to-run-gui-apps-on-wsl-as-of-2018>
> All that having been said, I have no idea if WSL supports printing. I doubt it, but I thought I'd throw this out as a possible alternative to running a VM. WSL is much more "lightweight" than a VM, but takes a LOT less resources.