On Sun, Feb 22, 2015 at 6:24 PM, Sébastien Villemot
<[email protected]> wrote:
> Le dimanche 22 février 2015 à 17:15 -0500, Reinhard Tartler a écrit :
>> On Sun, Feb 22, 2015 at 4:30 PM, Sébastien Villemot
>> <[email protected]> wrote:
>>
>> > I don't get it. You told in your bug report that gnucash was starting
>> > successfully. Now you say it crashes. You have to decide…
>>
>> The plugin (the .so) crashes with an uncaught python exception. This
>> is captured and reported by apport. Gnucash (the host program) itself
>> tolerates such crashes and carries on.
>>
>> Does this clarify the issue?
>
> Thanks for your clarifications.
>
> However I am unable to replicate the problem, even after installing
> apport-gtk. I see no trace of a segmentation fault or something similar.
> And apport does not pop up. Could you please tell me what I should do to
> replicate the issue?
I don't see any segmentation fault either. The problem is the uncaught
python exception that leads to this output:
Traceback (most recent call last):
File "/usr/share/gnucash/python/init.py", line 3, in <module>
from gnucash import *
ImportError: No module named gnucash
Found Finance::Quote version 1.35
Possibly the Debian apport package does not catch uncaught python
exceptions (yet?). This may or may not be a separate issue in the
Debian apport package.
> Also, I saw your recent comments in Ubuntu bug #1369273, and I think you
> are confusing two issues. Version 2.6.4-1 of gnucash really fixed a
> crash, more precisely a segmentation fault, that I could replicate. That
> segfault was occurring when python-gnucash was not installed, and would
> be triggered *at the exit* of gnucash, i.e. after clicking the close
> button. So it was barely unnoticeable without apport, but still very
> real. This segmentation fault is no longer present in the version of
> gnucash currently in unstable. Can you therefore confirm that you could
> replicate a segmentation fault with the current version (2.6.4-3) and on
> a Debian system (i.e. not on Ubuntu)?
You are right that ubuntu bug discusses two separate issues, of which
the segmentation fault was brought up not sooner than update #5. I
havenot been filing this issue for the segmentation fault, but for
the uncaught python exception.
I have also installed gnucash in a clean unstable chroot and confirm
that the exception remains uncaught there as well.
BTW, https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1369273/comments/19
is a comment from Geert Janssens, one of the gnucash developers, who
basically confirms this issue. I'm CC'ing him with this email. Geert,
maybe you can share your opinion on this?
Cheers,
Reinhard
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
