Red Hat Bugzilla – Bug 49136
'flag' screensaver dies with XError error messages -- sometimes.
Last modified: 2014-03-16 22:21:47 EDT
Description of Problem:
Sony Vaio PCG-SR1K with 128 megs of memory with fairfax beta1 on it.
Running Gnome with random screensaver set in capplet. Had sat idle for
hours when I caught an xscreensaver error: yellow text in top left of
screen. Took photo, started to copy down error message. Screen blanked
before I could copy it, and the digital camera messed it, so no bug
Now has happened again and this is the error I saw. I am reasonably
sure I copied it down correctly:
X Error in flag:
X Error of failed request: BadAccess (attempt to access private resource
Major opcode of failed request 88 (X_FreeColors)
Serial number of failed request 51143184
Current serial number 51143189
xscreensaver: child pid 14421 (flag) exited abnormally (code -1)
It appears to be reasonably reproducible if you have about four days to
watch endless screensavers in hope of catching the wrong one. There are
two (!?) screensavers labelled 'Flag' in the screensaver capplet. I have
been running them alternately and watching out of the corner of my eye
for some hours and they now won't do it again. I bet they will as soon
as I put it on random again. Other guess:
Sits there for some time with a screensaver image in the centre of the
screen and the error message in yellow in the top left.
Then screen blanks completely. Hitting a key gets rid of the empty
screen and nothing bad happens. This is just a minor irritant I suppose.
This defect considered SHOULD-FIX for Fairfax gold-release.
What resolution & color depth are you running at?
closing - no response.