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