Summary: | Screen won't wake up after blanking | ||
---|---|---|---|
Product: | [Unmaintained] kscreensaver | Reporter: | Alpheus <alpheus.madsen> |
Component: | general | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | major | CC: | mgraesslin |
Priority: | NOR | ||
Version: | 4.9.2 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Alpheus
2013-01-04 20:24:24 UTC
I should also add that I have attempted to change the resolution of the laptop screen from 1920x1080 (auto) to 1680x1050, and to a couple of other lower resolutions, but this doesn't seem to affect the problem. I'd like to add another update: Today I have received my docking station, and I was finally able to plug in my second monitor! But it took a while to figure out how to get my computer to recognise it. In order for me to do so, I had to go into BIOS or rather UEFI, and turn off "Optimus" (which, if I understand correctly, makes it possible to turn Nvidia support on or off, so that you could save in battery power). By turning off "Optimus", I am strictly using nVidia hardware. I finally have both monitors working, although I'm not sure at this point whether I'm using the Open Source nVidia driver, or if I'm using an nVidia binary. (It seemed that every time I tried to use the binary, it would mess up my xorg.conf file, and I'd be stuck with VGA resolution until I deleted it). At this point, I don't care: it works, and I'm going to leave it alone. (I *do* wish I could get the laptop screen to work along with the other two monitors, but I think that's a hardware issue, not a software one...) Thus, this bug might be in the Intel chipset code, rather than the nVidia code. Since I don't expect to be taking my laptop home, or to take it travelling any time soon, I don't expect to run into this bug in the near future; all this means, however, is that when the bug hits me, it will hit unexpectedly (assuming I forget about it! ;-). Also: I haven't tested it, but perhaps turning off "Optimus" in UEFI will be a decent temporary fix... Sounds like a driver and/or hardware issue. Initially optimus support on Linux was really bad, so I rather blame the hardware ;-) |