Please provide sufficent detail to allow others to reproduce the issue. Start by postingthe text output from inxi -Fzx(braced by triple backquotes or using the </> icon so the post can be found in searches by the next person with the same problem and hardware).
What is the history: is this a fresh install or an upgrade? Check journalctl for more details of the problem.
Linux Hardware Database (LHDB) has many entries, most higher spec. You appear to have 4GB RAM, but Intel graphics steals some of that, so you are right on the edge of what will work with Fedora Workstation.
Which Fedora spin are you using? Your dbus daemon service matches what I see on Workstation:
Systemd tries to do initializations in parallel, so memory uasge at startup will be higher than for legacy init. Each new kernel tends to increase memory demands (but then people do work on trimming those demands) but living on the edge is dangerous.
Your CPU is also far below current norms. You will find one of the lightweight spins makes better use of limited RAM and CPU resources so is less likely to get into difficulties. Note that many widely used GUI programs do not work well in 4GB systems.
I’m seeing the same (similar?) issue with Kernel 6.3.6, though system RAM is 96 GB and CPU is dual Xeon E5-2687W. This is a system that’s been upgraded since Fedora 35, I think, so not a vanilla workstation. Per sealert recommendation, the system has been fully relabeled (i.e., touch /.autorelablel; reboot. Still trying to identify the cause of “No socket received”. Here’s the log message associated with the dbus-daemon failure:
Jun 10 23:47:24 zyxw.slewsys.org dbus-daemon[1862]: Failed to start message bus: No socket received.
Jun 10 23:47:24 zyxw.slewsys.org systemd[1]: dbus-daemon.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit dbus-daemon.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jun 10 23:47:24 zyxw.slewsys.org systemd[1]: dbus-daemon.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit dbus-daemon.service has entered the 'failed' state with result 'exit-code'.
Jun 10 23:47:24 zyxw.slewsys.org audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Evidently gdm still launches dbus-run-session[1] which is provided by the dbus-daemon package. So if running Gnome, rather than remove dbus-daemon, just disable it, i.e., systemctl disable --now dbus-daemon.
The system-wide dbus server is started by systemd long before gdb has been launched. systemd also starts another dbus service for each gdb or gnome session.
There is an additional dbus server for the user session, and that is also started by systemd during setting up the session. If systemd fails to start dbus, there is a fall-back used by gdb and gnome to start it.
dbus-broker replaces dbus-daemon as you indicated. But after moving dbus-run-session out of the way: mv /usr/bin/dbus-run/session{,~}, the system crashes hard on boot:
To recover, booting to multi-user target isn’t sufficient: I had to got back to rescue target (i.e., append to kernel command line rd.systemd.init=rescue.target). So it would appear that systemd-logind is also be calling dbus-run-session???
I’m not sure how to start dbus with gdb, but in the case of gdm and maybe systemd-logind, without dbus-run-session there appear to be no fall-backs?
[vek@newbox ~]$ sudo systemctl --global list-unit-files dbus\*
UNIT FILE STATE PRESET
dbus-broker.service enabled enabled
dbus-daemon.service disabled disabled
dbus.service alias -
dbus.socket enabled enabled
4 unit files listed.
[vek@newbox ~]$
Note that --global is for user services for all users, whereas --user is for services for the current logged in user. In the latter case you must run it without sudo.
