Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1662080 - systemd 240 breaks booting to graphical user
Summary: systemd 240 breaks booting to graphical user
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-26 04:53 UTC by Bruno Wolff III
Modified: 2019-01-15 19:29 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-15 17:50:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Bruno Wolff III 2018-12-26 04:53:59 UTC
Description of problem:
Boot into graphical display doesn't work after going from 239 to 240. Booting to multi-user worked. Reverting to 239 fixed things. Most services seem to get started but I never get the display manager. I wasn't able to use c-a-f2 to get to a tty, but I have other problems with the keyboard (it's a macbook air) that might be preventing that.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Paul DeStefano 2019-01-02 19:50:08 UTC
downgrade isn't possible on rawhide, rats.  So, I'm dead until this is fixed.

Comment 2 Valdis Kletnieks 2019-01-02 20:37:51 UTC
(In reply to Paul DeStefano from comment #1)
> downgrade isn't possible on rawhide, rats.  So, I'm dead until this is fixed.

Download the RPMs for systemd-* from a Fedora 29 site and 'rpm -Uvh --force --nodep' them onto your system, that will at least get you back up and running.  If you don't have an FTP or non-GUI browser (lynx or similar) client installed, you may need to download them to another machine and sneakernet them over on a USB stick.

ftp://mirror.cc.vt.edu/pub/fedora/linux/releases/29/Everything/x86_64/os/Packages/s/ or any other mirror should do it for you.

ncftp ...g/x86_64/os/Packages/s > pwd
  ftp://mirror.cc.vt.edu/pub/fedora/linux/releases/29/Everything/x86_64/os/Packages/s/
ncftp ...g/x86_64/os/Packages/s > dir systemd-*
-rw-r--r--   16 0        0      3868908   Jul 19 08:13   systemd-239-3.fc29.i686.rpm
-rw-r--r--   12 0        0      3763956   Jul 19 08:13   systemd-239-3.fc29.x86_64.rpm
-rw-r--r--    4 0        0        70508   Jul 15 21:41   systemd-bootchart-233-3.fc29.x86_64.rpm
-rw-r--r--   16 0        0       451396   Jul 19 08:12   systemd-container-239-3.fc29.i686.rpm
-rw-r--r--   12 0        0       436552   Jul 19 08:13   systemd-container-239-3.fc29.x86_64.rpm
-rw-r--r--    8 0        0       298140   Jul 19 08:13   systemd-devel-239-3.fc29.i686.rpm
-rw-r--r--    4 0        0       298148   Jul 19 08:13   systemd-devel-239-3.fc29.x86_64.rpm
-rw-r--r--    4 0        0        90688   Jul 19 08:13   systemd-journal-remote-239-3.fc29.x86_64.rpm
-rw-r--r--   16 0        0       517524   Jul 19 08:13   systemd-libs-239-3.fc29.i686.rpm
-rw-r--r--   12 0        0       488228   Jul 19 08:13   systemd-libs-239-3.fc29.x86_64.rpm
-rw-r--r--   12 0        0       167072   Jul 19 08:13   systemd-pam-239-3.fc29.x86_64.rpm
-rw-r--r--    4 0        0      4068848   Jul 19 08:13   systemd-tests-239-3.fc29.x86_64.rpm
-rw-r--r--   12 0        0      1320236   Jul 19 08:12   systemd-udev-239-3.fc29.x86_64.rpm

That should at least get you up and running.  Oh, and add 'exclude=systemd-*' to your /etc/dnf/dnf.conf so your next 'dnf update' doesn't re-wedge your box. Remember to remove it once a fixed systemd ships.

Comment 3 Bruno Wolff III 2019-01-02 20:55:04 UTC
If you notice the problem within a couple of weeks you can go back using older composes. 
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20181222.n.0/compose/Everything/x86_64/os/ is still available and is what I used to downgrade.
https://kojipkgs.fedoraproject.org/compose/rawhide/ has the currently available composes, though not all went far enough to generate usable repos. Note that some didn't completely finish successfully, though still produced usable repos.

Comment 4 Bruno Wolff III 2019-01-02 21:03:07 UTC
Another option is to go to koji builds for a package. Binaries from older builds are available for a while and you can download builds for a package using a web browser or koji (koji download-build --arch=x86_64 --arch=noarch systemd-239-10.git3bf819c.fc30).
Systemd is at:
https://koji.fedoraproject.org/koji/packageinfo?packageID=10477

Comment 5 Paul DeStefano 2019-01-02 21:27:53 UTC
Ah, cool, thanks.  That makes sense.

Comment 6 Bruno Wolff III 2019-01-07 16:58:15 UTC
Now that I'm back at work, I see this doesn't seem to affect my work desktop. The home machine is a macbook air. The work machine is a dell workstation. It might be that more than one package was involved in the problem, so I'll retest the latest systemd again when I get home tonight.

Comment 7 Bruno Wolff III 2019-01-08 05:06:41 UTC
I am still having the problem on my home machine. So an update of some other package didn't fix the problem and whatever the problem is, isn't affecting all systems.

Comment 8 Zbigniew Jędrzejewski-Szmek 2019-01-11 13:49:33 UTC
Which desktop do you use?

Comment 9 Bruno Wolff III 2019-01-12 08:27:38 UTC
I use XFCE on both the machine that works and the one that doesn't.
I use lxdm for the display manager on the machine that works.
I use lightdm on the one that doesn't.

Comment 10 Bruno Wolff III 2019-01-15 17:50:54 UTC
Systemd 240-5 fixes this though I still have some artifacts in XFCE and I still have worse problems on my work machine which also uses XFCE (even when I switch to lightdm).


Note You need to log in before you can comment on or make changes to this bug.