Bug 87591

Summary:	KMal anti-virus wizard from KDE 3.3.0_rc2 does not recognize f-prot on Gentoo
Product:	[Unmaintained] kmail	Reporter:	Henk Poley <hpoley>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version First Reported In:	1.7
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Henk Poley 2004-08-20 12:28:08 UTC

Version:           1.7 (using KDE 3.3.0, Gentoo)
Compiler:          gcc version 3.3.3 20040412 (Gentoo Linux 3.3.3-r6, ssp-3.3.2-2, pie-8.7.6)
OS:                Linux (i686) release 2.6.7

No installed virusscanners show up in the anti-virus wizard of KMail from KDE 3.3.0_rc2, though f-prot version 4.3.1 is installed as /opt/f-prot/f-prot (Gentoo ebuild). There's also a little /usr/bin/f-prot.sh script which will invoke the above executable.

Obviously expected behaviour is that f-prot is detected and setup by the wizard.

Comment 1 Andreas Gungl 2004-08-20 12:40:51 UTC

> No installed virusscanners show up in the anti-virus wizard of KMail from
> KDE 3.3.0_rc2, though f-prot version 4.3.1 is installed as
> /opt/f-prot/f-prot (Gentoo ebuild). There's also a little
> /usr/bin/f-prot.sh script which will invoke the above executable.

Please check if the f-prot executable is in the path. If it's not and the f-prot.sh is used instead (what I believe), then either create a symlink or extend the PATH to access f-prot directly.

> Obviously expected behaviour is that f-prot is detected and setup by the
> wizard.

Sure, but if distribution XYZ uses f-prot.sh or f-prot-wrapper.sh or anything else except the native executable called f-prot, then the distributor should adjust the scripts in KDE as well.

That's why I close this report as invalid. Thanks for understanding.

Comment 2 Henk Poley 2004-08-20 12:59:57 UTC

I'll open a bug at bugs.gentoo.org for this problem in the f-prot ebuild, adding a symlink should be a quicky.

Comment 3 Henk Poley 2004-08-20 13:02:07 UTC

Actually there already is a bug report at bugs.gentoo.org.

See: http://bugs.gentoo.org/show_bug.cgi?id=56332