Thank you for the review.
I agree that a read-only root filesystem can indicate disk or filesystem
errors. However, I do not believe that is what is happening here.
On every boot:
gdm.service fails because /usr/share/gdm/generate-config reports:
install: /var/lib: chmod failed with error Read-only file system
Immediately afterwards, from a TTY, I can execute:
mount -o remount,rw /
systemctl restart gdm
GDM starts successfully and the system operates normally.
The kernel log does not contain the usual EXT4 messages indicating that
the filesystem was remounted read-only due to errors (for example
EXT4-fs error, Aborting journal, or Remounting filesystem read-only).
In addition, a systemd override that executes:
ExecStartPre=/bin/mount -o remount,rw /
before generate-config makes every boot succeed.
This suggests a boot-time remount or ordering problem rather than a
permanent filesystem failure.
If there are additional diagnostics you would like me to collect to
distinguish between these possibilities, I would be happy to provide
them.
** Changed in: gdm3 (Ubuntu)
Status: Invalid => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2161707
Title:
GDM fails to start at boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2161707/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
