Description of problem:
Had unchecked clamd plugin, due to problems with ping clamd. https://lists.fedoraproject.org/pipermail/test/2012-December/112542.html
Now hen I go to re-check scan all messages "Configuratuion - Prefrences - plugins - clamd" it crashes
Version-Release number of selected component:
Thread no. 1 (10 frames)
#0 clamav_create_widget_func at clamav_plugin_gtk.c:430
#1 prefswindow_build_page at prefswindow.c:304
#3 prefswindow_row_selected at prefswindow.c:724
#5 _gtk_tree_selection_row_is_selectable at gtktreeselection.c:1273
#6 _gtk_tree_selection_internal_select_node at gtktreeselection.c:1330
#8 gtk_tree_view_real_set_cursor at gtktreeview.c:12595
#9 gtk_tree_view_button_press at gtktreeview.c:2797
#10 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
#15 gtk_widget_event_internal at gtkwidget.c:5017
#16 gtk_widget_event at gtkwidget.c:4814
Please try to resubmit this bug report in ABRT. So far, there are no attachments. No stacktrace.
OS Release: Fedora release 18 (Spherical Cow)
There's still no backtrace, and the line numbers in the truncated one are useless. You could still cut'n'paste the backtrace manually from within ABRT. Or generate it manually with gdb after using debuginfo-install, of course.
From a tester perspective, it has not been possible to reproduce a crash of the plugin's preferences dialog, no matter how often I tried to open/close it with clamd running or inactive.
Unfortunately I can't at the moment.
Clamav is completely uninstalled.
it may have been causing the problem
abrt had been cleared out due to wanting to just add a comment,
and bz was giving a http 502. and not much extra
So will close as nab for this.
Until can reproduce.
Claws-mail is now working with no clamd plugin or otherwise.
It *is* a bug. Claws Mail must not crash in the plugin preferences. Not either if the plugin code doesn't manage to connect with clamd.
But if it's not reproducible [and mind you, the developer(s) have likely not had it crash either], and without a detailed stacktrace, somebody would need to proof-read the source code and come up with a theory what might make it crash.
That is what I've done after skimming over the source code. :-)
Created attachment 664151 [details]
one basic way to fix it
Created attachment 664152 [details]
regenerated the missing backtrace
Upstream has found an underlying [worse] problem in the code, which to fix will need more changes.
| Changes related to this bug have been committed.
| Please check latest CVS and update the bug accordingly.
Fix is included since
- clamd-3.5.5cvs2.tar.gz (for old extra plugins)