Arch announced that they are going to use dbus-broker by default as the D-Bus daemon, to read more go to the official announcement.
edit by @joekamprad adding info image
edit by @joekamprad adding info image
16 Likes
That was it! I had a problem last night, tried to downgrade dbus and systemd and broke my system quite badly! Didnāt know about the change so I just made it worse 
I wonder what happened, because updating the system should suggest to replace the old dbus package with the new package. And they are ātheoreticallyā fully compatible and no breakage should happen.
I also recommend to subscribe to Archlinux News with a RSS reader in example: https://archlinux.org/news/
1 Like
eos-update-notifier should also announce the existence of Arch News - maybe check the config
1 Like
I read a bit about this yesterday, and decided to wait to update until my next day off since it looked like there needed to be some manual follow up to enable the new services.
nope, simply choose between broker (recommended) and daemon while updating and thatās it.
The stuff in the RFC on Gitlab is just internal stuff that is done in the background, no user interaction required.
On my system kde crashes during start when dbus-broker-units is used. If I use dbus-daemon-units everything is working as before. There is nothing in the logs that points me to the cause of the issue. So I hope dbus-daemon-units is not removed in the futureā¦
you should add that you are using KDE-Unstable repoās so your issue is not relevant to normal users who donāt:
https://bbs.archlinux.org/viewtopic.php?id=289413&p=6
and yet there you even post a log message and even have a reply with a possible solution:
https://bbs.archlinux.org/viewtopic.php?pid=2141865#p2141865
Dbus-broker is enabled and running. No mixing of daemon and broker. the first log was not the correct one - I saw this later (of course there is no ā¦daemonā¦ in the logs). My question about locale has no echoā¦ What solution do you mean?
thanks for the update butā¦
ā¦in a yay update yesterday, yay made me make a choice: update dbus by picking #1 dbus-broker or #2 dbus-whatever-i-cant-remember
in the opposite of a sherlock holmes moment I deduced Archās labeling of #1 with the parenthetical subtitle of (default) meant to pick itā¦
ā¦so I gambledā¦
ā¦rebooted=success so I have to assume I picked the right dbus. I did not consult internet or forum, I just kind of gambled, or āgripped it and ripped itā as John Daly used to sayā¦
sincerely, ellipsis-obsessed drunk
1 Like
Well:
https://wiki.archlinux.org/title/D-Bus#dbus-broker
The systemd system and user services are triggered by
dbus.socketat systemd system and user levels. The sockets trigger the relevantdbus.service, the service file for which is a symlink todbus-broker.service. Thedbus-broker.servicethus should not be expressly enabled.
sorry @Bryanpwo forget to post this before i was only adding it as a message on telegram and forget about it after this 
3 Likes
Why apologize? Youāre not the only one responsible for the news feed for this project. I received the announcement and and shared it over here, thatās all. 
3 Likes
indeed
Donāt worry, i can spread it further by making some HONK!!!
Gut gut 
Shit. I selected D-Bus daemon because I always knew it as what Arch used. RIP
Edit: Am I going to have any issues if I donāt switch?
So thatās why my additional drives hang on mounting now perhapsā¦?
arch said it will be supported for some time:
For the foreseeable future we will still support the use of
dbus-daemon, the previous implementation.
i bet there will be an announcement when support is fully stoppingā¦ but i would change now so you are safeā¦
1 Like