As soon as the UFO krell entirely appears, GKrellm crashes with no error - it just goes gray (the background colour I have set in my GKrellm theme) - an entire rectangle of just grey. [ root@linuxbox /home/ddicks ] # emerge info Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.3) ================================================================= System uname: 2.6.3 i686 Intel(R) Pentium(R) 4 CPU 1.80GHz Gentoo Base System version 1.4.3.13 distcc 2.12.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -mfpmath=sse -msse -msse2 -mmmx -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -mfpmath=sse -msse -msse2 -mmmx -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="http://mirror.cpsc.ucalgary.ca/mirror/gentoo.org" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.ca.gentoo.org/gentoo-portage" USE="X aalib alsa avi berkdb bonobo cdf cdr crypt cups dvd encode esd flac foomaticdb gdbm gif gimpprint gnome gstreamer gtk gtk2 gtkhtml imagemagick imap imlib java javascript joystick jpeg ldap libg++ libwww mad mikmod mmx motif mozilla mpeg mpeg4 ncurses nls nptl oggvorbis opengl oss pam pdflib perl png ppds python quicktime readline samba sdl slang spell sse ssl svga tcltk tcpd tiff truetype usb v4l x86 xml2 xmms xv zlib"
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.