Hide Forgot
Created attachment 564123 [details] messages, f17 alpha tc2 kde livecd Description of problem: First, it is the same "Bug 732513" but tested with F17 Alpha TC KDE LiveCD. While on battery, if i put the laptop (Asus Ul80vt) to sleep (KDE/Leave/Sleep), it does come back black.. * If the same procedure (KDE/Leave/Sleep) is performed while the AC Power is connected, there is no problem. Suspend/Resume works. * If the same procedure (KDE/Leave/Sleep) is performed while the AC Power is connected, and the AC power is removed BEFORE resume, then there is no problem also. Suspend in AC / Resume in BAT works. So, it still is not possible to suspend this laptop and expect it to resume 100% of the time. Version-Release number of selected component (if applicable): F17 Alpha TC2 KDE LiveCD xorg-x11-drv-nouveau-0.0.16-34.20110720gitb806e3f.fc17.x86_64 kde-workspace-4.8.0-7.fc17.x86_64 kde-workspace-libs-4.8.0-7.fc17.x86_64 mesa-dri-filesystem-8.0-1.fc17.x86_64 mesa-libGL-8.0-1.fc17.x86_64 mesa-libGLU-8.0-1.fc17.x86_64 mesa-dri-drivers-8.0-1.fc17.x86_64 Kernel: 3.3.0-0.rc3.git5.1.fc17.x86_64 How reproducible: Allways Steps to Reproduce: 1. remove ac power cord 2. suspend (KDE > sleep) 3. push the power button to resume, black screen Actual results: a non technical user will not be able to wake the laptop from resume (not to mention that the X server needs to be killed in order to regain control) Expected results: 100 % resume rate (or at least 99.9999% :-) ) Additional info: VGA compatible controller [0300]: nVidia Corporation GT218 [GeForce G210M] [10de:0a74] (rev a2) The laptop has two videocards, intel (which i disabled by setting the sata controller in IDE mode {yeap. ridiculous but...}, so only the nVIDIA card is active.
Created attachment 564124 [details] lspci asus ul80vt
Created attachment 564125 [details] pm-suspend log asus ul80vt
Created attachment 564126 [details] Xorg.0.log.old asus ul80vt
Created attachment 564127 [details] Xorg.0.log asus ul80vt
Created attachment 564128 [details] dmesg
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.