Bug 266180

Summary:	TV-out blinks every 30 seconds
Product:	[I don't know] kde	Reporter:	Perles <perles>
Component:	dualhead	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version:	4.6
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:

Description Perles 2011-02-13 05:36:18 UTC

Version:           4.6 (using KDE 4.6.0) 
OS:                Linux

I noticed that TV-out keeps blinking every 30 seconds when using KDE. Interesting points are that we need to reboot in order to stop TV blink. Even logging off KDE killing all KDE process is not enough. TV keeps blinking even when is not in use, just need to be connected through S-video.
This doesn't affect all KDE software but I could not pinpoint only one. 

The test I performed was to boot with latest kernel 2.6.37, KMS ATI driver, log using KDM into fluxbox, connect S-Video to TV, use xrandr to turn TV out on. TV keeps quite and usable. If I turn on konsole and krandrtray through terminal I still have TV-out stable. When I turn on knotify4 it starts to blink every 30 secs. Killing all KDE process doesn't help. Killing XServer doesn't help either. Only reboot fixes it.
However, if I delete knotify4 from my system and then reboot my Linux and log into KDE my TV starts to blink. 

Reproducible: Always

Steps to Reproduce:
Login into KDE 4.6

Actual Results:  
TV through S-Video keeps blinking every 30 seconds

Expected Results:  
Stable TV-out

This was not present in version 4.5. 
This bug is some component that knotify4 and some other softwares but is not present in konsole neither krandrtray.

Comment 1 Andrew Crouthamel 2018-11-05 03:07:16 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 2 Perles 2018-11-08 01:28:48 UTC

I marked as resolved. I found out later that was due to the timer frequency set in the kernel at the compiling time.

Comment 3 Christoph Feck 2018-11-08 02:09:06 UTC

Thanks for the update!