Description of problem:
After installing the pantheon-session-settings package on fedora 30, gdm won't come up at boot at all. The log files for that boot don't show anything of interest, but I have to force reset the machine, boot into multi-user.target, and dnf remove pantheon-session-settings - only then gdm works again at the next boot.
Version-Release number of selected component (if applicable):
100% reliable, both on clean installs of f30 beta and when upgraded from f29
Steps to Reproduce:
1. Start with either a clean install of f30 beta or upgrade from f29
2. install pantheon-session-settings / group "Pantheon Desktop"
4. GDM won't start
gdm is broken.
gdm works and shows the "Pantheon" session.
Proposed as a Blocker for 30-final by Fedora user decathorpe using the blocker tracking app because:
Installing either the "pantheon-session-settings" package or the "Pantheon Desktop" group (which contains the package) completely breaks the system - gdm won't start successfully at the next boot.
However, it still seems to capture Ctrl-Alt-FX keys, so the only way to fix it again is to *boot into multi-user.target* and "dnf remove" the packages again.
I don't think it's acceptable that installing packages can effectively lock users out of their system for good if they don't know how to set "systemd.unit=multi-user.target" on the kernel command line ...
ctrl-alt-f3 doesn't get you to a console?
also, why assign this to gdm when it seems a lot more like a pantheon bug?
No, Ctrl-Alt-F1-12 don't do anything.
And ... why would this be a Pantheon bug? I can't even get to the GDM login screen.
because GDM works fine until you install Pantheon, implying Pantheon does something to break GDM...that's how it seems to me, anyway.
The only thing that should change for GDM is an additional file in "/usr/share/gnome-session/sessions".
All autostart entries for Pantheon are qualified with "OnlyShowIn=Pantheon;".
There's basically no difference between the Pantheon session files for fedora 29 and 30.
Everything works fine on fedora 29.
After upgrading to fedora 30, GDM fails to start.
So .. I have no idea what's going wrong here.
Additional info: Installing the "pantheon-sesion-settings" package that works fine on fedora 29 doesn't change anything.
So the only moving part here really is GDM, AFAICT.
Crawling through the logs almost line by line, I think I found the real issue here:
dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
Which is preceded by this crash in dbus-broker-launch:
ERROR manager_add_services @ ../src/launch/main.c +1130: Input/output error
manager_run @ ../src/launch/main.c +1708
run @ ../src/launch/main.c +1857
main @ ../src/launch/main.c +1886
Exiting due to fatal error: -5
Which isn't even caused by anything in pantheon-session-settings -
but by the appcenter dbus service (for a reason I cannot imagine).
So, sorry about blaming GDM for this, it's dbus-broker that crashes and brings down GDM with it.
I've decided to retire the broken package (appcenter) instead of spending even more time on this. It's not worth it.
Thanks everybody for your help, and sorry for any trouble I might have caused you.
Right, I looked at Elementary-AppCenter and it installs a dbus-service-file with `Name=AppCenter`. This is not a valid dbus-service-name. I don't know how this ever worked on dbus-daemon, but dbus-broker refuses this and will complain when you provide invalid configuration data. I assume the service file was simply ignored but dbus-daemon.
Anyway, I will look into improving the error-message from dbus-broker there! Thanks for the report!
Well, it's definitely not urgent anymore, since I removed the package from fedora (it had numerous other issues, as well).
But I will provide this information to the upstream elementary / appcenter developers. Thank you!
For completeness: This is now fixed in upstream dbus-broker. It will be included in the v20 release this week. The fix now makes dbus-broker ignore service files with invalid names.
Great, thanks! That should make it more robust for everybody. :)
dbus-broker-20-2.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c1189aa7ea
dbus-broker-20-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c1189aa7ea
dbus-broker-20-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.