You are not logged in.
Pages: 1
Topic closed
Pacman update (with core-testing enabled) offers
:: There are 2 providers available for dbus-units:
:: Repository core-testing
1) dbus-broker-units 2) dbus-daemon-units
Enter a number (default=1):
The current system (journalctl) shows many dbus-daemon running.
According to
https://wiki.archlinux.org/title/D-Bus
dbus-broker is an alternative implementation.
Should I follow pacman's suggestion to change (to a new default ?), or keep dbus-daemon ?
Is a new default in progress by developers ?
Offline
If you're using the testing repos, you really need to be following the arch-dev-public mailing list so you know what's going on.
Offline
Mod note: Moving to Testing
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
If I choose dbus-broker-units my kde crashes during start (kde6 beta2). If I choose dbus-daemon-units everything is running fine.
Offline
If you're using the testing repos, you really need to be following the arch-dev-public mailing list so you know what's going on.
This seems to have landed in core. I just got the same prompt, while not using testing.
Offline
Yes, this is now out of testing: https://archlinux.org/news/making-dbus- … us-daemon/
Closing.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Pages: 1
Topic closed