Date: Tue, 22 Apr 2003 14:48:02 -0500 From: Glenn Johnson <gjohnson@srrc.ars.usda.gov> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: FreeBSD GNOME Users <gnome@freebsd.org> Subject: Re: xscreensaver problem Message-ID: <20030422194802.GA70621@node1.cluster.srrc.usda.gov> In-Reply-To: <1051037867.1079.73.camel@gyros> References: <20030422182907.GA23560@node1.cluster.srrc.usda.gov> <1051036572.1079.67.camel@gyros> <20030422185005.GA84400@node1.cluster.srrc.usda.gov> <1051037867.1079.73.camel@gyros>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 22, 2003 at 02:57:47PM -0400, Joe Marcus Clarke wrote:
> On Tue, 2003-04-22 at 14:50, Glenn Johnson wrote:
>
> > > >
> > > > The problem is that all xscreensaver hacks that use the GL
> > > > visual fail during screen blanking. The screensavers look fine
> > > > in the preview window of the xscreensaver-demo interface. Also,
> > > > I can call them from the command line and they will appear and
> > > > execute just fine in a window. But when they are used to blank
> > > > the screen, or I hit 'Preview' from the interface, they fail. I
> > > > get a message like the following (hand transcribed):
> > > >
> > > > xscreensaver: 0: child pid 29034 (cage) terminated with SIGSEGV
>
> Found your problem. Remove the line that says:
>
> memoryLimit: 50M
>
> from ~/.xscreensaver, restart your server, and you'll be set.
That was it. I took a look at the manual page to see what the
default is. I found this:
Default: 0, meaning "no limit." 30M is a good choice on most
systems. (But beware that setting this to a small value can cause
OpenGL programs to malfunction on certain systems.)
D'oh.
Thanks.
--
Glenn Johnson
USDA, ARS, SRRC Phone: (504) 286-4252
New Orleans, LA 70124 e-mail: gjohnson@srrc.ars.usda.gov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030422194802.GA70621>