licq fails to start when its PID file (~/.licq/licq.pid) exists, and a
process with that PID exists, even if that process isn't licq. I believe a
simple check that the process has the right name (and owner!!) is in order.
System tools like ``start-stop-daemon'' check all those properties on a pid before even considering that it is already running, so this might be valid.
Package maintainer wrote:
Since no solution was proposed for this bug, I close it. You can reopen
it if you have additional information.
Couldn't you just submit it upstream as a bug and tag it ``upstream''? Or ``help''. Sure, the problem is easy to fix for the experienced and with a reboot. But the average user does not know why licq won't start up.
Kind regards, Philipp Kern Debian Developer
PGP.sig
Description: This is a digitally signed message part
