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

On 09/08/2017 03:00:06 PM, Helmut Jarausch wrote:
I haven't changed Balsa nor its configuration. But my Gentoo system changes
nearly each day.
Suddenly, I cannot send emails with Balsa. It crashes all the time with:
Starting program: /usr/bin/balsa
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/".
[New Thread 0x7fffe2d46700 (LWP 30677)]
[New Thread 0x7fffe1df8700 (LWP 30678)]
[New Thread 0x7fffe15f7700 (LWP 30680)]
** Message: init gpgme version 1.8.0
** Message: protocol OpenPGP: engine /usr/bin/gpg2 (home (null), version 2.2.0) ** Message: protocol CMS: engine /usr/bin/gpgsm (home (null), version 2.2.0) ** Message: protocol GPGCONF: engine /usr/bin/gpgconf (home (null), version 2.2.0) ** Message: protocol Assuan: engine /run/user/230/gnupg/S.gpg-agent (home !GPG_AGENT, version 1.0.0) ** Message: protocol UIServer: engine /run/user/230/gnupg/S.uiserver (home (null), version 1.0.0) ** Message: protocol Spawn: engine /nonexistent (home (null), version 1.0.0)
** Message: OpenPGP protocol supported
** Message: CMS (aka S/MIME) protocol supported
Network is available   (Thu 07 Sep 2017 07:47:48 PM CEST)
[New Thread 0x7fffe08b5700 (LWP 30693)]
[New Thread 0x7fffd30a8700 (LWP 30873)]

Thread 1 "balsa" received signal SIGSEGV, Segmentation fault.
0x00007ffff24748a7 in g_main_context_prepare ()
   from /usr/lib64/
(gdb) where
#0  0x00007ffff24748a7 in g_main_context_prepare ()
   from /usr/lib64/

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.


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