Summary: | Screensaver 'molecule' is flickering | ||
---|---|---|---|
Product: | [Unmaintained] kscreensaver | Reporter: | Mathias Heier <privat> |
Component: | kxsrun | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ana, Pradeep.Sadanapalli |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Attached is my xorg.conf for the Radeon 8500 LE graphics card. |
Description
Mathias Heier
2003-05-16 18:56:37 UTC
*** Bug 59958 has been marked as a duplicate of this bug. *** This seems to be related to DRI; if I disable DRI then I do not get the problem. Actually, this bug applies to all of the OpenGL screensavers not just "molecule." Also, it also happens when the screensaver is started normally because of an activity timeout or started via the "test" button in the control center. The same screensavers work fine in GNOME or directly from xscreensaver. This bug is still present in KDE 3.2. For the record, it my graphics card is a Radeon: OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI Radeon 20020611 AGP 4x x86/MMX/SSE TCL OpenGL version string: 1.2 Mesa 4.0.4 Strangely, it reminds me of a double-buffering issue -- that is, it looks like it isn't double buffered. Just using kde 3.4 from kubuntu and this problem persists on xscreensaver and rss screensavers enabled via the KDE desktop configuration. I am running xorg 6.8.2 radeon drivers with dri enabled. My video card is a radeon mobility 9200. Using the ATI fglrx drivers does not flicker the screensavers. I think this is actually related to the way KDE specifies the VisualID resource. I'm guessing KDE sets this to a generic default (default or any, not sure) when it should be specified as "GL" for OpenGL screensavers. Adding a tab that allows you to specify the visual used (and modify the command line arguements) ala xscreensaver-demo's advanced tab would be a step in the right direction. Why this doesn't exist already is beyond me. Ah, I forgot -- I'm running FreeBSD 5.4 (Radeon 9100, XOrg 6.8.2, DRI, radeon driver) and seeing the same thing, so it doesn't appear to be platform dependant. I am having the same problem with OpenGL screensavers running following system: - Kubuntu Breezy Badger with KDE 3.5.1 - Graphics card: Radeon 8500 LE - Opensource Radeon drivers that come with Xorg 6.8.2 Interestingly, whenever I start the screensaver manually via the test button in the Configure - KDesktop Dialog, the screensavers don't flicker anymore. It happens only when they are automatically activated after a certain time span as specified in the KDestop Dialog. Created attachment 15282 [details]
Attached is my xorg.conf for the Radeon 8500 LE graphics card.
Attached is my xorg.conf for the Radeon 8500 LE graphics card. As mentioned
before, I am using KDE 3.5.1 under Kubuntu Breezy Badger and the SMP Kernel
2.6.12-10-686-smp as provided by Kubuntu.
As I experienced crashes when working on the desktop, I deactivated rendering acceleration for my Radeon 8500 LE graphics card. There were no more crashes and in addition the flickering of the automatically activated OpenGl screensavers disappeared. Probably the flickering was caused by buggy Radeon drivers and appeared when KDE was already using rendering acceleration before the screensavers kicked in. Here the relevant sections of my new xorg.conf: Section "Device" Identifier "ATI Technologies, Inc. Radeon 8500 (R200 QL)" Driver "radeon" BusID "PCI:1:0:0" Option "AGPMode" "4" #Option "AGPSize" "64" # default: 8 #Option "RingSize" "8" #Option "BufferSize" "2" Option "EnablePageFlip" "true" Option "EnableDepthMoves" "true" #Option "RenderAccel" "true" #Option "AGPFastWrite" "true" EndSection #Section "Extensions" #Option "Composite" "Enable" #Option "RENDER" "Enable" #EndSection works for me. there have been some visual selection related fixes in the past, so i assume they might have fixed this issue. |