From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Foa7E-0005ZZ-Px for garchives@archives.gentoo.org; Fri, 09 Jun 2006 06:05:05 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.6) with SMTP id k5963cqJ014890; Fri, 9 Jun 2006 06:03:38 GMT Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.201]) by robin.gentoo.org (8.13.6/8.13.6) with ESMTP id k595vjPV017137 for ; Fri, 9 Jun 2006 05:57:45 GMT Received: by nz-out-0102.google.com with SMTP id q3so594497nzb for ; Thu, 08 Jun 2006 22:57:44 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=SMb8Trtsr74O++ZzBooyuoj82jNEQTuOLZTnjQzJ9tmrN2tGCyQUeYJR3eF93k56oyLbSPnbYPGcX+nxHMZYwNEGZ0WLjlfDdcZ9gVYoU23fEZ5F78bCY0D62kxFY93rxgIPUoeyCVvZz4iUk7Oa7LL1IUkwI7WD90j+6ie+vLA= Received: by 10.36.250.59 with SMTP id x59mr3477764nzh; Thu, 08 Jun 2006 22:57:44 -0700 (PDT) Received: by 10.37.22.74 with HTTP; Thu, 8 Jun 2006 22:57:44 -0700 (PDT) Message-ID: <9acccfe50606082257o654a9da7ja0c9041b6534a46c@mail.gmail.com> Date: Thu, 8 Jun 2006 22:57:44 -0700 From: "Kevin O'Gorman" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] KAlarm now broken -- suffers many SIGFPE alarms In-Reply-To: <200606081255.57582.jesse.hannah@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_20228_741049.1149832664140" References: <200606081255.57582.jesse.hannah@gmail.com> X-Archives-Salt: 905451b2-9094-4fad-8f9d-012e68b708ff X-Archives-Hash: bf885b02c674cb7f454c8340ad210e62 ------=_Part_20228_741049.1149832664140 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 6/8/06, Jesse Hannah wrote: > > 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 That sounds like really good advice, so I investigated a bit. There indeed seems some sort of conflict between kdepim and kalarm. There's something familiar about the pattern of "blocking" I saw with "emerge -pe kalarm kdepim" that made me try unmerging both of them first . I'm doing a new emerge --oneshot now. Wish me luck. Maybe my list of alarms will survive? -- Kevin O'Gorman, PhD ------=_Part_20228_741049.1149832664140 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 6/8/06, Jesse Hannah <jesse.hannah@gmail.com> wrote:
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

That sounds like really good advice, so I investigated a bit.  There indeed
seems some sort of conflict between kdepim and kalarm.  There's something
familiar about the pattern of "blocking" I saw with "emerge -pe kalarm kdepim"
that made me try unmerging both of them first .  I'm doing a new emerge
--oneshot now.   Wish me luck.  Maybe my list of alarms will survive?

--
Kevin O'Gorman, PhD
------=_Part_20228_741049.1149832664140-- -- gentoo-user@gentoo.org mailing list