Version-Release number of selected component:
Thread no. 1 (10 frames)
#1 hooks_marshal at hooks.c:108
#3 g_hook_list_marshal at ghook.c:676
#4 hooks_invoke at hooks.c:126
#5 do_copy_msgs at folder.c:3622
#6 folder_item_move_msgs at folder.c:3675
#7 inc_start at inc.c:712
#8 inc_all_account_mail at inc.c:403
#9 _g_closure_invoke_va at gclosure.c:840
#11 g_signal_emit_by_name at gsignal.c:3393
Created attachment 680458 [details]
Created attachment 680459 [details]
Created attachment 680460 [details]
Created attachment 680461 [details]
Created attachment 680462 [details]
Created attachment 680463 [details]
Created attachment 680464 [details]
Created attachment 680465 [details]
Created attachment 680466 [details]
Created attachment 680467 [details]
How often does it happen? Reproducibly?
Upstream would like to know whether possibly you had tried and unloaded the NewMail plug-in (claws-mail-plugins-newmail) prior to this crash?
Проблема возникла один лишь раз и я не знаю, как её воспроизвести. При попытке загрузить NewMail получаю сообщение об ошибке:
"Следующая ошибка произошла при попытке загрузить модуль newmail.so:
No such file or directory".
I tried to translate that from Russian to English using Babylon. The error message is much different than in English but it could mean that you've not unloaded the NewMail plugin in the Preferences.
What do you get if you run: grep plugins ~/.claws-mail/clawsrc
$ grep plugins ~/.claws-mail/clawsrc
Okay. So, it's not loaded. Keep your configuration. Don't load the NewMail plugin if you don't need it. Remove the claws-mail-plugins-newmail package if it's installed.
Try to reproduce the crash _without_ using the NewMail plugin. That would be interesting.
Я не знаю, как воспроизвести эту проблему.
Это случилось опять, причём я не работал в это время в почтовой программе.
Please stop replying in Russian. I do not speak Russian, and all I can do is use online-translation services, but because they are not accurate, we talk past eachother.
So, to sum up:
- There is only one Claws Mail plug-in, which registers itself on the "mail_postfiltering_hooklist": NewMail
- If you don't use that plug-in, the "mail_postfiltering_hooklist" list is empty, and no hook would be called when fetching new messages (folder.c line 3622).
- The attached backtrace is about a crash due to calling an invalid hook.
To me that looks like memory is getting corrupted/damaged somewhere.
I wrote an e-mail and sent it. The e-mail seemed to make it through SMTP correctly, but it seems that Claws crashed during the step of saving it to my "Sent" IMAP folder.
OS Release: Fedora release 18 (Spherical Cow)
Randy, avoid the NewMail plugin like a plague for now. I dunno how much you've been playing with it due to the other bug report, but in this case Claws Mail called an invalid mail postfiltering hook. Also see http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2885
Understood, I've removed it from my system. Thanks for your help!
*** Bug 913553 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.