[Bug 1645505] Re: Screen doesn't turn on after suspending

2016-12-18 Thread Christopher M. Penalver
Diego Veas, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645505/comments/6 regarding this being fixed with a BIOS update. For future reference you can manage the status of your own bugs by clicking on the current status in the

Re: [Bug 1645505] Re: Screen doesn't turn on after suspending-SOLVED

2016-12-02 Thread Diego Veas
I found the solution, I upgraded the bios from 1.0.0 to 1.0.1 (obtained from dell web page) and now,if you suspend manually you can turn it on again. If you close the lid, it suspends until you open it again. Regards, Diego Veas On 02/12/16 20:11, Mario Limonciello wrote: > ** Tags added:

[Bug 1645505] Re: Screen doesn't turn on after suspending

2016-12-02 Thread Mario Limonciello
** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645505 Title: Screen doesn't turn on

Re: [Bug 1645505] Re: Screen doesn't turn on after suspending kernel-bug-exists upstream-confirmed

2016-11-29 Thread Diego Veas
Dear Joseph, I tried with kernel 4.9.0-040900rc7_4.9.0-040900rc7.201611271731_all.deb but bug still exists. Regards, Diego Veas On 29/11/16 14:34, Joseph Salisbury wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having

Re: [Bug 1645505] Re: Screen doesn't turn on after suspending

2016-11-29 Thread Diego Veas
Dear Joseph, this issue started after a new installation (I bought my computer with Windows 10). I'll try the upstream kernel. Regards, Diego Veas On 29/11/16 14:34, Joseph Salisbury wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where

[Bug 1645505] Re: Screen doesn't turn on after suspending

2016-11-29 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9