Description of problem: when resuming from suspend, the desktop with all its contents before suspending are visible for a short moment before the screen goes blank and one is able to enter his/her password to the session lock window. this poses a slight security risk as there is enough time to read parts of the content. the kernel is 2.6.35.11, and the display adapter is Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 215a which is using kernel module i915. KDE version is 4.5.5.
bugs.kde.org is probably the best place for this.
Seems to happen also in Gnome: https://bugzilla.redhat.com/show_bug.cgi?id=713640 Also happening on F16
yes it seems like something similar popped up with gnome. :'( a further extended list of similar bugs: https://bugzilla.redhat.com/show_bug.cgi?id=677345 https://bugzilla.redhat.com/show_bug.cgi?id=682132 https://bugzilla.redhat.com/show_bug.cgi?id=713640 https://bugzilla.redhat.com/show_bug.cgi?id=714784 https://bugzilla.redhat.com/show_bug.cgi?id=748560 https://bugzilla.redhat.com/show_bug.cgi?id=761074 https://bugzilla.redhat.com/show_bug.cgi?id=697199
Here might be the upstream bug ? https://bugs.kde.org/show_bug.cgi?id=246623 I am experiencing this in F16 KDE too. Recently thou, this has "evolved" here : now, the whole desktop is not visible any more, but instead, the list of current tasks are shown, covering the entire screen with some gray background (i.e. "user@host - Konsole" and "Whatever filename - Kate", etc.). So, it shows yet another strange view of the taskbar. This is 100% reproducible so far, every time I come back from suspend which I use at least once a day these days. Note: maybe this coincides with my switch to smooth-taskbar, I didn't perform any further check or test on this issue.
Graphics card/driver? I've seen this before and it's most likely a graphics driver bug
Fair enough, noVideo + proprietary driver distributed by fusion here :) I will *not* test nouveau again with F16 on this hardware. Nouveau was an absolute no-go for me with first series of F16 stock kernels and mods, hence the switch at the time. However I will, of course, give it another go while moving to F17... or F18, and update the present report accordingly. Please do not close. Thanks. (Asus V1S laptop) # lspci | grep VGA 01:00.0 VGA compatible controller: nVidia Corporation G84 [GeForce 8600M GT] (rev a1) # yum list installed kmod-nvidia kmod-nvidia.x86_64 1:295.59-1.fc16.1 @rpmfusion-nonfree-updates
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
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.