Nekochan Net

Hi all,

So I downloaded all of the nekoware and installed ... really great stuff.

I was curious if anyone had any problems with xscreensaver-getimage?

When I run it, it dies.

Like so:


This matters because it makes the webcollage screen saver die.

I have a plain-jane install of irix 6.5.20m on my Octane. I have some freeware installed, all the nekoware, I have fixed all my paths for both distributions - Nekoware is first in the path environment variable...

I figure this must work for other folks, since it has not been mentioned in the forums.

-Nick

BadMatch errors are usually attributed to SGI Freeware FAQ4.3:

http://freeware.sgi.com/faq.html#Q4.3

_________________
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.

Not all of the Xscreensaver hacks are operational for me -- I'd be interested on what excatly you are doing that generates the Bad Match error. Maybe I can peek at the source code and come up with a work-around.

BTW I get following results when I run webcollage directly



I assume it's because I haven't set it up correctly.

I'm not quite sure what you mean by "what I am doing" to get the BadMatch error, but when I get a chance I'll try to describe the environment. Given the previous reply, I did try setting my Xsgi settings differently - then I messed with some other stuff, decided to reboot (I had been using chkconfigs as well), and on reboot, it won't get to the login screen. The point is, since I am already busy with other stuff, fixing my SGI isn't top priority (even though I know how) this moment. I'll post back here when I get the time (in a day or two).

As for the perl, I decided that since Freeware and Nekoware include newer perls I would try uninstalling the IRIX perl. After uninstall, I made sure paths were set, and the missing "bytes.pm" error dissappeared (presumably becuase Perl could now find it in the nekoware/lib/perl directory).

Hmm. I'll have to go back and make sure xscreensaver was finding the nekoware Perl during configure. Also, I tried running the xscreensaver-getimage command directly, giving it the root window id as an argument. Although I didn't know what to expect for results, it seemed to work, but if you could describe the steps for your trial image grab, I'd be happy to reproduce them to see if I get the BadMatch X error.

This generally happens if the Xservers entry contains a carriage return someplace in the middle of the line - it needs to be one line only with "-depth 24 -class TrueColor" added to the end of the existing line.

BadMatch errors are visual depth/colordepth mismatch errors - so I'd check that out first.



http://www.rahul.net/kenton/perrors.html

_________________
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.

Ressurecting this thread on a tangential note:
I thought it worthwhile to document the occassional (and not so occasional) Xscreensaver problem I've had since the first IRIX Xscreensaver built here. Basically, when I "jog" the keyboard or mouse to wake the system up, Xscreensaver will crash the Xserver instead of giving me the password prompt. This seems to only happen on Vpro graphics (V6/V12). The IR3/4 and Octane with MMX are stable. The error in the SYSLOG is



If y'all have any thoughts, I'd love to poke around the source code some.

I found this in the 6.5.28 release notes



Unfortunately, the Xscreensaver error still occurs under Vpro in 6.5.28.



I grep hunted all of the Xscreensaver source for glDrawPixels but was surprised to find no occurances.

Still a bug lunking in the IRIX video drivers?

For the other Vpro users out there I have a theory I'm testing. I think only the Really Slick Screensavers (neko_rss) hacks are causing the Xserver crash. I've set the screensaver to flurry and been up 2 days so far. Here's hoping!

[b]Edit[\b]: It's been more than a week, which is *much* longer than the mean-time between crashes I was experiencing. Looks like the GL in the Really Slick Screensaver may be throwing V12 cards for a loop.