[Bug 480410] Re: grisbi crash (segmentation default) when apply a new state

2011-02-06 Thread Launchpad Bug Tracker
[Expired for grisbi (Ubuntu) because there has been no activity for 60 days.] ** Changed in: grisbi (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/480410

[Bug 480410] Re: grisbi crash (segmentation default) when apply a new state

2010-12-08 Thread Stéphane Glondu
** Changed in: grisbi (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/480410 Title: grisbi crash (segmentation default) when apply a new state -- ubuntu-bug

[Bug 480410] Re: grisbi crash (segmentation default) when apply a new state

2010-12-08 Thread Stéphane Glondu
Is this bug still on topic with version 0.6.0? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/480410 Title: grisbi crash (segmentation default) when apply a new state -- ubuntu-bugs mailing list ub

[Bug 480410] Re: grisbi crash (segmentation default) when apply a new state

2009-11-20 Thread Viale Fabrice
Apparently, the problem has been identified and has just been resolved. Is there any plan to build a .deb with the last version? -- grisbi crash (segmentation default) when apply a new state https://bugs.launchpad.net/bugs/480410 You received this bug notification because you are a member of Ubun

[Bug 480410] Re: grisbi crash (segmentation default) when apply a new state

2009-11-20 Thread Viale Fabrice
Same problem, but segmentation fault exists for long (4-5 years). Thus it is not probably an Ubuntu problem. Don't know whether or not it is the problem treaded recently and described at Grisbi's site. The main problem is to update Grisbi with this recent code correction. It is effectively critical