Daniel, again thanks for your efforts. My replies in red below. --rti
On Thu, Dec 13, 2018 at 2:41 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> There are two main issues I can see:
> 1. The 'pixel-saver' extension may be causing some bugs so maybe remove
> it while debugging.
>
Although that new log from comment #19 is more useful. It shows GDM
repeatedly failing:
Dec 13 01:06:43 hp15-ay016nr systemd[1]: Starting GNOME Display Manager...
Dec 13 01:06:43 hp15-ay016nr generate-config[2068]: warning: Failed to read
keyfile '/usr/share/gdm/dconf/90-debian-settings': Key
There are two main issues I can see:
1. The 'pixel-saver' extension may be causing some bugs so maybe remove
it while debugging.
2. You haven't actually had a gdm3 boot attempt since 9 December. So the
failures you are experiencing recently are from SLiM, which makes this
bug invalid for gdm3.
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Invalid
--
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/1808125
Title:
[WORKAROUND] Ubuntu 18.10 boot hangs with INTEL
I'm sorry, I got confused between the full journal file and the previous
boot journal file. This is the previous boot as requested. The huge
compressed .xz file is the full journal.
#journalctl -b-1 > prevboot.txt
** Attachment added: "previous boot journal file"
This is a recent apt history log. Perhaps it may provide an extra clue
to the cause. The boot failure began after the December 9 update.
** Attachment added: "hp15-ay016nr_apt_history.log"
Unable to take screenshot of the boot hang (duh) so I copied verbatim
the two lines that appear in a *backlit* black screen (not sure if the
backlight makes a difference,) and added a note about changes in the
power button behavior during boot time. This could be related to my
removal of timeout
I ran #journalctl -b-1 > prevboot.txt in Recovery Mode after a hung GDM3
login attampt, then re-enabled SLiM DM to log in. The upload of this
file was taking forever, so, I checked, and it's 771.2 MB! I am
attempting to re-upload it as a compressed file
hp15-ay016nr_journal.tar.xz 10.8 MB.
**
** Attachment added: "lspcik.txt model name prepended"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1808125/+attachment/5221856/+files/hp15-ay016nr_lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
I don't think "Starting bpfilter" will be related at all. Likely that's
just the last message you happen to see before the hang occurs.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
This is not a question, but I found no thread to report this bug and
workaround on NON-NVIDIA-BASED systems:
Ubuntu 18.10, kernel 4.18.0-12-generic, GNOME Shell 3.30.1 on X11, after
a Dec 9 update:
Boot
Please:
1. Run 'apport-collect 1808125' to send us more information about the
system.
2. Take a photo of the problem if you can.
3. Run 'journalctl > journal.txt' and attach the file 'journal.txt'
here.
4. Run 'lspci -k > lspcik.txt' and attach the file 'lspcik.txt' here.
** Tags added:
5. Reproduce the hang, and then on the very NEXT reboot (recovery mode) run
this command:
journalctl -b-1 > prevboot.txt
and attach the file 'prevboot.txt' here.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
13 matches
Mail list logo
