Created attachment 661507 [details] 3.7-rc8 kernel Description of problem: I'm using F18 x86_64 with KDE. When I use the rawhide kernel (3.7.0-rc8) and I do a graphical login, my workspace freezes for few seconds, then I heard the login sound and all goes well. This doesn't happen with F18 current kernel (3.6.9). Version-Release number of selected component (if applicable): 3.7.0-rc8 How reproducible: Steps to Reproduce: 1. KDE graphical login Actual results: Partial temporal limited freeze Expected results: No freeze Additional info: In dmesg I've many ACPI errors, with both kernerls. I use acpi_backlight=vendor to make my hotkeys working for my backlight (this is a F13 regression). When KDE loads with this option, I get black screen for a 1/10 of second. If I use the new kernel, when I see the workspace, it appears the brightness bar (but I don't press anything to show the brightness). I don't know if those APCI problem could be related to this freeze.
Created attachment 661508 [details] 3.6 kernel
It could be related with: https://bugzilla.redhat.com/show_bug.cgi?id=595885 With other kernels, there's no problems (Windows 7 and DragonFly BSD 3.2.2 tested).
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
Is this still an issue with the 3.9 kernels in F19?
It disappeared with 3.8 on F18, but there's some ACPI errors persisting regarding the brightness management (this is a regression).
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.