Bug 134578

Summary:	kde 3.5 screensavers partly broken
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Dennis Lubert <plasmahh>
Component:	KDE	Assignee:	Lubos Lunak <llunak>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	xdpyinfo from specified date

Description Dennis Lubert 2005-11-20 14:31:17 UTC

Hi,

I have just upgraded to supplement repositories kde 3.5rc1 and noticed that screensavers are broken. When going through the screensavers and testing them, at one point they all seem to stop to work (with a exception of a few ones). When I then restart kcontrol, they work again until one them breaks it all again. Then I get one of those messages on konsole:

X error in superquadrics:
X Error of failed request:  BadColor (invalid Colormap parameter)
  Major opcode of failed request:  92 (X_LookupColor)
  Resource id in failed request:  0x0
  Serial number of failed request:  32
  Current serial number in output stream:  32
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  8
  Minor opcode:  0
  Resource id:  0x3000775
======================
X error in gltext:
X Error of failed request:  BadColor (invalid Colormap parameter)
  Major opcode of failed request:  92 (X_LookupColor)
  Resource id in failed request:  0x0
  Serial number of failed request:  32
  Current serial number in output stream:  32
======================
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  8
  Minor opcode:  0
  Resource id:  0x3000775

Comment 1 Stephan Kulow 2005-11-30 13:46:22 UTC

pretty bad and I'm afraid it's showing some other problem

Comment 2 Lubos Lunak 2005-11-30 13:52:51 UTC

Please attach(!) your output from 'xdpyinfo'.

Comment 3 Dennis Lubert 2005-11-30 14:08:28 UTC

Created attachment 59194 [details]
xdpyinfo from specified date

attachment created

Comment 4 Lubos Lunak 2005-11-30 18:19:07 UTC

It happens only when testing the screensavers, they still otherwise work normally.

Comment 5 Dennis Lubert 2005-12-01 02:57:25 UTC

It does not always, this is why I had originally found the bug. Directly after upgrade, I tried to lock the screen and got a blank screen instead of the screensaver. Therefore I tried to test and figured that it gives the above mentioned errors. It works always only when you do the following:
- Start a fresh controlcenter
- Check the screensaver you want and hit ok
- startup the lock e.g. by ctrl+alt+l (if activated)

In other cases it might work sometimes, somtimes not. It does never work if:
- Start the controlcenter
- klick and test screensavers until it fails
- save the last failing screensaver
- startup e.g. via ctrl+alt+l (if activated)

then I get the same blank screen always. Seems like something is persistent during this. It then works well when starting up the controlcenter, just testing the same screensaver and saving. Seems really weird to me.

Comment 6 Lubos Lunak 2005-12-06 15:41:47 UTC

Fixed for KDE3.5.1.