Description of problem: I have installed a fresh F14 installation from DVD+network to a HP 6730b laptop. Then I have tried to log in. The performance was very sluggish, and the display was redrawn very often, resulting in blinks every second or two. I have compared the running processes to my other system (F14 upgraded from F12), and found that the laptop has several instances of /usr/bin/gcm-apply process running. After removing gnome-color-manager package via rpm -e, the display stopped blinking and the performance became normal. Version-Release number of selected component (if applicable): How reproducible: 100 % (I have tried to install F14 twice - once from DVD and later yum update, the second time using DVD+network to get an up-to-date system) Steps to Reproduce: 1. Install fresh F14 on HP 6730b 2. Log in as user Actual results: blinking display (even during gdm prompt), sloooow response to keyboard input. Expected results: steady display, acceptable response time. Additional info: lspci says the following about the graphics card: 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 30dd Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at d8000000 (64-bit, non-prefetchable) [size=4M] Memory at c0000000 (64-bit, prefetchable) [size=256M] I/O ports at 60f0 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Subsystem: Hewlett-Packard Company Device 30dd Flags: bus master, fast devsel, latency 0 Memory at d8400000 (64-bit, non-prefetchable) [size=1M] Capabilities: <access denied>
If you run "/usr/bin/gcm-apply --verbose" what is printed out? Thanks.
Had the same problem on a Dell E5500, F14 all updates as of yesterday. F13 did not have this issue. Removing gnome-color-manager fixed the issue. [Joe@bart ~]$ /usr/bin/gcm-apply --verbose TI:12:37:34.264580 FI:egg-debug.c FN:egg_debug_post_parse_hook,436 - Verbose debugging 1 (on console 1) TI:12:37:34.265646 FI:gcm-client.c FN:gcm_client_set_loading,117 - loading: 1 TI:12:37:34.265707 FI:gcm-client.c FN:gcm_client_add_connected,1023 - adding devices of type XRandR TI:12:37:35.229040 FI:gcm-edid.c FN:gcm_edid_parse,309 - PNPID: LPL TI:12:37:35.229084 FI:gcm-edid.c FN:gcm_edid_parse,337 - gamma is reported as 2.200000 TI:12:37:35.229126 FI:gcm-edid.c FN:gcm_edid_parse,343 - red x=0.599609,y=0.347656 TI:12:37:35.229147 FI:gcm-edid.c FN:gcm_edid_parse,348 - green x=0.325195,y=0.553711 TI:12:37:35.229166 FI:gcm-edid.c FN:gcm_edid_parse,353 - blue x=0.154297,y=0.144531 TI:12:37:35.229186 FI:gcm-edid.c FN:gcm_edid_parse,358 - white x=0.313477,y=0.329102 TI:12:37:35.229212 FI:gcm-edid.c FN:gcm_edid_parse,409 - monitor name: (null) TI:12:37:35.229229 FI:gcm-edid.c FN:gcm_edid_parse,410 - serial number: (null) TI:12:37:35.229246 FI:gcm-edid.c FN:gcm_edid_parse,411 - ascii string: X397H�154WX5 TI:12:37:35.229274 FI:gcm-tables.c FN:gcm_tables_get_pnp_id,94 - loading: /usr/share/hwdata/pnp.ids TI:12:37:35.230719 FI:gcm-device-xrandr.c FN:gcm_device_xrandr_set_from_output,247 - asking to add xrandr_lg_philips_x397h_154wx5 TI:12:37:35.230931 FI:gcm-client.c FN:gcm_client_xrandr_add,640 - emit: added xrandr_lg_philips_x397h_154wx5 to device list TI:12:37:35.230954 FI:gcm-client.c FN:gcm_client_xrandr_add,599 - VGA1 is not connected TI:12:37:35.230971 FI:gcm-client.c FN:gcm_client_xrandr_add,599 - HDMI1 is not connected TI:12:37:35.230986 FI:gcm-client.c FN:gcm_client_xrandr_add,599 - DP1 is not connected TI:12:37:35.231002 FI:gcm-client.c FN:gcm_client_xrandr_add,599 - HDMI2 is not connected TI:12:37:35.231018 FI:gcm-client.c FN:gcm_client_xrandr_add,599 - DP2 is not connected TI:12:37:35.231033 FI:gcm-client.c FN:gcm_client_xrandr_add,599 - DP3 is not connected TI:12:37:35.231049 FI:gcm-client.c FN:gcm_client_xrandr_add,599 - TV1 is not connected TI:12:37:35.231067 FI:gcm-client.c FN:gcm_client_set_loading,117 - loading: 0 TI:12:37:35.231087 FI:gcm-apply.c FN:main,91 - setting profiles on device: xrandr_lg_philips_x397h_154wx5 TI:12:37:35.526019 FI:gcm-clut.c FN:gcm_clut_get_array,179 - min=0.000000,max=1.000000 TI:12:37:35.526059 FI:gcm-clut.c FN:gcm_clut_get_array,185 - falling back to dummy gamma TI:12:37:35.953797 FI:gcm-xserver.c FN:gcm_xserver_remove_output_profile,634 - found LVDS1, removing atom TI:12:37:36.377892 FI:gcm-xserver.c FN:gcm_xserver_remove_root_window_profile,396 - removing root window ICC profile atom TI:12:37:36.378013 FI:gcm-xserver.c FN:gcm_xserver_remove_protocol_version,289 - removing root window ICC profile atom
Does this still happen in F15 or F16?
I cannot reproduce it under F15, so you can probably close this bug after F14 EOL.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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