Ops, apologies for the typo, I'm running Xubuntu 18.04.03
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801609
Title:
Fails to deactivate dpms off mode after user initiated wake-up
events(not sys
I'm running Xubuntu 18.0.03, which hasn't reached end-of-life, and this
bug is still present. It was introduced when I upgraded to kernel 5.0
with xorg 1.20.4-1ubuntu3~18.04.1. It can be circumvented using either
of 2 methods:
1. Uninstalling light-locker and installing xscreensaver
or
2. As sugge
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. Bu
I would refrain from messing with the video drivers just to workaround a
bug in the screen locker. Solution #27 doesn't work for me either.
What works for me is killing light-locker and replacing it with
xfce4-screensaver or gnome-screensaver. I haven't tested mate-
screensaver and xscreensaver.
A simple workaround (that worked for me at least):
sudo apt install slick-greeter
printf '[Seat:*]\ngreeter-session=slick-greeter\n' | sudo tee -a
/etc/lightdm/lightdm.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
More info here, as well:
If I only set the "Switch off after" Display setting to >1 Minute and leave
the other settings("Blank after" and "Put to sleep after") at 0(Never),
then the display wakes up normally!
This was tested on the originally affected system(s) and required no
customized xorg.con
@bbethge, your solution worked for me. After creating xorg.conf and
enabling intel driver screen wakes up after lock and behaviour is right.
Xubuntu 18.10, Intel(R) HD Graphics 620 (Kaby Lake GT2).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Enabling the intel driver by creating /etc/X11/xorg.conf containing
Section "Device"
Identifier "intel"
Driver "intel"
EndSection
still results in a blank screen (no backlight), but it comes on when moving the
pointer, like it did in Xubuntu 18.04.
--
You received this bu
Tested positive on: Intel Core i3 3rd generation, Intel HD graphics
Also with Intel Core i7 8700k & Intel Core M-5Y31
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801609
Title:
Indeed. The log file does not list intel_drv.so, so maybe Xorg has to be
explicitly configured to do so.
Here is an upstream bug report which appears be closely related to the
blanking problem:
https://bugs.freedesktop.org/show_bug.cgi?id=108021
** Bug watch added: freedesktop.org Bugzilla #1080
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 xserver-
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 r
The cause of this issue has to be in Xorg 1.20 then (18.04 comes with
1.19).
I assume that xserver-xorg-video-intel is still installed by default, so
please check if removing this driver package has any effect (the generic
modesetting driver will be used instead).
For reference the greeter code:
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
Few more things:
- Does running "dm-tool switch-to-greeter" instead trigger the bug?
- Does simply waiting at the login screen for 10 minutes trigger the bug?
- Can the bug be reproduced after installing and booting an older kernel
version? I suggest to test with 4.15 (version used in 18.04).
ht
** Changed in: xorg-server (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/1801609
Title:
Fails to deactivate dpms off mode after user initiated wake-up
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 another
@Theo: Thanks for your help.
On Fri, Nov 9, 2018 at 10:15 AM Theo Linkspfeifer <
1801...@bugs.launchpad.net> wrote:
> I did not spot anything relevant in your log files either.
>
> Sadly, no idea how to debug this further also.
>
> ** Package changed: light-locker (Ubuntu) => xorg-server (Ubuntu
I did not spot anything relevant in your log files either.
Sadly, no idea how to debug this further also.
** Package changed: light-locker (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Attachment removed: "light-locker_lightdm.out"
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210057/+files/light-locker_lightdm.out
** Attachment removed: "light-locker_seat0-greeter.out"
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801
lightdm & syslog(relevant sections only), attached. I saw nothing
suspicious, although the lightdm.log seemed to have the most relevant
entries.
Also,
$ sleep 1 && xset dpms force off
works normally and as expected.
On Tue, Nov 6, 2018 at 11:56 AM Theo Linkspfeifer <
1801...@bugs.launchpad.net
** Attachment added: "light-locker_x-0.out"
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210060/+files/light-locker_x-0.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Attachment added: "light-locker_x-1.out"
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210061/+files/light-locker_x-1.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Attachment added: "light-locker_syslog.out"
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210059/+files/light-locker_syslog.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
lightdm & syslog(relevant sections only), attached. I saw nothing
suspicious, although the lightdm.log seemed to have the most relevant
entries.
Also,
$ sleep 1 && xset dpms force off
works normally and as expected.
** Attachment added: "light-locker_lightdm.out"
https://bugs.launchpad.net/
** Attachment added: "light-locker_seat0-greeter.out"
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1801609/+attachment/5210058/+files/light-locker_seat0-greeter.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Are there any hints in the system or lightdm logs?
/var/log/lightdm/*.log
Also, does running "sleep 1 && xset dpms force off" in general work
properly or do you encounter the same bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
27 matches
Mail list logo
