Seg Fault

[John David Ravenscroft]

Thanks derek; the repo enables upgrade. Still crashing though. I'll make a
new thread.

On Fri, 27 May 2016 at 12:25 Derek Atkins <derek at ihtfp.com> wrote:

> Try the getdeb repo.
>
> -derek
>
> Sent on my mobile. Please forgive any typos.
> ----- Reply message -----
> From: "John David Ravenscroft" <j.ravenscroft at gmail.com>
> To: "Derek Atkins" <derek at ihtfp.com>, <gnucash-user at gnucash.org>
> Subject: Seg Fault
> Date: Fri, May 27, 2016 1:11 PM
>
> Thanks Derek.
>
> Those are the versions in my repos, only upgrade I've found is source and
> I'm having trouble compiling. Specifically the last hurdle I hit was
> loading glib, gio, gthread etc at configuration stage on debian based linux
> mint. I'll keep looking for compilation how-tos.
>
> Regards,
>
> John
>
> On Fri, 27 May 2016, 11:57 Derek Atkins, <derek at ihtfp.com> wrote:
>
> > 2.6.12 is current.  2.6.1 and 2.6.4 are known to be buggy. Please upgrade
> > and try again.
> >
> > -derek
> >
> > Sent on my mobile. Please forgive any typos.
> >
> > ----- Reply message -----
> > From: "John David Ravenscroft" <j.ravenscroft at gmail.com>
> > To: <gnucash-user at gnucash.org>
> > Subject: Seg Fault
> > Date: Fri, May 27, 2016 11:28 AM
> >
> > Program keeps exiting with seg fault during different tasks, on different
> > machines, with different versions (2.6.1 and 2.6.4) using the same file (Or
> > a sync copy at least). Happens usually when altering or saving something to
> > do with the business tools, such as a bill or invoice. I'm now at the point
> > where saving my file causes the fault.
> >
> > stack trace from version 2.6.4 running on LMDE 2
> >
> > #0  0x00007ffff6302c23 in ?? () from
> > /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
> > #1  0x00007ffff630c08b in ?? () from
> > /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
> > #2  0x00007ffff39f2474 in ?? () from
> > /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> > #3  0x00007ffff3a0c087 in g_signal_emit_valist () from
> > /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> > #4  0x00007ffff3a0cf2a in g_signal_emit_by_name () from
> > /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> > #5  0x00007ffff46262e9 in ?? () from
> > /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
> > #6  0x00007ffff4626a96 in ?? () from
> > /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
> > #7  0x00007ffff4626b3e in ?? () from
> > /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
> > #8  0x00007ffff5f7fc5d in g_main_context_dispatch () from
> > /lib/x86_64-linux-gnu/libglib-2.0.so.0
> > #9  0x00007ffff5f7ff48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> > #10 0x00007ffff5f80272 in g_main_loop_run () from
> > /lib/x86_64-linux-gnu/libglib-2.0.so.0
> > #11 0x00007ffff6375597 in gtk_main () from
> > /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
> > #12 0x00007ffff7894ac9 in gnc_ui_start_event_loop () from
> > /usr/lib/x86_64-linux-gnu/gnucash/gnucash/libgncmod-
> >
> > gnome-utils.so
> > #13 0x0000000000402d54 in _start ()
> >
> > Is this a known occurrence? Are there any alterations I can make to my file
> > to avoid this? Is there any other info I can provide?
> >
> > Thanks for any help available,
> >
> > John
> > ______________________________
>
> _________________
> > gnucash-user mailing listgnucash-user at gnucash.orghttps://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.
> >
> >
> _______________________________________________
> gnucash-user mailing listgnucash-user at gnucash.orghttps://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.
>
>