Re: [NOT SO BRIGHT UPDATE] Installing K3b installs HAL. Should I do it?
On Thu, 12 May 2011 02:28:27 +0000, Juan R. de Silva wrote:
> If you install Clamav after HAL was installed, a file /var/run/clamav/
> freshclam.pid is created with root:haldaemon group:owner permissions and
> the following error is generated after installation: "ERROR: Can't save
> PID to file /var/run/clamav/freshclam.pid: Permission denied"
> But if you install Clamav on a fresh squeeze without HAL installed, the
> ownership of the same file is root:clamav instead, and Clamav does
> produce this error.
HAL is still being installed so this can affect other people.
> While the problem is really a small one, one can always change the owner
> of the file, it shows that presence of HAL in the system might
> potentially be root of unpredictable problems since some apps are
> confused by its presence. And I can imagine that in some instances to
> find the problem of the kind could be quite time consuming.
That sounds a bit apocalyptic :-)
I don't think so because in the end you can have problems with every
single package installed on the system conflicting with specific parts of
> So, I'm not sure yet, but at least for now I probably would prefer to
> live without K3b. It's a pity though. It's a best burning app over
> there. I hope K3b developers would remove this dependency soon.
Again, HAL is being pulled as a hard requirement by many others packages,
it's not K3B the only one that depends on it (for instance, "xfburn" also