xorg does not properly zero the screen on init. For a dozen of seconds, while gdm starts up, the content of the screen as it was before last xorg shut down is displayed If the system didn't shut down cleanly, or if it was shut down via a /sbin/init 6 in a term (because gnome3 people decided it was smart to remove the reboot shortcut even though people use it all the time), that means whole pages of private text that may belong to a different user are clearly visible (more than long enough to take a picture of them) $ rpm -qa xorg*|sort xorg-x11-drv-acecad-1.5.0-1.fc16.x86_64 xorg-x11-drv-apm-1.2.3-7.fc16.x86_64 xorg-x11-drv-ast-0.91.10-6.fc16.x86_64 xorg-x11-drv-ati-6.14.1-1.20110504gita6d2dba6.fc16.x86_64 xorg-x11-drv-cirrus-1.3.2-9.fc16.x86_64 xorg-x11-drv-dummy-0.3.4-6.fc16.x86_64 xorg-x11-drv-evdev-2.6.99-1.20110601giteaf202531.fc16.x86_64 xorg-x11-drv-fbdev-0.4.2-1.fc16.x86_64 xorg-x11-drv-glint-1.2.5-1.fc16.x86_64 xorg-x11-drv-hyperpen-1.4.1-1.fc16.x86_64 xorg-x11-drv-i128-1.3.4-8.fc16.x86_64 xorg-x11-drv-i740-1.3.2-8.fc16.x86_64 xorg-x11-drv-intel-2.15.0-5.fc15.x86_64 xorg-x11-drv-mach64-6.9.0-1.fc16.x86_64 xorg-x11-drv-mga-1.4.13-7.fc16.x86_64 xorg-x11-drv-mouse-1.7.1-1.fc16.x86_64 xorg-x11-drv-nouveau-0.0.16-25.20110324git8378443.fc16.x86_64 xorg-x11-drv-nv-2.1.18-7.fc16.x86_64 xorg-x11-drv-openchrome-0.2.904-14.fc16.x86_64 xorg-x11-drv-r128-6.8.1-10.fc16.x86_64 xorg-x11-drv-rendition-4.2.4-6.fc16.x86_64 xorg-x11-drv-s3virge-1.10.4-8.fc16.x86_64 xorg-x11-drv-savage-2.3.2-4.fc16.x86_64 xorg-x11-drv-sis-0.10.3-6.fc16.x86_64 xorg-x11-drv-sisusb-0.9.4-6.fc16.x86_64 xorg-x11-drv-synaptics-1.4.1-1.fc16.x86_64 xorg-x11-drv-tdfx-1.4.3-8.fc16.x86_64 xorg-x11-drv-trident-1.3.4-6.fc16.x86_64 xorg-x11-drv-v4l-0.2.0-13.fc16.x86_64 xorg-x11-drv-vesa-2.3.0-8.fc16.x86_64 xorg-x11-drv-vmmouse-12.7.0-1.fc16.x86_64 xorg-x11-drv-vmware-11.0.3-5.fc16.x86_64 xorg-x11-drv-void-1.4.0-1.fc16.x86_64 xorg-x11-drv-voodoo-1.2.4-6.fc16.x86_64 xorg-x11-drv-wacom-0.11.99-3.20110527.fc16.x86_64 xorg-x11-font-utils-7.5-6.fc15.x86_64 xorg-x11-server-common-1.10.99.1-9.20110510.fc17.x86_64 xorg-x11-server-utils-7.5-5.fc16.x86_64 xorg-x11-server-Xorg-1.10.99.1-9.20110510.fc17.x86_64 xorg-x11-util-macros-1.15.0-1.fc16.noarch xorg-x11-utils-7.5-2.fc15.x86_64 xorg-x11-xauth-1.0.6-1.fc16.x86_64 xorg-x11-xinit-1.3.1-1.fc16.x86_64 xorg-x11-xkb-utils-7.5-5.fc16.x86_64
Yes.
That's sort of a property of the driver too. Which one are you using?
Should be ati 01:00.1 Audio device: ATI Technologies Inc Device aa98 Subsystem: PC Partner Limited Device aa98 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin B routed to IRQ 50 Region 0: Memory at eb020000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee0300c Data: 41c1 Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Kernel driver in use: snd_hda_intel Kernel modules: snd-hda-intel
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.