Bug 754580 - color-plugin failed to get edid
Summary: color-plugin failed to get edid
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 16
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-16 21:39 UTC by Dmitry Burstein
Modified: 2013-02-13 11:52 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 11:52:38 UTC
Type: ---


Attachments (Terms of Use)

Description Dmitry Burstein 2011-11-16 21:39:40 UTC
Description of problem:
System Settings -> Color panel doesn't list my monitor information, saying "no devices supporting color management detected"

Version-Release number of selected component (if applicable):
gnome-settings-daemon-3.2.1-4.fc16.x86_64

How reproducible:
every time - with both the nvidia and nouveau drivers

Steps to Reproduce:
1.System Settings
2.Color
3."no devices..."
  
Additional info:
.xsession-errors file shows the following:
(gnome-settings-daemon:1858): color-plugin-WARNING **: failed to get edid: unable to get EDID for output

My monitor is DELL U2410, and the color management worked perfectly in F15.

The Xorg.0.log is full of EDID data received by the drivers.

May be it's a kind of permission issue:
[root@home ~]# monitor-get-edid
mmap /dev/mem: Permission denied
[root@home ~]# ll -Z /dev/mem
crw-r-----. root kmem system_u:object_r:memory_device_t:s0 /dev/mem

Comment 1 Need Real Name 2011-11-25 08:03:13 UTC
Accidently hit on this bugreport while debugging an unrelated kernel
crash on modprobe nouveau modeset=1
The permission issue in this case can be solved like this:

[root@linux ~]# ll -Z /dev/mem
crw-r-----. root kmem system_u:object_r:memory_device_t:s0 /dev/mem

[root@linux ~]# monitor-edid --v
probing EDID using VBE (port 0)
mmap /dev/mem: Permission denied
VBE: could not initialize LRMI
VBE info call failed, skipping all ports

[root@linux ~]# tail -5 /var/log/messages | grep setroubleshoot
Nov 25 08:26:03 linux setroubleshoot: SELinux is preventing /usr/bin/dosemu.bin from mmap_zero access on the memprotect Unknown. For complete SELinux messages. run sealert -l 42ab0559-1bc8-4b52-99b2-b42d4a846516

sealert -l 42ab0559-1bc8-4b52-99b2-b42d4a846516
..
SELinux is preventing /usr/bin/dosemu.bin from mmap_zero access on the memprotect Unknown.
..

If you want to control the ability to mmap a low area of the address space, as configured by /proc/sys/kernel/mmap_min_addr.
Then you must tell SELinux about this by enabling the 'mmap_low_allowed' boolean.
Do
setsebool -P mmap_low_allowed 1


[root@linux ~]# setsebool -P mmap_low_allowed 1

and now  monitor-edid works
You should probably revert the boolean after finishing your testing 
as the mmap low memory in the kernel is a security risk.

[root@linux ~]# setsebool -P mmap_low_allowed 0

Good luck with solving your original problem.
For me personally ever since enabling SELinux half of the time something
doesn't work as expected there is an SELinux warning in the log.

Comment 2 Fedora End Of Life 2013-01-16 12:04:03 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-13 11:52:40 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.