OK then it sounds like a kernel configuration problem where the system
is sleeping some components too deeply to wake up.
Do you have 'tlp' installed? If so then it's a tlp bug/feature. Just
uninstall tlp.
If you don't have 'tlp' installed then you can still tweak which system
components are able
Connected USB mouse did the trick! I just noticed that I can only wake
up the screen if a USB mouse is connected.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1977977
Title:
** Attachment added: "System log with connected USB mouse"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977977/+attachment/5596317/+files/kmsdebug2.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in U
** Attachment added: "System log without connected USB mouse"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977977/+attachment/5596316/+files/kmsdebug1.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell i
Did you forget the "Wait 10 seconds" step maybe? See comment #3.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1977977
Title:
Blanked screen doesn't wake up after locking
To
When a monitor turns off you will get a log message that contains:
property 'ACTIVE' (22) to 0
which is not mentioned in the log of comment #17. So indeed that log is
not from a time when the monitor was turned off via software.
--
You received this bug notification because you are a member o
Either the log in comment #17 is not from when the screen was
blank/black/off, or it was and the monitor/driver is faulty. Because the
kernel seems to be reporting that the screen is successfully displaying
new frames. If it's doing that but you can't see an image then it's a
problem in the kernel
The screen remained blank. II want to clarify that "blank screen"
doesn't just mean that it's black, but also powered off. On X11 I found
a workaround by disabling DPMS (in this case, "blank screen" means it's
just black, not powered off).
--
You received this bug notification because you are a m
kmsdebug.txt ends with the screen drawing normally and successfully. Did
you see anything on screen or did it appear to be off?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1977
** Attachment added: "kmsdebug.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977977/+attachment/5596083/+files/kmsdebug.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.laun
Happened again :(
** Attachment added: "System log"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977977/+attachment/5595900/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and disabling disable-wakeup-on-
lid-switch.service did the trick for me! Thanks!
> Out of curiosity, what package owns /etc/systemd/system/disable-
wakeup-on-lid-switch.service ?
It's a self-written service that blocks the laptop from waking up when
the li
Another possibility is that you have excessively deep sleep enabled on
too many devices (like if 'tlp' is installed) and some machines can't
wake up from that. Make sure you don't have tlp installed and also try
adding a USB mouse to wake the machine up with - you can also then see
if the mouse is
OK, the final thing to try is to replace the above environment variable
with:
MUTTER_DEBUG=kms
then reboot, reproduce the hang in a Wayland session, reboot again and
run:
journalctl -b-1 > kmsdebug.txt
and attach the resulting text file here.
That will tell us if gnome-shell is sending the
Out of curiosity, what package owns /etc/systemd/system/disable-wakeup-
on-lid-switch.service ?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1977977
Title:
Blanked screen doe
> Looks like you were only logged in for 2 seconds before the log ends.
Is that right, you just locked the screen immediately?
Yes, that's right.
> Also do you have any external monitors connected?
No.
> MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
> Any improvement?
Nothing changed.
** Attachment added:
If a bug is common to Xorg and Wayland sessions then that often means
it's in the kernel, or in the hardware. Let's assume that's not yet true
and please follow the instructions in comment #8.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscrib
I was wrong, disabling DPMS didn't fix the suspend issue. So these
problems are most likely unrelated.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1977977
Title:
Blanked scr
Thanks. Looks like you were only logged in for 2 seconds before the log
ends. Is that right, you just locked the screen immediately?
Also do you have any external monitors connected?
Next please try adding this to /etc/environment:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
and then reboot and log into
The /var/crash folder is empty, there are no fresh logs at
https://errors.ubuntu.com/user/ID.
** Attachment added: "Wayland system log"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977977/+attachment/5595815/+files/wayland_prevboot.txt
--
You received this bug notification bec
Thanks. The Xorg session in comment #4 doesn't appear to have crashed.
Maybe it was just frozen.
Please repeat the above steps with a Wayland session and also remember
to follow
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug n
Also, disabling DPMS solved the issue for me where my laptop couldn't
properly suspend/resume.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1977977
Title:
Blanked screen does
** Attachment added: "System log"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977977/+attachment/5595797/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launch
Thanks for the bug report.
Firstly please check for crashes by following these steps:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
In a Wayland session it is only crashes of 'gnome-shell' that are
relevant here.
Secondly, next time the problem happ
Disabling DPMS (using command "xset -dpms") fixes this issue on X11, but
I haven't found a workaround on Wayland.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1977977
Title:
Blanked
25 matches
Mail list logo
