Gnucash 2.7 on Windows
John Ralls
jralls at ceridwen.us
Sat Nov 18 22:31:51 EST 2017
Sorry, no. Github’s issue tracker doesn’t scale to the number of bugs we need to manage.
Regards,
John Ralls
> On Nov 18, 2017, at 8:54 AM, Sébastien de Menten <sdementen at gmail.com> wrote:
>
> I filled a bug in bugzilla. Could it be possible to fill issues in github instead as the bugzilla interface is rather complex ?
>
> On Sat, Nov 18, 2017 at 4:38 AM, John Ralls <jralls at ceridwen.us <mailto:jralls at ceridwen.us>> wrote:
>
>
>> On Nov 17, 2017, at 5:05 PM, David Carlson <david.carlson.417 at gmail.com <mailto:david.carlson.417 at gmail.com>> wrote:
>>
>> I assume that you know that 2.7 is is a pre-release version, I would call
>> it an alpha or beta version, not for production use.
>>
>> That said, I thought that the developers had updated it so that it did not
>> crash instantly in Windows. Be sure that you have the most recent build.
>> It may be a bit hard to find. I personally am not testing it myself.
>>
>> David C
>>
>> On Fri, Nov 17, 2017 at 5:55 PM, Sébastien de Menten <sdementen at gmail.com <mailto:sdementen at gmail.com>>
>> wrote:
>>
>>> Had anyone got some success in running the gnucash 2.7 binaries on Windows?
>>> My version just crashes at startup time without any meaningful logs.
>>> _______________________________________________
>>> gnucash-user mailing list
>>> gnucash-user at gnucash.org <mailto:gnucash-user at gnucash.org>
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user <https://lists.gnucash.org/mailman/listinfo/gnucash-user>
>>> -----
>>> Please remember to CC this list on all your replies.
>>> You can do this by using Reply-To-List or Reply-All.
>>>
>
> The latest shouldn’t be hard to find at all, the links are in the announcement that leads http://www.gnucash.org/news.phtml <http://www.gnucash.org/news.phtml>. Since we’ll be releasing 2.7.2 next weekend it would be good to know if there’s still a problem. If 2.7.1 crashes please file a bug report as soon as you can with as much detail as possible—a stack trace would be ideal.
>
> Regards,
> John Ralls
More information about the gnucash-user
mailing list