On 07/30/2015 11:57 AM, Lennart Poettering wrote: > Heya! > > I'd like to ask everybody to test kdbus on Rawhide. Josh thankfully > added it to the Rawhide kernel packages, and our systemd RPMs come > with built-in support, too now. If you are running an up-to-date > Rawhide system adding "kdbus=1" to your kernel command line is hence > everything you need to run kdbus instead of dbus-daemon. (No > additional RPMs need to be installed.) If you do, things should just > work the same way as before, if we did everything right. By adding or > dropping "kdbus=1" to/from the command line you can enable kdbus or > revert back to dbus1 on each individual boot.
What I see: # dmesg | grep dbus [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-0.rc4.git3.1.fc24.x86_64 root=UUID=82dead0b-1e73-41b9-a46e-a107f23fda68 ro quiet LANG=en_US.UTF-8 kdbus=1 [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-0.rc4.git3.1.fc24.x86_64 root=UUID=82dead0b-1e73-41b9-a46e-a107f23fda68 ro quiet LANG=en_US.UTF-8 kdbus=1 [ 0.976597] systemd[1]: Failed to insert module 'kdbus': Function not implemented [ 6.523291] kdbus: initialized [ 6.523379] systemd[1]: Inserted module 'kdbus' [ 1166.601797] systemd-dbus1-generator[7138]: Failed to create /run/user/0/systemd/generator.late/dbus-org.kde.kuiserver.service: File exists Why the earlier failure? Getting duplicate requests for dbus-org.kde.kuiserver.service? -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
