Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions).

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Created attachment 368158 [details]
Full list of installed RPMs

Performed full update a few hours ago. The problem is still present: it is virtually impossible to log in.
The related driver package is xorg-x11-drv-intel-2.9.1-1.fc12.i686.

I'm also attaching full list of installed packages.

Would adding

i915.powersave=0

string to kernel command line (in /etc/grub.conf) help?

Created attachment 368191 [details]
Modified grub.conf

/etc/grub.conf points to /boot/grug/grub.conf, so I edited the latter.
Unfortunately it did not worked. Message like
'Unknown parameter: "i915.powersave=0" ignoring'
was shown soon after grub menu has gone. Then boot process continued as with default grub settings. I was not able to log in.

I'm attaching my modified grub.conf. The modified entry is the third one.

Here is the exact message shown soon after grub menu is gone:
Unknown boot option: "i915.powersave=0", ignoring

That ignoring message is harmless, however, if it haven't helped, we have a problem.

Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Do you need this info with "i915.powersave=0" or not?

Doesn't matter.

Here are the results.
1) I've run Fedora with default grub entry.
2) There are no /etc/X11/xorg.conf
3) I've waited about 10 minutes after entering credentials in login screen. But Fedora did not logged me in. So, I've used second virtual console (Alt+Ctrl+F2) to log in. The dmesg output an X server log files (attached below) were collected from that console (because I don't know the other approach to obtain them when graphical log in fails).

Created attachment 368235 [details]
dmesg output

Created attachment 368236 [details]
Xorg.0.log

Created attachment 368237 [details]
Xorg.0.log.old

Created attachment 368240 [details]
Xorg.9.log

This is the last one. There were 3 X server log files.

(In reply to comment #9)
> Here are the results.
> 1) I've run Fedora with default grub entry.
> 2) There are no /etc/X11/xorg.conf
> 3) I've waited about 10 minutes after entering credentials in login screen. But
> Fedora did not logged me in. So, I've used second virtual console (Alt+Ctrl+F2)
> to log in. The dmesg output an X server log files (attached below) were
> collected from that console (because I don't know the other approach to obtain
> them when graphical log in fails).  

Thanks a lot, that's absolutely perfect.

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

I'm use Msi Wind U90x. FC12 x32.

Any additional info about resolving this bug? I'm yum upgrade FC12 to latest package with enabled update and update-testing repo. No success, flickering at login screen not gone (to break flickering it i'm use Alt+F1 sequence).


I'm think https://bugs.launchpad.net/fedora/+bug/415023?comments=all it's launchpad info on this bug, and https://bugzilla.gnome.org/show_bug.cgi?id=601410 is gnome.

See also bug 509577 (also for MSI WIND)

suspicious to be duplicates: bug 509577 and bug 544749

(In reply to comment #18)
> suspicious to be duplicates: bug 509577 and bug 544749  

sorry, forgot about the latter, that's ATI

this flickring is because of loops seting back and forth brigitness 

https://bugs.launchpad.net/fedora/+bug/415023

comment 80 is very clear

I often see this flickering when I wake my ThinkPad SL500 laptop from suspend. During the flickering, many gcm-apply processes are running and CPU use is high. When these processes stop, the flickering stops and CPU use drops.

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

I'm still experiencing this problem with Fedora 13.

I am experiencing the same issue in Fedora 14. Extensive number of gcm-apply processes is running.

00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
Notebook HP EliteBook6930p

Screen flickers with cca 30% chance when:
- starting gnome-greeter (login screen)
- directly after loging in
- after screensaver blanks and un-blanks the screen
- when starting gcm-prefs
- when changing color profiles from one to another in gcm-prefs

Workaround is to unistall gnome-color-manager.

Michal Ambroz

I see the same problem gcm-apply going nuts problem on my HP laptop after installing Fedora 14 x86_64.  

yum erase gnome-color-manager
 
Fixed the problem on my laptop with its Intel GPU.  Could the problem be related to the unclaimed display controller where an external monitor can be connected?

product: HP Compaq 6730b (NA373UC#ABA) (NA373UC#ABA)
vendor: Hewlett-Packard
version: F.16
serial: xxx
width: 64 bits
capabilities:
	SMBIOS version 2.4,
	DMI version 2.4,
	64-bit processes,
	32-bit processes
configuration:
	boot: normal
	chassis: notebook
	family: 103C_5336AN
	sku: NA373UC#ABA


VGA compatible controller
/0/100/2
product: Mobile 4 Series Chipset Integrated Graphics Controller [8086:2A42]
vendor: Intel Corporation [8086]
bus info: pci@0000:00:02.0
version: 07
width: 64 bits
clock: 33MHz
capabilities:
	Message Signalled Interrupts,
	Power Management,
	vga_controller,
	bus mastering,
	PCI capabilities listing,
	extension ROM
configuration:
	driver: i915
	latency: 0
resources:
	irq: 48
	memory: d0000000-d03fffff
	memory: c0000000-cfffffff
	ioport: 60f0(size=8)


Display controller
/0/100/2.1


product: Mobile 4 Series Chipset Integrated Graphics Controller [8086:2A43]
vendor: Intel Corporation [8086]
bus info: pci@0000:00:02.1
version: 07
width: 64 bits
clock: 33MHz
capabilities:
	Power Management,
	bus mastering,
	PCI capabilities listing
configuration:
	latency: 0
resources:
	memory: d0400000-d04fffff
this device hasn't been claimed

I am yet another person getting this screen flicker running fedora 14 with many gcm-applys starting sometimes after exiting the screen saver. I tried uninstalling gnome-color-manager, but that leaves me with out a manger and on bootup I am simply left at an endless screen test. This is happening on a HP Elitebook 6930p. I have to use intel_iommu=off at the boot options to not have any problems with the graphics. That boot option works sometimes and sometimes it doesn't. Under Fedora 13 it worked most of the time.

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