[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
I think this might be related to bug 1790525 or bug 1812359. So keep an
eye on those.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1811599
Title:
When booting, the computer hangs at
Those repeated messages are probably just a consequence of still having
debugging turned on. Maybe now is a good time to try with debugging
turned off in /etc/gdm3/custom.conf so as to generate smaller logs.
> Whenever I try to get the computer to recognize the CD image and to
boot from it, I
Hey Daniel,
The other thing I noticed in the the boot logs are a seemingly futile
loop:
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/share/gdm/greeter/autostart'
Jan 22 11:38:36 HackBook
You're right - those logs are apparently from short boots.
longhangprevboot.txt lasted less than 2 minutes and only 2 seconds
between GLSL errors and the machine beginning to shutdown.
longhangprevboot2.txt lasted 2 minutes and again was only 4 seconds
between GLSL errors and the machine
Hey Daniel,
I've recorded two long hangs for you and your team to analyze.
Please find attached longhangprevboot.txt and longhangprevboot2.txt.
The only difference between the two is that longhangprevboot.txt followed
the following timeline:
normal mode -> restart to long hang -> restart to
Yes please for a new log.
This bug is almost certainly fixable. We just need a complete log, and
then a lot of patience to wait for some upstream developer to get around
to figuring it out.
If you can't wait and want to use the machine now then Lubuntu might be a
better option:
Hey Daniel,
Yeah, at the beginning of this all, I thought it was taking a long time to
boot as well, but even after letting the system sit at the purple screen
for quite some time, it never went anywhere. I had a though that my
ancient laptop might simply be too old to properly run Ubuntu, but I
Alex,
It's unclear how long this bug will take to get resolved, if at all.
Even if you find the machine does start up after 15 minutes or so, it
might not perform well enough to be usable.
If you would like to use Ubuntu on it then maybe the lighter weight
Lubuntu is a better solution right now:
10 matches
Mail list logo
