Re: Urgent: Balsa crashes on send - one reason found



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Helmut:

On 11/20/2017 11:45:15 AM Mon, Helmut Jarausch wrote:
…
To remember:

On my "old" system (from August, 2017) Balsa worked just fine.
Then - after some upgrades to my Gentoo system - Balsa crashed each time - see above.

I now had time to upgrade my  "old" system  step by step to see which update broke Balsa.

And here is the result:

Upgrading from enchant-1.6.0 to enchant-1.6.1 causes this error above.

Then I went back to my current system with all packages up-to-date (new glibc new glib, new gcc, ....)
Balsa still crashed on this system.

But, downgrading  enchant-1.6.1 to enchant-1.6.0 made Balsa working again..
That is the only change that was necessary.

There are several other packages here, e.g. geany, which use enchant, work just fine with enchant-1.6.1
except Balsa

Hopefully this helps to track down the problem within Balsa.
If I can help please tell my how.

Helmut

My Fedora 27 setup is still on enchant-1.6.0. I'll see if I can build Balsa against 1.6.1 to test it. It *says* it is 
"ABI and API compatible with 1.6..0"…

Best,

Peter
-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQS030wPRfNNA5alz3MfX9S1uSp09QUCWhMzrAAKCRAfX9S1uSp0
9UZiAJ0fZpb8lTAEBEyXHWMSoV2x8FMvrwCfdFChNuk2Wsanx3qwsCATFVKJAmo=
=sHMp
-----END PGP SIGNATURE-----


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]