Kernel with optional kdbus USE flag was released today to start testing. First issue I've come across is that the KDE environment fails to load when kdbus is being used. Seems to fail trying to create a session bus. Not really quite sure which package to attribute it to. Reproducible: Always
Created attachment 405884 [details] Emerge Info
We are really going to need more information of some sort to be able to do anything useful with this bug report. Please give the versions of the following packages: KDE systemd dbus kernel As well, please check your journal and Xorg.0.log for errors.
Xorg.log does not contain any errors, The problem seems to be confined to kdm / klauncher. I'm attaching the kdm.log and the relevant chunck from the journal. KDE: 4.14.3 systemd-220-r2 dbus-1.8.16 gentoo-sources-4.1.0-r1
Created attachment 405932 [details] KDM log
Created attachment 405934 [details] journal log
Could you please try with another login manager like sddm?
I had already thought of that and tried SDDM. No difference.
(In reply to Reuben Martin from comment #7) > I had already thought of that and tried SDDM. No difference. Thanks for testing. It's probably not possible with Plasma 4 to get it working. I will try with Plasma 5 soon.
Probably you just have to use the reverse-shim proxy: /usr/lib/systemd/user/systemd-bus-proxyd.service --- [Unit] Description=Legacy D-Bus Protocol Compatibility Daemon [Service] ExecStart=/usr/lib/systemd/systemd-bus-proxyd \ --address=kernel:path=/sys/fs/kdbus/%U-user/bus NotifyAccess=main ---
I actually kdbus working with KDE4 working via startx. I did comment out a line at the top of /usr/bin/startx to prevent it from starting a redundant dbus session, but that didn't stop anything from working. #unset DBUS_SESSION_BUS_ADDRESS I will try to test with KDM this weekend.
(In reply to Johannes Huber from comment #8) > (In reply to Reuben Martin from comment #7) > > I had already thought of that and tried SDDM. No difference. > > Thanks for testing. It's probably not possible with Plasma 4 to get it > working. I will try with Plasma 5 soon. Testing done: Plasma 5 + sddm works.
(In reply to Ulenrich from comment #9) > Probably you just have to use the reverse-shim proxy: > > /usr/lib/systemd/user/systemd-bus-proxyd.service > --- > [Unit] > Description=Legacy D-Bus Protocol Compatibility Daemon > > [Service] > ExecStart=/usr/lib/systemd/systemd-bus-proxyd \ > --address=kernel:path=/sys/fs/kdbus/%U-user/bus > NotifyAccess=main > --- I linked the system service version of the shim, as well as the user socket version to: /etc/systemd/system/basic.target.wants/systemd-bus-proxyd.service and /etc/systemd/user/default.target.wants/systemd-bus-proxyd.socket respectively, and am able to load the kde4 environment via kdm & klauncher. I'm not sure if this is the "correct" way to do it though, because the system console shows a lot of messages similar to this: systemd-bus-proxyd[1738]: Failed to add match for directed signals: Invalid argument This is now with systemd-222.
I had issues with systemd 220. 222 no issues and it works fine.
I can confirm that it works with KDM/KDE4 on systemd-222. I did not need to mess with symlinking any service files. I do get this error message in my journal every few minutes, but I have not noticed anything broken. systemd-bus-proxyd[851]: Failed to add match for directed signals: Invalid argument
(In reply to Mike Gilbert from comment #14) > I can confirm that it works with KDM/KDE4 on systemd-222. I did not need to > mess with symlinking any service files. > > I do get this error message in my journal every few minutes, but I have not > noticed anything broken. > > systemd-bus-proxyd[851]: Failed to add match for directed signals: Invalid > argument I should have tried it without linking in the services directly since it was an updated version of systemd. Got rid of the manual linking and it still works. Marking as resolved -> obselete.
