begin Net Llama's quote: | Hrmmm...not that i'm doubting your experience with it but: | 1) Xscreensaver has had quite a few revs over the past few months, | i'd think that if there was a problem with one, it would have been | fixed by now
not necessarily. a lot of the hacks are contribs, and i don't know how closely jamie goes through them. | 2) I've always tested all of my choices before using them, and | never was able to forcefully reproduce any problem me, too. but that doesn't necessarily make the nut. for instance, in about 3.32, the extrusion hack would run, and nicely, too. for awhile. sometimes it would make it through its whole cycle. but sometimes it would do some little thing that would flat-out freeze x, keyboard, mouse, the whole shebang. the only reason i ever knew which hack it was was that it stayed on the screen when it froze. i locked it out, and all was well thereafter. problem this time, here, is that this time around the screen is blank when whatever hack it is goes south. i'm trying to cook up some kind of way of logging the modules it uses. then when it freezes and i have to do the brb, on restart i could look at the log, identify the last module called, and take it off the list. so far, none of the obvious logging methods has proved effective. -- dep There is sobbing of the strong, And a pall upon the land; But the People in their weeping Bare the iron hand; Beware the People weeping When they bare the iron hand. _______________________________________________ Linux-users mailing list - http://linux.nf/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
