Xorg.0.log keeps filling up with DDC information

Bug #299492 reported by Holger Schletz
52
This bug affects 4 people
Affects Status Importance Assigned to Milestone
kdebase-workspace (Ubuntu)
Fix Released
Medium
Unassigned
xserver-xorg-video-intel (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

On my fresh install of Kubuntu 8.10, this stuff gets logged to Xorg.0.log every 10 seconds:

(II) intel(0): EDID vendor "FUS", prod id 1362
(II) intel(0): Using hsync ranges from config file
(II) intel(0): Using vrefresh ranges from config file
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
(II) intel(0): Modeline "640x480"x0.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
(II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
(II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) intel(0): Modeline "1024x768"x0.0 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz)
(II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
(II) intel(0): Modeline "1280x1024"x60.0 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -hsync +vsync (63.6 kHz)
(II) intel(0): EDID vendor "FUS", prod id 1362

The amount of approximately 470 kB per hour is not a big issue on most desktop systems which don't run 24/7. However, the clutter makes tracing the logfile for different problems more annoying.

The affected system is a Gigabyte EG45M-DS2H (Intel G45 chipset, "intel" driver). My monitor is a Fujitsu-Siemens P19-2. Connecting via DVI or VGA doesn't make a difference. This problem may be driver related because another system with the "nv" driver didn't show this behavior.

I have attached my Xorg.0.log.

Revision history for this message
Holger Schletz (holger-schletz) wrote :
Revision history for this message
Holger Schletz (holger-schletz) wrote :
Revision history for this message
Geir Ove Myhr (gomyhr) wrote :

I have the same problem on a Thinkpad X61 Tablet, Intel 965GM chipset.

Geir Ove Myhr (gomyhr)
Changed in xserver-xorg-video-intel:
status: New → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

Sounds like something in KDE is polling xrandr calls. Probably nothing we can do about this from the X side.

Changed in xserver-xorg-video-intel:
status: Confirmed → Won't Fix
Revision history for this message
eugenez (eugene-zvyagintsev) wrote :

I have the same problem on a desktop computer with GA-G31M-S2L motherboard (Intel G31 chipset) and Kubuntu 8.10 with KDE 4.1.3

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

This is probably caused by the randr detection daemon patch that our KDE packages have. (Used to detect monitor additions, etc)
We will be able to remove this patch in KDE 4.2 since upstream has introduced a more proper way of managing multiple screens.

Changed in kdebase:
importance: Undecided → Medium
milestone: none → ubuntu-9.04
status: New → Fix Committed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

KDE 4.2 has been released to Kubuntu Jaunty. Packages for Intrepid are available for Kubuntu Intrepid via the kubuntu-experimental personal package archive for those interested in testing/using them.

Changed in kdebase-workspace:
status: Fix Committed → Fix Released
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

I should clarify, KDE 4.2 beta1 has been released.

Revision history for this message
Holger Schletz (holger-schletz) wrote :

I upgraded to KDE 4.2 from the kubuntu-experimental PPA and can confirm that the problem is fixed there.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.