Bug 158296 - short "black screens" while working.
Summary: short "black screens" while working.
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.0.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-23 22:43 UTC by Markus Grob
Modified: 2008-05-21 16:56 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Grob 2008-02-23 22:43:24 UTC 
Version:           4.0.1 (using KDE 4.0.1)
Installed from:    SuSE RPMs
OS:                Linux

While working with kde, some times, the screen goes short to black (1/2 sek.) and comes back, like he tries to go to powersave or activate the screensaver.
I couldn't say why, but it cames while I'm writing or moving the mouse.
Not shure, if it's the design or something else, but KDE3 does without a problem.
Comment 1 A. Spehr 2008-05-15 04:29:06 UTC 
Did you do any changes just before it started happening? This could be a video driver problem, maybe. Or try upgrading and see if that helps, a lot of stuff has been fixed over the past several releases.
Comment 2 A. Spehr 2008-05-15 04:29:38 UTC 
Did you do any changes just before it started happening? This could be a video driver problem, maybe. Or try upgrading and see if that helps, a lot of stuff has been fixed over the past several releases.
Comment 3 George Goldberg 2008-05-15 04:32:48 UTC 
Actually, I used to have this problem quite often on Mandriva using trunk too. It only happened with composite on. I have the nvidia drivers (yes, they are the latest ones :)). However I haven't seen this issue much lately (trunk in the last month or so), but I'll definitely report back here if I see it again.
Comment 4 Markus Grob 2008-05-16 22:37:32 UTC 
I have installed 4.0.4 now, but I think, I haven't seen it since 4.0.2.

For me, it's working now and we can close the bug.
Comment 5 Lubos Lunak 2008-05-21 16:56:36 UTC 
Closing as per comment #4.