Den lör 1 sep. 2018 kl 09:54 skrev Zbigniew Jędrzejewski-Szmek <zbys...@in.waw.pl>: > > On Sat, Sep 01, 2018 at 09:21:42AM +0200, Tomasz Torcz wrote: > > On Sat, Sep 01, 2018 at 07:06:09AM -0000, Raphael Groner wrote: > > > Hi, > > > > > > tried the suggested workaround with systemctl enable dbus-daemon. Now I > > > get a black screen after login with sddm to lxqt-session. > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1623781 > > > > F29 was supposed to switch to dbus-broker as a provider of dbus: > > > > https://fedoraproject.org/wiki/Changes/DbusBrokerAsTheDefaultDbusImplementation > > Enabling dbus-daemon would make two conflicting implementation active, > > won't it? > > "Enabling" dbus-daemon activates a link which creates the alias dbus.service > → dbus-broker.service. > So that step replaces the original dbus daemon. At least that was supposed to > happen. It is probably useful to look at 'systemctl status dbus.service' to > see what it is actually running. > > Here: > $ systemctl status dbus > ● dbus-broker.service - D-Bus System Message Bus > Loaded: loaded (/usr/lib/systemd/system/dbus-broker.service; enabled; > vendor preset: disabled) > ... > CGroup: /system.slice/dbus-broker.service > ├─1029 /usr/bin/dbus-broker-launch --scope system --audit > └─1030 dbus-broker --log 4 --controller 9 --machine-id > 08a5690a2eed47cf92ac0a5d2e3cf6b0 --audit > > Aug 31 21:12:15 krowka dbus-broker-launch[1029]: Activation request for > 'org.freedesktop.PackageKit' fail> > Aug 31 21:12:15 krowka dbus-broker-launch[1029]: Activation request for > 'org.bluez' failed: Unit dbus-org> > ... > > But note that there are actually 3 (!) dbus daemons in play. > There's the system dbus instance, discussed above, and then each user > has a user instance (systemctl status --user dbus) and another > instance used for at-spi2 (changing this requires patching at-spi2, > which I think has already happened upstream, but those changes aren't > present in Fedora yet, so we expect to see dbus-daemon there). > > Zbyszek
I can't get a commandline, everything seems stuck in the boot process.... Is there anyway to get a commandline and update the system when it is in this state? /Andreas > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
