From: Jesse Hannah <jesse.hannah@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KAlarm now broken -- suffers many SIGFPE alarms
Date: Thu, 8 Jun 2006 12:55:54 -0700 [thread overview]
Message-ID: <200606081255.57582.jesse.hannah@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
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: FlakPenguin@Freenode
GPG Key: 0x78F156E7
Available on the keyservers (search the key or for "Jedi Web-Penguin")
or from <http://everstar.hostultra.com/jesse.asc>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-06-08 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 19:55 Jesse Hannah [this message]
2006-06-09 5:57 ` [gentoo-user] KAlarm now broken -- suffers many SIGFPE alarms Kevin O'Gorman
2006-06-10 2:11 ` Kevin O'Gorman
-- strict thread matches above, loose matches on Subject: below --
2006-06-08 4:16 Kevin O'Gorman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200606081255.57582.jesse.hannah@gmail.com \
--to=jesse.hannah@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox