Re: Unstable terminates immediately

> On Mar 3, 2018, at 12:37 AM, Martin Preuss wrote: > > Hi, > > Am 03.03.2018 um 05:40 schrieb John Ralls: > [...] >> https://fedora.pkgs.org/27/fedora-x86_64/ktoblzcheck-1.44-9.fc27.x86_64.rpm.html >> >>

Re: Unstable terminates immediately

Hi, Am 03.03.2018 um 05:40 schrieb John Ralls: [...] > https://fedora.pkgs.org/27/fedora-x86_64/ktoblzcheck-1.44-9.fc27.x86_64.rpm.html > > > > It should be a dependency of aqbanking. Gwengui-gtk3 is built by

Re: Unstable terminates immediately

> On Mar 2, 2018, at 1:26 PM, Alex Aycinena wrote: > > > > On Fri, Mar 2, 2018 at 6:21 AM, John Ralls > wrote: > > > > On Mar 2, 2018, at 4:03 AM, Geert Janssens >

Re: Unstable terminates immediately

On Fri, Mar 2, 2018 at 6:21 AM, John Ralls wrote: > > > > On Mar 2, 2018, at 4:03 AM, Geert Janssens > wrote: > > > > Op vrijdag 2 maart 2018 02:21:45 CET schreef Alex Aycinena: > >> On Thu, Mar 1, 2018 at 5:15 PM, John Ralls

Re: Unstable terminates immediately

> On Mar 2, 2018, at 4:03 AM, Geert Janssens wrote: > > Op vrijdag 2 maart 2018 02:21:45 CET schreef Alex Aycinena: >> On Thu, Mar 1, 2018 at 5:15 PM, John Ralls >> >> wrote: >>> Run it in the debugger and see where it’s crashing and

Re: Unstable terminates immediately

Op vrijdag 2 maart 2018 02:21:45 CET schreef Alex Aycinena: > On Thu, Mar 1, 2018 at 5:15 PM, John Ralls > > wrote: > > Run it in the debugger and see where it’s crashing and why? > > > > Regards, > > John Ralls > > Actually I tried that before sending the first

Re: Unstable terminates immediately

On Thu, Mar 1, 2018 at 5:15 PM, John Ralls wrote: > > > > Run it in the debugger and see where it’s crashing and why? > > Regards, > John Ralls > > Actually I tried that before sending the first e-mail and there was no crash and no backtrace. It simply exited during

Re: Unstable terminates immediately

Op donderdag 1 maart 2018 21:50:55 CET schreef Alex Aycinena: > Geert, > > Rebuilt after checking out unstable with same results. > I presume, though I can't infer from your answer you did run rm -fr * .??* in your build directory ? Could selinux be interfering ? You could try sudo setenforce 0

Re: Unstable terminates immediately

Geert, Rebuilt after checking out unstable with same results. On Thu, Mar 1, 2018 at 12:02 PM, Geert Janssens wrote: > > > Other than not fully clearing your build directory I don't see any issues. > If > that doesn't fix it, you could > > 1. check if the gnucash

Re: Unstable terminates immediately

Op donderdag 1 maart 2018 19:31:20 CET schreef Alex Aycinena: > On Thu, Mar 1, 2018 at 8:51 AM, Alex Aycinena > > wrote: > > On Wed, Feb 28, 2018 at 12:58 PM, Geert Janssens < > > > > geert.gnuc...@kobaltwit.be> wrote: > >> Alex, > >> > >> I can't reproduce this on

Re: Unstable terminates immediately

On Thu, Mar 1, 2018 at 8:51 AM, Alex Aycinena wrote: > > > On Wed, Feb 28, 2018 at 12:58 PM, Geert Janssens < > geert.gnuc...@kobaltwit.be> wrote: > >> Alex, >> >> I can't reproduce this on Fedora 26 (64bit) not even after a clean >> rebuild. >> Gnucash starts and runs

Re: Unstable terminates immediately

On Wed, Feb 28, 2018 at 12:58 PM, Geert Janssens wrote: > Alex, > > I can't reproduce this on Fedora 26 (64bit) not even after a clean rebuild. > Gnucash starts and runs just fine. > > What platform are you on again ? > Do you see anything in the build log ? An

Re: Unstable terminates immediately

Alex, I can't reproduce this on Fedora 26 (64bit) not even after a clean rebuild. Gnucash starts and runs just fine. What platform are you on again ? Do you see anything in the build log ? An unusual warning or something ? Do you configure for ninja or makefiles ? Geert Op woensdag 28