Kevin O'Gorman wrote: > It doesn't die. And it usually doesn't do it when I'm around, but when I > come > back to my system in the morning there are usually 200 or so crash dialogs > waiting for me, all indicating the application suffered a SIGFPE (floating > point error?). But it keeps on working anyway. > > Am I alone with this? > > ++ kevin >
Probably not, depends on the version of KAlarm that you're using. But more likely than anything else is that something didn't quite compile right when you were emerging whatever KAlarm's parent package (kdepim?) is. I've had that happen with other things such as xine-lib, and I've discovered that if something keeps crashing re-emerging it (or its parent package, in KAlarm's case) usually fixes the problem. And, a SIGFPE is the sort of thing that a build problem would be the cause of. General rule of thumb: If it crashes, rebuild it. :D -- Jesse Hannah Homepage: <http://everstar.hostultra.com/> IRC Nick: [EMAIL PROTECTED] GPG Key: 0x78F156E7 Available on the keyservers (search the key or for "Jedi Web-Penguin") or from <http://everstar.hostultra.com/jesse.asc>
pgpjYEuWwmsRn.pgp
Description: PGP signature
