[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 Ubuntu
Desktop Bugs, 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 Ubuntu
Desktop Bugs, 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1811599
Title:
When booting, the computer hangs
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:
Note to developers: This system seems to have an Intel GMA 950 GPU.
Limited to OpenGL 1.4? So it is much older than the CPUs that bug
1727356 was about. Still, this system should start up eventually even if
using software rendering.
** Summary changed:
- When booting, the computer hangs at a
Thanks, that log is good. The only real error I can see is that your GPU
doesn't support some feature gnome-shell is trying to use:
Jan 21 10:25:58 HackBook gnome-shell[1919]: Shader compilation failed:
0:44(42): warning: `cogl_texel0'
used
Hey Daniel,
You were right - the computer was stuck in recovery mode. I manually
booted it into normal mode and then restarted it and re-produced a hang. I
then rebooted into recovery mode and recorded that boot with journalctl
-b-1 > prevboot.txt. Please see attached.
The log states that the
Although you have provided some logs that are not in recovery mode,
those logs span multiple days so are not helpful in pinpointing the
immediate problem.
When sending logs in future please ensure they don't mention "recovery
nomodeset", AND that the earliest and oldest dates in the log file are
I suspect the mistake is that you are not manually un-selecting recovery
mode, so it is always rebooting in the same mode as last time, so is
always in recovery mode.
Either that or the non-recovery mode boots are failing to record a log
at all. But I suspect it's more likely you're stuck in
Hey Daniel,
I'm honestly not sure what I'm doing wrong. Here's precisely what I'm
doing. Tell me where I'm messing up:
First, I booted into recovery mode by hitting Esc on bootup, and selecting
boot into recovery mode. The computer then boots, and reaches a point at
which it I have multiple
Please try again. The log in comment #7 is from recovery mode :(
I think you forgot step 2 in comment #2.
--
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/1811599
Title:
When booting,
My apologies, I've been out of town for a few days. Here is the updated
version, which was just created, with debugging enabled.
Please see attached.
Alex
On Tue, Jan 15, 2019 at 11:45 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> That boot seems to be starting from 11 Jan.
That boot seems to be starting from 11 Jan. Does it also include debug
enabled per comment #2?
Regardless, it's a little too old and unnecessarily large. Please follow
the steps in comment #2 more carefully and do it again.
--
You received this bug notification because you are a member of
Here it is.
Alex
On Tue, Jan 15, 2019 at 7:20 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> Alex,
>
> The log in comment #3 is from recovery mode, not what we need.
>
> Please follow the steps in comment #2 again, but before sending
> 'prev_boot.txt' try compressing it to make
Alex,
The log in comment #3 is from recovery mode, not what we need.
Please follow the steps in comment #2 again, but before sending
'prev_boot.txt' try compressing it to make it smaller:
xz prev_boot.txt
and then send us 'prev_boot.txt.xz'
--
You received this bug notification because you
I received an error from Launchpad stating that the previous file I sent
was too large (14 MB) and could not be delivered, and so I repeated the
above steps again. Here's another failed boot log, and for some reason,
it's much, much smaller (836 KB).
Alex
On Tue, Jan 15, 2019 at 10:35 AM Alex
Please:
1. Boot into recovery mode and enable (uncomment) debugging in
/etc/gdm3/custom.conf
2. Reboot into normal mode and reproduce the hang.
3. Reboot again into recovery mode and run:
journalctl -b-1 > prev_boot.txt
and then send us the file 'prev_boot.txt'.
** Changed in: gdm3
23 matches
Mail list logo
