Summary: | gkrellm-seti-0.7.0b-r1 crashes GKrellm after the work job is completed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dale K Dicks <dale_d> |
Component: | Current packages | Assignee: | Martin Holzer (RETIRED) <mholzer> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | dragonheart |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dale K Dicks
2004-03-08 13:54:22 UTC
could this be caused by starting the seti app with /etc/init.d/setiathome at boot and then loading gkrellm when i load up X? gkrellm-seti is now segfaulting gkrellm whenever I try to load it. i had to completely unmerge it. I have tested this a bit more and the crashing seems more consistent if it is left overnight and XScreensaver comes on. Occasionally during the day without the Screensaver on, the app won't crash. I am going to try xlockmore and see if that makes a difference. So if it is segfaulting when you run it (comment #2), then how can you get it to run (comment #3)? Mine segfaults immediately. I recompiled it and it run can be run but still segfaults after teh current Seti job completes. gkrellm-seti is now masked pending removal since the SETI@home 3.x service was discontinued upstream. All related packages will be removed from Portage. |