[Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

2018-11-21 Thread Lawrence Houston
The Bug is present whether or not xserver-xorg-video-intel driver is installed. >From what I can determine the generic modsetting driver is being used in either case! Attached is the Xorg.0.log with the xserver-xorg-video-intel driver installed? ** Attachment added: "Xorg.0.log with the

[Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

2018-11-21 Thread Lawrence Houston
Attached is the Xorg.0.log without the xserver-xorg-video-intel driver installed? ** Attachment added: "Xorg.0.log without the xserver-xorg-video-intel driver installed" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801609/+attachment/5215016/+files/Xorg.0.log.nointel -- You

[Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

2018-11-20 Thread Lawrence Houston
With my Toshiba Satellite C650 (Core i3-2350M 2.3 GHz, onboard Intel HD Graphics 3000): - Running "dm-tool switch-to-greeter" does NOT trigger the Bug, rather it takes me to a Locked Screen, from which I can Unlock and return to my Desktop - From a Blanked Login Screen. Behaviour is what it

[Bug 1803268] Re: Ubuntu 18.10 after Blank Screen System Will NOT Unblank

2018-11-19 Thread Lawrence Houston
*** This bug is a duplicate of bug 1801609 *** https://bugs.launchpad.net/bugs/1801609 ** This bug has been marked a duplicate of bug 1801609 Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) ** Summary changed: -

[Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

2018-11-19 Thread Lawrence Houston
Confirming this problem exists with my Toshiba Satellite C650 (Core i3-2350M 2.3 GHz, onboard Intel HD Graphics 3000), with a fresh Xubuntu 18.10 Installation. In my case switching to another Virtual Terminal and back to VT-7 (Alt- Ctrl-F7), returns me to an unblanked XFCE Desktop! For me

[Bug 1803268] Re: Ubuntu 18.10 after Blank Screen System Will NOT Unblank

2018-11-17 Thread Lawrence Houston
** 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/1803268 Title: Ubuntu 18.10 after Blank

[Bug 1803268] Re: Ubuntu 18.10 after Blank Screen System Will NOT Unblank

2018-11-17 Thread Lawrence Houston
This was a clean installation of Xubuntu 18.10 on my Toshiba Satellite C650 and the issue with the blanked screen NOT responding to Keystrokes or Mouse Events was observed during Installation and has continued since the clean installation! With the Upstream Kernel I have the same problem with the

[Bug 1803268] [NEW] Ubuntu 18.10 after Blank Screen System Will NOT Unblank

2018-11-13 Thread Lawrence Houston
Public bug reported: Toshiba Satellite C650 (embedded Intel HD Graphics 3000) running Xubuntu 18.10. Once the Toshiba's Screen has Blanked, it will not unblank with normal Keystrokes or Mouse Events. My "Work around": Plugging an External Monitor into the Satellite C650's VGA Port, which will

[Bug 1799964] Re: Ubuntu 18.10 After Blank Screen System Won't Come Back

2018-11-13 Thread Lawrence Houston
Similar problem with my Toshiba Satellite C650 (embedded Intel HD Graphics 3000) running Xubuntu 18.10. Once the Screen has Blanked, it will not unblank with normal Keystrokes and Mouse Events. My "Work around": Plugging an External Monitor into the Satellite C650's VGA Port, which will unblank

[Bug 1743027] Re: error loading realtime clock since upgrading to 17.10

2018-11-01 Thread Lawrence Houston
Within the 4 computer I have running Ubuntu, only one, my Toshiba Satellite Laptop with the current 4.15 Kernels available from the Ubuntu 16.04.5 and 18.04.1 Repositories fails to create the /dev/rtc device... NOTE: The 3 other Ubuntu Machine are not effected by this CONFIG_WDAT_WDT Bug...