No clue if that is a known bug but there are also applications using the Sparkle framework to update that sometimes have the same problem...
I have found a bug or two though when it comes to Leopard:
from LogMeIn > stderr.log
Generating a 1024 bit RSA private key
....................++++++
..++++++
unable to write 'random state'
writing new private key to '/tmp/RAR930b.tmp'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
countryName []:US
commonName []:LogMeIn Inc.
Generating a 1024 bit RSA private key
..++++++
.........................++++++
unable to write 'random state'
writing new private key to '/tmp/RAR945c.tmp'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
commonName []:Switch.local
Signature ok
subject=/CN=Switch.local
Getting CA Private Key
unable to write 'random state'
SessionCommunicationThread - SessionAgent was closed unexpectedly
And there's a second bug, you can not disable the LogMeIn service. Whenever I click Disable LogMeIn it just doesn't get disabled
So basically, it works, it's usable but there are a few things that need straitening out.