Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#59315 - Systemd update to version 239.0-2 bricks system

Attached to Project: Arch Linux
Opened by john01dav (john01dav) - Thursday, 12 July 2018, 23:21 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 13 July 2018, 01:18 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


I originally posted this bug to the systemd bug tracvker, but they redirected me here.

Original systemd bug tracker post:

My computer is MSI GT62VR 6RE laptop.

systemd bug report text:

systemd version the issue has been seen with:
> 239.0-2

Used distribution:
> Arch Linux

Expected behaviour you didn't see:
Unexpected behaviour you saw:
> I recently updated via pacman to the new systemd version listed above. I expected it to automatically work, as all previous updates have. Instead, the system hangs on boot some time between running fsck on my / partition and loading gdm to allow for graphical

**Steps to reproduce the problem**
I am unsure of exactly what causes this problem, but I know for sure systemd is, at least partially, at fault (updating this and only this package produces the issue exactly on my system). I do not know what, if any, other packages are involved. It is possible that gdm is also involved, for I noticed an error from Glib running in gdm's process about a failed assertion as the last log before the system hang. I can not access this message when my system is fully loaded, and able to copy/paste the message into something like a web browser, so I can not provide the exact message. Journalctl does not seem to provide any way to access older messages, and I need to reboot in single-user mode (where I saw the message) to undo the systemd update. Based on this, the most likely steps to reproduce this are as follows:

1. Install Arch Linux (with the latest packages as of July 5th 2018 in the Arch Linux package archives
2. Install gdm
3. Set gdm to launch on the system's startup
4. Update systemd to the latest version (, at the time of writing) in Arch's repositories, optionally updating the other packages to the latest version as well.
5. Reboot and observe as the computer is Temporarily Bricked™

To undo the issue and Unbrick™ the computer:

1. When booting, press "e" on the Arch Linux menu entry in grub, or do the equivalent in your bootloader.
2. Replace the word "quiet" with "S" on the line near the bottom beginning with the word "linux".
1. Use the Arch Linux package archives to downgrade all packages to their latest versions as of July 5th 2018.
4. Reboot to a no-longer-up-to-date but also Unbricked™ system.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 13 July 2018, 01:18 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#59262 
Comment by john01dav (john01dav) - Thursday, 12 July 2018, 23:50 GMT
I managed to solve the issue (as one usually does after making a report). I had to disable wayland for gdm in the config /etc/gdm/custom.conf by uncommenting the line that does so.
Comment by loqs (loqs) - Friday, 13 July 2018, 00:34 GMT