Bug 26011

Summary:	clamtk does not load or install any virus signature updates after changing setting
Product:	Mageia	Reporter:	Serge Guindon <serge.guindon>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	lewyssmith
Version:	7
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	clamtk-6.01-1.mga7.src.rpm	CVE:
Status comment:

Description Serge Guindon 2020-01-04 01:40:59 CET

Description of problem:

when i did modification to theme appearance in settings clamtk stopped to load or install virus updates

Version-Release number of selected component (if applicable):

clamtk-6.01-1.mga7.src.rpm


Steps to Reproduce:
1.open settings
2.go to appearance
3.change any settings

Comment 1 Lewis Smith 2020-01-04 21:27:01 CET

Was clamav in the process of downloading the database (which takes a long time) when you changed a setting in clamtk? That is, did it stop in the middle? Or did you notice subsequently that the database was not being updated? If so, how did you notice (or know)?

I am unsure how the D/B gets updated. We push new versions periodically; the package description talks of "a tool for automatic updating via Internet", I suspect that the command '$ freshclam' does that. If this is so, can you say whether that does not work any more after changing clamtk settings? That would be surprising.

I will if necessary install & try this, depending on your reply.

Summary: clamtk does not load or install any virus signature updates => clamtk does not load or install any virus signature updates after changing setting
CC: (none) => lewyssmith

Comment 2 Aurelien Oudelet 2020-08-26 13:35:59 CEST

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released.

Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD