Bug 49136

Summary: 'flag' screensaver dies with XError error messages -- sometimes.
Product: [Retired] Red Hat Linux Reporter: Telsa Gwynne <hobbit>
Component: xscreensaverAssignee: Bill Nottingham <notting>
Status: CLOSED WORKSFORME QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 7.3CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-07-16 19:09:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Telsa Gwynne 2001-07-15 10:17:14 UTC
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
report.

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
denied)
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)

How Reproducible:

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:

Actual Results:

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.

Comment 1 Glen Foster 2001-07-16 18:55:34 UTC
This defect considered SHOULD-FIX for Fairfax gold-release.

Comment 2 Bill Nottingham 2001-07-16 19:08:59 UTC
What resolution & color depth are you running at?

Comment 3 Bill Nottingham 2002-01-24 05:54:58 UTC
closing - no response.