| 1 |
On 6/8/06, Jesse Hannah <jesse.hannah@×××××.com> wrote: |
| 2 |
> |
| 3 |
> Kevin O'Gorman wrote: |
| 4 |
> |
| 5 |
> > It doesn't die. And it usually doesn't do it when I'm around, but when |
| 6 |
> I |
| 7 |
> > come |
| 8 |
> > back to my system in the morning there are usually 200 or so crash |
| 9 |
> dialogs |
| 10 |
> > waiting for me, all indicating the application suffered a SIGFPE |
| 11 |
> (floating |
| 12 |
> > point error?). But it keeps on working anyway. |
| 13 |
> > |
| 14 |
> > Am I alone with this? |
| 15 |
> > |
| 16 |
> > ++ kevin |
| 17 |
> > |
| 18 |
> |
| 19 |
> Probably not, depends on the version of KAlarm that you're using. But more |
| 20 |
> likely than anything else is that something didn't quite compile right |
| 21 |
> when |
| 22 |
> you were emerging whatever KAlarm's parent package (kdepim?) is. I've had |
| 23 |
> that happen with other things such as xine-lib, and I've discovered that |
| 24 |
> if |
| 25 |
> something keeps crashing re-emerging it (or its parent package, in |
| 26 |
> KAlarm's |
| 27 |
> case) usually fixes the problem. And, a SIGFPE is the sort of thing that a |
| 28 |
> build problem would be the cause of. |
| 29 |
> |
| 30 |
> General rule of thumb: If it crashes, rebuild it. :D |
| 31 |
> |
| 32 |
> -- |
| 33 |
> Jesse Hannah |
| 34 |
|
| 35 |
|
| 36 |
That sounds like really good advice, so I investigated a bit. There indeed |
| 37 |
seems some sort of conflict between kdepim and kalarm. There's something |
| 38 |
familiar about the pattern of "blocking" I saw with "emerge -pe kalarm |
| 39 |
kdepim" |
| 40 |
that made me try unmerging both of them first . I'm doing a new emerge |
| 41 |
--oneshot now. Wish me luck. Maybe my list of alarms will survive? |
| 42 |
|
| 43 |
-- |
| 44 |
Kevin O'Gorman, PhD |
Archives