It's seemingly much less bad if I disable suspend when plugged into
power, and maybe the remaining problems come from plugging in power
before resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This one seemed like it refused to wake even enough to draw a black
scree, just stayed asleep. I've no idea if this is hlepful
** Attachment added: "refuses_to_wake.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5579458/+files/refuses_to_wake.txt
--
You
Another purple screen lockup. It's now also more common the system runs
how while closed.
** Attachment added: "purple_screen_lockup-8_april.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5578017/+files/purple_screen_lockup-8_april.txt
--
You received
I've still not tried other kernels, in part because ubuntu keeps pushing
out new OEM kernels, so I give them all a try, but the same basic
problem persist, either gnome-shell gives only a black screen, or else
the whole system hangs on the purple screen.
I've far more diverse crashes with the
It's growing kinda worst with 5.14.0-1031-oem in that gnome-shell now
more reliably fails unsleep, but I've not yet seen any real crash under
5.14.0-1031-oem.
I've still not tried non OWM kernels.
** Attachment added: "black_screen_with_mouse-29_march-b.txt"
I'd another crash with a purple screen and no mouse movement, but this
time only a 10 minute lid close caused the crash. Awful lot of gdm and
gnome-shell errors this time, but not clear the source.
** Attachment added: "purple_no_mouse-23_march.txt"
It's again waking with a black screen in which only mouse and
Fn+Ctrl+Alt+F?? keys work. I've attached the jountalctl -b0 output from
prior to reboot, probably more relevant than grabbing the actual reboot.
Mär 23 07:09:16 aletheia kernel: Restarting tasks ... done.
Mär 23 07:09:16 aletheia
Appears nope I've purely a sleep problem, unless all this fwupd playing turnned
off hibernate:
```
root@aletheia:/home/jeff/Downloads# systemctl status hibernate.target
● hibernate.target - Hibernate
Loaded: loaded (/lib/systemd/system/hibernate.target; static; vendor prese>
Active:
I've found some lenovo firmware oddities too
https://github.com/fwupd/firmware-lenovo/issues/210 so I'll poke around
there too.
** Bug watch added: github.com/fwupd/firmware-lenovo/issues #210
https://github.com/fwupd/firmware-lenovo/issues/210
--
You received this bug notification because
It's related to during being suspended: It does not trigger on pressing
suspend from the menu bar, waiting briefly, and then pressing keys to
wake. It also does not trigger if I close and open the lid less than a
minute later. It can now trigger if I close the lid and then reopen the
lid 10
I've also found folks fixed similar issues by downgrading the kernel to
5.11.0.38:
https://askubuntu.com/questions/1384450/ubuntu-20-04-wont-wake-from-suspend-or-completely-shutdown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've also found folks fixed similar issues by downgrading the kernel to
5.11.0.38:
https://askubuntu.com/questions/1384450/ubuntu-20-04-wont-wake-from-suspend-or-completely-shutdown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also the Fn+Ctrl+Alt+F?? keys no longer worked here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965219
Title:
gnome lock screen does not permit reentering password
To manage notifications
I'd something new this time, after sleep/suspend it returned to the
purple login screen, but now nothing worked, no mouse or keyboard. It
ran the fan for a little while, so I give it some time to return, but no
luck.
** Attachment added: "purple_no_mouse.txt"
oops alright. I've no gnome-shell reports in /var/crash only another
systemd-timesyncd report.
I don't think gnome-ghell is crashing, but sometimes just stuck when
emerging from suspend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Is it normal that gnome-session-bin is installed but gnome-session is
not installed?
I believe this black screen version is different because when switching
back with Fn+Ctrl+Alt+F1 it simply returns to the black screen, without
any purple password prompt. I suppose another problem must be
It now manifests as a black screen with the same behavior, mouse works
but no keyboard, except for Fn+Alt+Ctrl+F?? working.
I've attacked the output of journalctl but from the current boot since I
used killall -HUP gnome-shell, which yes leave some applications
running, but not firefox (or tor
It's only the three built in extensions installed.
Thanks I'll run journalctl -b-1 > prevboot.txt next time.
ls /var/crash/ says
_usr_lib_systemd_systemd-timesyncd.102.crash
_usr_lib_systemd_systemd-timesyncd.102.upload
_usr_lib_systemd_systemd-timesyncd.102.uploaded
I only see a similar
Public bug reported:
Initially, only the mouse works in the gnome lock screen, without any
way to get a password prompt. It's likely only happening when returning
from suspend with lid open.
It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
login without gnome. After this,
Yes, this remains an issues in ubuntu 20, nearly a fresh install. I'll
try to report what happens, but it's running for over an hour so far.
It's progress bar does slowly move however.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
20 matches
Mail list logo
