|
Bugzilla – Full Text Bug Listing |
| Summary: | KDE4 desktop (likely some RANDR tool) triggers DDC scan every 10 seconds | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Peter B <auxsvr> |
| Component: | KDE4 Workspace | Assignee: | Lubos Lunak <llunak> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | alinm.elena, eich, f.leerink, felix, jdelvare, mlatimer, monkey9, sndirsch, stefan.bruens, varkoly |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Xorg log
xorg configuration file testcase |
||
|
Description
Peter B
2008-09-19 09:37:16 UTC
Created attachment 240501 [details]
xorg configuration file
Which desktop are you using? Sounds like a RANDR tool which polls every 10 seconds. Verify by starting a failsafe *Xsession*. I'm using KDE4.1.1. You're right, in a failsafe Xsession the DDC scan appears only twice in Xorg.0.log. So this is most likely a desktop session problem. Some desktop process is querying the RandR extension every 10 seconds to find out if the connected displays have changed. As a result the Xserver will read out DDC which produces those messages in the log file. That is correct:
===
void RandrMonitorModule::poll()
{
// HACK: It seems that RRNotify/RRNotify_OutputChange event (i.e. detecting a newly
// plugged or unplugged monitor) does not work without polling some randr functionality.
int dummy;
XRRGetScreenSizeRange( QX11Info::display(), window, &dummy, &dummy, &dummy, &dummy );
}
===
I didn't expect polling of a RANDR function would have any other effect than making it tell the client about the change, when it fails to do so on its own. If you tell me how to get RRNotify_OutputChange about a monitor change without polling, I'll gladly remove the hack.
Created attachment 240580 [details]
testcase
A small testcase, in case that helps.
> If you tell me how to get RRNotify_OutputChange about a monitor change
> without polling, I'll gladly remove the hack.
AFAIK this won't be possible before RANDR 1.3 (which we won't have in time for openSUSE 11.1/SLE11), but Matthias knows more details here.
It's most likely that even RandR 1.3 won't have this feature. Also, most hardware isn't capable of creating interrupts on hotplug change. RandR 1.3 might have a less intrusive scanning operator, though. (In reply to comment #5 from Lubos Lunak) > I didn't expect polling of a RANDR function would have any other effect than > making it tell the client about the change, when it fails to do so on its own. > If you tell me how to get RRNotify_OutputChange about a monitor change without > polling, I'll gladly remove the hack. This is impossible ATM. Sorry. Sorry, I didn't read carefully and mixed this up with the less intrusive scanning operator of RANDR 1.3. I suggest to remove this hack. > --- KDE4 desktop (likely some RANDR tool) triggers DDC scan every 10 seconds
> +++ RANDR doesn't inform about newly plugged monitors
Sorry, but this is nothing you can expect to be implemented by us for SLE11. There are even upstream no plans to implement this. It's a also a hardware limitation, as Matthias outlined before. Please remove this hack. I don't think it's acceptable, that every 10 seconds you can't use your mouse and keyboard for 1-3 seconds.
It appears that things are a little more complicated than that. I tested xorg-x11-7.3-96.2 and xorg-x11-driver-video-7.3-138.5 (default opensuse 11) and every 10 seconds the line (**) RADEON(0): RADEONSaveScreen(2) is appended to Xorg.0.log, without any ill-effects that I'm aware of. It is possible to watch a video without any freezes, something that is impossible with the current Xorg. 11.0 has still the old non-RANDR 1.2 capable radeon driver. This old radeon driver won't be available on 11.1. Conclusion: All RANDR 1.2 capable drivers are affected by this issue. Among these are radeon, radeonhd, intel, nv(G80) and soon fglrx, nvidia. Major/P2 according to my comment #10. Removing the hack should be easy. I disabled the startup service "Detecting RANDR (monitor) changes" in the service manager and DDC scans stopped, so I'd say that a patch isn't necessary, adjusting the default setting seems to be enough. > Conclusion: All RANDR 1.2 capable drivers are affected by this issue.
This conclusion is wrong, how do you think the feature was developed? I was even thinking about having just 1 second as the polling time, and I built the feature around the assumption that detecting hardware changes works, which sucks :(.
Disabled polling.
*** Bug 437739 has been marked as a duplicate of this bug. *** *** Bug 431200 has been marked as a duplicate of this bug. *** *** Bug 438984 has been marked as a duplicate of this bug. *** *** Bug 439615 has been marked as a duplicate of this bug. *** Since the bug still exists with Beta4 (about 5 weeks after it has been closed as fixed) it makes perfectly sense to reopen this one and not closing it again as fixed before it has been fixed for real. *** Bug 441152 has been marked as a duplicate of this bug. *** Sorry, no idea how I could have repeatedly got distracted in the middle and ended up thinking it'd been done already. Now it's in KDE:KDE4:Factory:Desktop and waiting in /work/src/done/STABLE, honest :). Which package is this? Which changelog? Please, I want to know this! kdebase4-workspace ------------------------------------------------------------------- Mon Nov 3 22:27:07 CET 2008 - llunak@suse.cz - update from randr branch (bnc#427645) - update from kwin branch (sync with 4.1 branch) *** Bug 440965 has been marked as a duplicate of this bug. *** *** Bug 435941 has been marked as a duplicate of this bug. *** *** Bug 441531 has been marked as a duplicate of this bug. *** *** Bug 436143 has been marked as a duplicate of this bug. *** Is here any way to disable this in the system, so that I can use Beta4 KDE for testing or is installing a new package the only way ? @Karsten $ qdbus org.kde.kded /kded unloadModule randrmonitor solved it for me. Hello I have copied "Comment #37 of bug 436143 to bug 427645 since I was told that my bug was a duplicate of that one. I now want to add my last finding after a reinstall of openSUSE 11.1 beta4, but now installed from the DVD instead of the LiveCD. The problem does not show up now !! !! !! Regards, Frans ------- Comment #37 From Frans Leerink 2008-11-04 09:25:23 MST [reply] ------- Hello, I have also a very irritating flickering problem on my display. The screen flickers every 9-10 seconds and in my opinion it goes over the complete screen. But if I cover up the whole screen, except 1 square cm at one of the corners, I still see 2 flickerings, 9-10 seconds in between and that repeated every 50 seconds. The flickering looks like a darker line flashing downwards over a third of the screen height. I have a GEFORCE 8400 GS NVIDIA card Regards, Frans ------- Comment #38 From Stefan Dirsch 2008-11-04 09:34:23 MST [reply] ------- Frank, Nkoli, your issues might very well be another duplicate of Bug #427645. OS: Linux 2.6.27.5-1-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4.6 (x86_64) KDE: 4.1.3 (KDE 4.1.3) "release 1.3" i am glad to say that i don't have to:$ qdbus org.kde.kded /kded unloadModule randrmonitor , every time i boot up :)) Seems to be fixed.. *** Bug 443502 has been marked as a duplicate of this bug. *** *** Bug 441031 has been marked as a duplicate of this bug. *** |