Re: [HEADS-UP] Please test kdbus in Rawhide!
On 07/31/2015 08:49 PM, Lennart Poettering wrote: On Thu, 30.07.15 19:57, Lennart Poettering (mzerq...@0pointer.de) 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. Quick update: We have released a new version of systemd now with all bugs reported here fixed. It's also in Rawhide already, but it might not have hit all mirrors yet. To download it directly, please use: http://koji.fedoraproject.org/koji/buildinfo?buildID=674692 And please remember to turn selinux at least into permissive mode when using this, or even turn it off entirely while testing (kdbus=1 selinux=0 on the kernel command line). As you probably know this is not only about a policy fix. We added a support for /sys/fs/kdbus in the latest rawhide policy builds to avoid unlabeled_t issues and we can better track all issues related to kdbusfs_t. But there is no a good policy fix in this state. It requires LSM/SELinux support and without this support it is a completely uncontrolled IPC mechanism. Also some mails about the kdbus development plans and timing would be helpful. Thanks. Mirek Thanks a lot to everybody who already tested this! Please test the new version, any feedback much appreciated! Lennart -- Miroslav Grepl Senior Software Engineer, SELinux Solutions Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On 08/06/2015 01:47 PM, Miroslav Grepl wrote: On 07/31/2015 08:49 PM, Lennart Poettering wrote: On Thu, 30.07.15 19:57, Lennart Poettering (mzerq...@0pointer.de) 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. Quick update: We have released a new version of systemd now with all bugs reported here fixed. It's also in Rawhide already, but it might not have hit all mirrors yet. To download it directly, please use: http://koji.fedoraproject.org/koji/buildinfo?buildID=674692 And please remember to turn selinux at least into permissive mode when using this, or even turn it off entirely while testing (kdbus=1 selinux=0 on the kernel command line). As you probably know this is not only about a policy fix. We added a support for /sys/fs/kdbus in the latest rawhide policy builds to avoid unlabeled_t issues and we can better track all issues related to kdbusfs_t. But there is no a good policy fix in this state. It requires LSM/SELinux support in kernel and without this support it is a completely uncontrolled IPC mechanism. Also some mails about the kdbus development plans and timing would be helpful. Thanks. Mirek Thanks a lot to everybody who already tested this! Please test the new version, any feedback much appreciated! Lennart -- Miroslav Grepl Senior Software Engineer, SELinux Solutions Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
Hi Orion
On Sat, Aug 1, 2015 at 2:36 PM, David Herrmann dh.herrm...@gmail.com wrote:
sendmsg(4, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\0\1\21\0\0\2\0\0\0\223\0\0\0\1\1o\0\25\0\0\0/org/freedesktop/DBus\0\0\0\6\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\2\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\3\1s\0\33\0\0\0UpdateActivationEnvironment\0\0\0\0\0\10\1g\0\5a{ss}\0\0\0\0\0\0,
168}, {4\21\0\0\0\0\0\0\22\0\0\0BASH_FUNC_module()\0\0)\0\0\0() { eval
`/usr/bin/modulecmd bash
You export a variable called 'BASH_FUNC_module()' (which is how bash
names its exported functions since the ShellShock updates). According
to POSIX, names of environment variables should only contain
[A-Za-z0-9_], which is what systemd enforces. Hence, systemd refuses
the trailing parantheses in this name.
Anyway, POSIX also explicitly says that applications should tolerate
any other character (except '='). This needs to be fixed in pid1.
This should now be fixed in -git [1]. We drop any variables that do
not conform to POSIX recommendations in UpdateActivationEnvironment().
This means, BASH_FUNC_module() will not end up in your activation
environment. But I assume that this is more or less the intended
behavior.
Next systemd update in rawhide will include this fix.
Thanks for the report!
David
[1] https://github.com/systemd/systemd/pull/858
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
Hi
On Sat, Aug 1, 2015 at 12:26 AM, Orion Poplawski or...@cora.nwra.com wrote:
On 07/31/2015 11:07 AM, David Herrmann wrote:
Hi
On Fri, Jul 31, 2015 at 6:47 PM, Orion Poplawski or...@cora.nwra.com wrote:
Cannot log into KDE with kdbus, I get:
$ cat .xsession-errors
startkde: Starting up...
startkde: Could not sync environment to dbus.
This is UpdateActivationEnvironment() failing. This call definitely
works and we use it on our machines. However, it returns an error if
the argument-array is empty. I fixed this in -git now [1]. It sounds
like you're hitting this. If the fix doesn't help, please let me know
(should be in rawhide by tomorrow).
Thanks a lot for the report!
David
[1]
https://github.com/systemd/systemd/commit/b2a0ac5e5b29c73ca7c0da23369a4769d5a91ddd
This still seems to be failing with systemd-224-1.fc24.x86_64
sendmsg(4, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\0\1\21\0\0\2\0\0\0\223\0\0\0\1\1o\0\25\0\0\0/org/freedesktop/DBus\0\0\0\6\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\2\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\3\1s\0\33\0\0\0UpdateActivationEnvironment\0\0\0\0\0\10\1g\0\5a{ss}\0\0\0\0\0\0,
168}, {4\21\0\0\0\0\0\0\22\0\0\0BASH_FUNC_module()\0\0)\0\0\0() { eval
`/usr/bin/modulecmd bash
You export a variable called 'BASH_FUNC_module()' (which is how bash
names its exported functions since the ShellShock updates). According
to POSIX, names of environment variables should only contain
[A-Za-z0-9_], which is what systemd enforces. Hence, systemd refuses
the trailing parantheses in this name.
Anyway, POSIX also explicitly says that applications should tolerate
any other character (except '='). This needs to be fixed in pid1.
Thanks
David
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On Sat, Aug 1, 2015 at 6:15 PM, Igor Gnatenko i.gnatenko.br...@gmail.com wrote: I've filled some bugs while I'm running fedora with kdbus and selinux in permissive mode. I've added kdbus to whiteboard for easy tracking them. https://bugzilla.redhat.com/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDbug_status=POSTbug_status=MODIFIEDbug_status=ON_DEVbug_status=ON_QAbug_status=VERIFIEDbug_status=RELEASE_PENDINGclassification=Fedoracomponent=selinux-policyemail1=i.gnatenko.brain%40gmail.comemailassigned_to1=1emailcc1=1emaillongdesc1=1emailqa_contact1=1emailreporter1=1emailtype1=exactlist_id=3686480product=Fedoraquery_format=advancedstatus_whiteboard=kdbusstatus_whiteboard_type=allwordssubstr Oops, I put my email into search. https://bugzilla.redhat.com/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDbug_status=POSTbug_status=MODIFIEDbug_status=ON_DEVbug_status=ON_QAbug_status=VERIFIEDbug_status=RELEASE_PENDINGclassification=Fedoracomponent=selinux-policylist_id=3686480product=Fedoraquery_format=advancedstatus_whiteboard=kdbusstatus_whiteboard_type=allwordssubstr -- valid link On Fri, Jul 31, 2015 at 1:35 PM, Lennart Poettering mzerq...@0pointer.de wrote: On Thu, 30.07.15 16:59, Orion Poplawski (or...@cora.nwra.com) wrote: On 07/30/2015 04:54 PM, Orion Poplawski wrote: 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: Also plenty of AVC denials. Looks like there's no label yet for the kdbus filesystem? Yes, I should have mentioned that: kdbus is not really known to the SELinux policy yet. Hence please also set SELinux to permissive mode or turn it off while testing kdbus for now. One of the reasons we added this to Rawhide is to make it easy to fix the policy now. Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- -Igor Gnatenko -- -Igor Gnatenko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
I've filled some bugs while I'm running fedora with kdbus and selinux in permissive mode. I've added kdbus to whiteboard for easy tracking them. https://bugzilla.redhat.com/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDbug_status=POSTbug_status=MODIFIEDbug_status=ON_DEVbug_status=ON_QAbug_status=VERIFIEDbug_status=RELEASE_PENDINGclassification=Fedoracomponent=selinux-policyemail1=i.gnatenko.brain%40gmail.comemailassigned_to1=1emailcc1=1emaillongdesc1=1emailqa_contact1=1emailreporter1=1emailtype1=exactlist_id=3686480product=Fedoraquery_format=advancedstatus_whiteboard=kdbusstatus_whiteboard_type=allwordssubstr On Fri, Jul 31, 2015 at 1:35 PM, Lennart Poettering mzerq...@0pointer.de wrote: On Thu, 30.07.15 16:59, Orion Poplawski (or...@cora.nwra.com) wrote: On 07/30/2015 04:54 PM, Orion Poplawski wrote: 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: Also plenty of AVC denials. Looks like there's no label yet for the kdbus filesystem? Yes, I should have mentioned that: kdbus is not really known to the SELinux policy yet. Hence please also set SELinux to permissive mode or turn it off while testing kdbus for now. One of the reasons we added this to Rawhide is to make it easy to fix the policy now. Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- -Igor Gnatenko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On 07/30/2015 05:15 PM, Josh Boyer wrote: On Thu, Jul 30, 2015 at 6:54 PM, Orion Poplawski or...@cora.nwra.com wrote: 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.00] 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.00] 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? Is the kdbus.ko.xz module in your initramfs? If it isn't, you probably need to rebuild it so that it is. josh Yup, dracut --force and a reboot cleared this up. Thanks. -- 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
Re: [HEADS-UP] Please test kdbus in Rawhide!
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.
This stuff is opt-in, and we are very keen on getting feedback and
testing for this. The version of kdbus in Rawhide we consider API
stable, there is a complete client side available now in systemd, with
a client API in sd-bus. Compatibility with good old dbus1 is provided
by the systemd-bus-proxy service.
The folks involved in kdbus development have been running this code on
their systems for more than half a year now. There were occasional
hiccups, but we fixed everything we ran into, and it works pretty well
now. Our focus was specifically on providing the best possible
compatibility with dbus1. Now we'd like to increase the testing
audience and added this to Rawhide because of this.
Cannot log into KDE with kdbus, I get:
$ cat .xsession-errors
startkde: Starting up...
startkde: Could not sync environment to dbus.
Code is:
# At this point all environment variables are set, let's send it to the DBus
session server to update the activation environment
/usr/libexec/ksyncdbusenv
if test $? -ne 0; then
# Startup error
echo 'startkde: Could not sync environment to dbus.' 12
test -n $ksplash_pid kill $ksplash_pid 2/dev/null
message Could not sync environment to dbus.
exit 1
fi
./plasma-workspace-5.3.2/startkde/ksyncdbusenv/ksyncdbusenv.cpp:
int main(int argc, char **argv)
{
QCoreApplication app(argc, argv);
QProcessEnvironment env = QProcessEnvironment::systemEnvironment();
EnvMap envMap;
for (const QString key : env.keys()) {
envMap.insert(key, env.value(key));
}
QDBusMessage msg =
QDBusMessage::createMethodCall(QStringLiteral(org.freedesktop.DBus),
QStringLiteral(/org/freedesktop/DBus),
QStringLiteral(org.freedesktop.DBus),
QStringLiteral(UpdateActivationEnvironment));
qDBusRegisterMetaTypeEnvMap();
msg.setArguments(QListQVariant({QVariant::fromValue(envMap)}));
QDBusPendingCall reply = QDBusConnection::sessionBus().asyncCall(msg);
reply.waitForFinished();
if (reply.isError()) {
qDebug() reply.error().name() reply.error().message();
}
return reply.isError() ? 1 : 0;
}
--
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
Re: [HEADS-UP] Please test kdbus in Rawhide!
On 07/30/2015 09:45 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Jul 30, 2015 at 04:54:18PM -0600, Orion Poplawski wrote:
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.00] 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.00] 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?
Josh answered that.
Getting duplicate requests for dbus-org.kde.kuiserver.service?
It would seem that there must be two dbus-1 service files with the
same Name= key. What does 'grep org.kde.kuiserver /usr/share/dbus-1/*/*' say?
Looks like it:
/usr/share/dbus-1/services/kf5_org.kde.kuiserver.service:Name=org.kde.kuiserver
/usr/share/dbus-1/services/org.kde.kuiserver.service:Name=org.kde.kuiserver
plasma-workspace-5.3.2-5.fc24.x86_64
kde-runtime-15.04.3-1.fc23.x86_64
Filed https://bugzilla.redhat.com/show_bug.cgi?id=1249157
[Hint: You can run the generator for debugging at any time with
mkdir /tmp/x; /usr/lib/systemd/systemd-dbus1-generator /tmp/{x,x,x}
Add SYSTEMD_LOG_LEVEL=debug or strace or similar for more detail ;) ]
Zbyszek
--
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
Re: [HEADS-UP] Please test kdbus in Rawhide!
Hi
On Fri, Jul 31, 2015 at 6:47 PM, Orion Poplawski or...@cora.nwra.com wrote:
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.
This stuff is opt-in, and we are very keen on getting feedback and
testing for this. The version of kdbus in Rawhide we consider API
stable, there is a complete client side available now in systemd, with
a client API in sd-bus. Compatibility with good old dbus1 is provided
by the systemd-bus-proxy service.
The folks involved in kdbus development have been running this code on
their systems for more than half a year now. There were occasional
hiccups, but we fixed everything we ran into, and it works pretty well
now. Our focus was specifically on providing the best possible
compatibility with dbus1. Now we'd like to increase the testing
audience and added this to Rawhide because of this.
Cannot log into KDE with kdbus, I get:
$ cat .xsession-errors
startkde: Starting up...
startkde: Could not sync environment to dbus.
This is UpdateActivationEnvironment() failing. This call definitely
works and we use it on our machines. However, it returns an error if
the argument-array is empty. I fixed this in -git now [1]. It sounds
like you're hitting this. If the fix doesn't help, please let me know
(should be in rawhide by tomorrow).
Thanks a lot for the report!
David
[1]
https://github.com/systemd/systemd/commit/b2a0ac5e5b29c73ca7c0da23369a4769d5a91ddd
Code is:
# At this point all environment variables are set, let's send it to the DBus
session server to update the activation environment
/usr/libexec/ksyncdbusenv
if test $? -ne 0; then
# Startup error
echo 'startkde: Could not sync environment to dbus.' 12
test -n $ksplash_pid kill $ksplash_pid 2/dev/null
message Could not sync environment to dbus.
exit 1
fi
./plasma-workspace-5.3.2/startkde/ksyncdbusenv/ksyncdbusenv.cpp:
int main(int argc, char **argv)
{
QCoreApplication app(argc, argv);
QProcessEnvironment env = QProcessEnvironment::systemEnvironment();
EnvMap envMap;
for (const QString key : env.keys()) {
envMap.insert(key, env.value(key));
}
QDBusMessage msg =
QDBusMessage::createMethodCall(QStringLiteral(org.freedesktop.DBus),
QStringLiteral(/org/freedesktop/DBus),
QStringLiteral(org.freedesktop.DBus),
QStringLiteral(UpdateActivationEnvironment));
qDBusRegisterMetaTypeEnvMap();
msg.setArguments(QListQVariant({QVariant::fromValue(envMap)}));
QDBusPendingCall reply = QDBusConnection::sessionBus().asyncCall(msg);
reply.waitForFinished();
if (reply.isError()) {
qDebug() reply.error().name() reply.error().message();
}
return reply.isError() ? 1 : 0;
}
--
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
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On Thu, 30.07.15 19:57, Lennart Poettering (mzerq...@0pointer.de) 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. Quick update: We have released a new version of systemd now with all bugs reported here fixed. It's also in Rawhide already, but it might not have hit all mirrors yet. To download it directly, please use: http://koji.fedoraproject.org/koji/buildinfo?buildID=674692 And please remember to turn selinux at least into permissive mode when using this, or even turn it off entirely while testing (kdbus=1 selinux=0 on the kernel command line). Thanks a lot to everybody who already tested this! Please test the new version, any feedback much appreciated! Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On 07/31/2015 11:07 AM, David Herrmann wrote:
Hi
On Fri, Jul 31, 2015 at 6:47 PM, Orion Poplawski or...@cora.nwra.com wrote:
Cannot log into KDE with kdbus, I get:
$ cat .xsession-errors
startkde: Starting up...
startkde: Could not sync environment to dbus.
This is UpdateActivationEnvironment() failing. This call definitely
works and we use it on our machines. However, it returns an error if
the argument-array is empty. I fixed this in -git now [1]. It sounds
like you're hitting this. If the fix doesn't help, please let me know
(should be in rawhide by tomorrow).
Thanks a lot for the report!
David
[1]
https://github.com/systemd/systemd/commit/b2a0ac5e5b29c73ca7c0da23369a4769d5a91ddd
This still seems to be failing with systemd-224-1.fc24.x86_64
sendmsg(4, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\0\1\21\0\0\2\0\0\0\223\0\0\0\1\1o\0\25\0\0\0/org/freedesktop/DBus\0\0\0\6\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\2\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\3\1s\0\33\0\0\0UpdateActivationEnvironment\0\0\0\0\0\10\1g\0\5a{ss}\0\0\0\0\0\0,
168}, {4\21\0\0\0\0\0\0\22\0\0\0BASH_FUNC_module()\0\0)\0\0\0() { eval
`/usr/bin/modulecmd bash
$*`\n}\0\0\0\n\0\0\0CCACHE_DIR\0\0\25\0\0\0/scratch/orion/ccache\0\0\0\0\0\0\0\16\0\0\0COBBLER_SERVER\0\0\25\0\0\0cobbler.cora.nwra.com\0\0\0\7\0\0\0CVSROOT\0\20\0\0\0/data/sw1/cvsrep\0\0\0\0\0\0\0\0\30\0\0\0DBUS_SESSION_BUS_ADDRESS\0\0\0\0D\0\0\0kernel:path=/sys/fs/kdbus/1744-user/bus;unix:path=/run/user/1744/bus\0\0\0\0\0\0\0\0\7\0\0\0DISPLAY\0\16\0\0\0localhost:11.0\0\0\6\0\0\0EDITOR\0\0\2\0\0\0vi\0\0\0\0\0\0\10\0\0\0GDL_PATH\0\0\0\0O\0\0\0+/opt/local/cmsvlib:+/usr/share/gnudatalanguage/lib:+/opt/local/itt/idl/idl/lib\0\0\0\0\0\v\0\0\0HISTCONTROL\0\n\0\0\0ignoredups\0\0\10\0\0\0HISTSIZE\0\0\0\0\4\0\0\0001000\0\0\0\0\0\0\0\0\4\0\0\0HOME\0\0\0\0\v\0\0\0/home/orion\0\0\0\0\0\4\0\0\0HOST\0\0\0\0\t\0\0\0vmrawhide\0\0\0\0\0\0\0\10\0\0\0HOSTNAME\0\0\0\0\27\0\0\0vmrawhide.cora.nwra.com\0\0\0\0\0\7\0\0\0IDL_DIR\0\25\0\0\0/nfs/local/exelis/idl\0\0\0\f\0\0\0IDL_DLM_PATH\0\0\0\0#\0\0\0/nfs/local/gpulib/lib:IDL_DEFAULT\0\0\0\0\0\10\0\0\0IDL_PATH\0\0\0\0001\0\0\0+/home/orion/idl:+/nfs/local/g
p
ulib:IDL_DEFAULT\0\0\0\v\0\0\0IDL_STARTUP\0\22\0\0\0/home/orion/.idlrc\0\0\23\0\0\0JITC_PROCESSOR_TYPE\0\1\0\0\0006\0\0\0\7\0\0\0KDEDIRS\0\4\0\0\0/usr\0\0\0\0\4\0\0\0LANG\0\0\0\0\v\0\0\0en_US.UTF-8\0\0\0\0\0\10\0\0\0LANGUAGE\0\0\0\0\0\0\0\0\0\0\0\0\10\0\0\0LESSOPEN\0\0\0\0\31\0\0\0||/usr/bin/l...,
4412}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 4580
recvmsg(4, {msg_name(0)=NULL,
msg_iov(1)=[{l\3\1\1\25\0\0\0\377\377\377\377_\0\0\0\5\1u\0\2\0\0\0\4\1s\0\0\0\0org.freedesktop.DBus.Error.InvalidArgs\0\0\7\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\10\1g\0\1s\0\0\20\0\0\0Invalid
argument\0, 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC},
MSG_CMSG_CLOEXEC) = 133
PS - I'm off network starting now until next week.
--
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
Re: [HEADS-UP] Please test kdbus in Rawhide!
On 30.07.2015 20:05, Stephen Gallagher wrote: On Thu, 2015-07-30 at 19:57 +0200, 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. This stuff is opt-in, and we are very keen on getting feedback and testing for this. The version of kdbus in Rawhide we consider API stable, there is a complete client side available now in systemd, with a client API in sd-bus. Compatibility with good old dbus1 is provided by the systemd-bus-proxy service. The folks involved in kdbus development have been running this code on their systems for more than half a year now. There were occasional hiccups, but we fixed everything we ran into, and it works pretty well now. Our focus was specifically on providing the best possible compatibility with dbus1. Now we'd like to increase the testing audience and added this to Rawhide because of this. Further information about kdbus and how to get started you may find here: http://www.freedesktop.org/wiki/Software/systemd/kdbus/ We'd very thankful for every Fedora developer testing this and providing bug reports! Any feedback is highly appreciated. Also, should you attend our upcoming conference, we might return the favour by buying you a beer or two: https://systemd.events/ Thank you, Lennart For folks not keen to jump headfirst into Rawhide, is it expected that this should work on Fedora 23 or Fedora 22 if one installs only the kernel and systemd packages from Rawhide? That might make people more comfortable trying it out (and get you more feedback), if so. You want to install at least systemd-223-2.git65c85ef.fc24 to get the latest fixes. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On Thu, 30.07.15 16:59, Orion Poplawski (or...@cora.nwra.com) wrote: On 07/30/2015 04:54 PM, Orion Poplawski wrote: 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: Also plenty of AVC denials. Looks like there's no label yet for the kdbus filesystem? Yes, I should have mentioned that: kdbus is not really known to the SELinux policy yet. Hence please also set SELinux to permissive mode or turn it off while testing kdbus for now. One of the reasons we added this to Rawhide is to make it easy to fix the policy now. Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On Thu, 30.07.15 14:20, Josh Boyer (jwbo...@fedoraproject.org) wrote: For folks not keen to jump headfirst into Rawhide, is it expected that this should work on Fedora 23 or Fedora 22 if one installs only the kernel and systemd packages from Rawhide? That might make people more comfortable trying it out (and get you more feedback), if so. You'll probably only need the rawhide kernel. IIRC, the systemd package was kdbus ready before the branch was created. Actually, most of the fixes we made in the past weeks were actually to the userspace components, not to the kernel part. Hence you do need both the new kernel and the new systemd from rawhide. Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On Thu, 2015-07-30 at 18:50 +, Zbigniew Jędrzejewski-Szmek wrote: On Thu, Jul 30, 2015 at 02:40:37PM -0400, Stephen Gallagher wrote: OK, I spun up a Fedora Server 23 Alpha TC2 system and installed the Rawhide kernel, then rebooted with kdbus=1 I then tried to run 'rolectl list roles', which returned Rolekit is not running. So it failed to provide D-BUS activation functionality, which is problematic. I see the same bug on rawhide. When I manually ran the service, D-BUS communication between the client and the daemon seems to be working properly. Where is the proper place to file a bug? https://bugzilla.redhat.com/enter_bug.cgi?product=Fedoracomponent=sy stemdversion=rawhideshort_desc=kdbus:+ or https://github.com/systemd/systemd/issues, whatever works better for you. Zbyszek https://bugzilla.redhat.com/show_bug.cgi?id=1248783 - kdbus: dbus activation of org.fedoraproject.rolekit1.service failed signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
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.00] 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.00] 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
Re: [HEADS-UP] Please test kdbus in Rawhide!
On 07/30/2015 04:54 PM, Orion Poplawski wrote:
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:
Also plenty of AVC denials. Looks like there's no label yet for the kdbus
filesystem?
Jul 30 16:31:33 vmrawhide audit: AVC avc: denied { read write } for pid=698
comm=systemd-logind name=bus dev=kdbusfs ino=4
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:31:33 vmrawhide audit: AVC avc: denied { open } for pid=698
comm=systemd-logind path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:31:33 vmrawhide audit: AVC avc: denied { ioctl } for pid=698
comm=systemd-logind path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:31:34 vmrawhide audit: AVC avc: denied { ioctl } for pid=698
comm=systemd-logind path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:31:40 vmrawhide audit: AVC avc: denied { ioctl } for pid=698
comm=systemd-logind path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:31:45 vmrawhide audit: AVC avc: denied { ioctl } for pid=698
comm=systemd-logind path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:31:45 vmrawhide audit: AVC avc: denied { ioctl } for pid=698
comm=systemd-logind path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:31:45 vmrawhide audit: AVC avc: denied { ioctl } for pid=698
comm=systemd-logind path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:31:49 vmrawhide audit: AVC avc: denied { read write } for
pid=1184 comm=sddm-helper name=bus dev=kdbusfs ino=4
scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:31:49 vmrawhide audit: AVC avc: denied { open } for pid=1184
comm=sddm-helper path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:31:49 vmrawhide audit: AVC avc: denied { ioctl } for pid=1184
comm=sddm-helper path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:31:49 vmrawhide audit: AVC avc: denied { ioctl } for pid=698
comm=systemd-logind path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:33:03 vmrawhide audit: AVC avc: denied { ioctl } for pid=698
comm=systemd-logind path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:41:28 vmrawhide audit: AVC avc: denied { ioctl } for pid=698
comm=systemd-logind path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:47:02 vmrawhide audit: AVC avc: denied { read write } for
pid=5541 comm=sshd name=bus dev=kdbusfs ino=4
scontext=system_u:system_r:sshd_t:s0-s0:c0.c1023
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:47:02 vmrawhide audit: AVC avc: denied { open } for pid=5541
comm=sshd path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
scontext=system_u:system_r:sshd_t:s0-s0:c0.c1023
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
Jul 30 16:47:02 vmrawhide audit: AVC avc: denied { ioctl } for pid=5541
comm=sshd path=/sys/fs/kdbus/0-system/bus dev=kdbusfs ino=4
Re: [HEADS-UP] Please test kdbus in Rawhide!
On Thu, Jul 30, 2015 at 6:54 PM, Orion Poplawski or...@cora.nwra.com wrote: 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.00] 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.00] 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? Is the kdbus.ko.xz module in your initramfs? If it isn't, you probably need to rebuild it so that it is. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On Thu, Jul 30, 2015 at 04:54:18PM -0600, Orion Poplawski wrote:
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.00] 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.00] 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?
Josh answered that.
Getting duplicate requests for dbus-org.kde.kuiserver.service?
It would seem that there must be two dbus-1 service files with the
same Name= key. What does 'grep org.kde.kuiserver /usr/share/dbus-1/*/*' say?
[Hint: You can run the generator for debugging at any time with
mkdir /tmp/x; /usr/lib/systemd/systemd-dbus1-generator /tmp/{x,x,x}
Add SYSTEMD_LOG_LEVEL=debug or strace or similar for more detail ;) ]
Zbyszek
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On Thu, Jul 30, 2015 at 02:40:37PM -0400, Stephen Gallagher wrote: OK, I spun up a Fedora Server 23 Alpha TC2 system and installed the Rawhide kernel, then rebooted with kdbus=1 I then tried to run 'rolectl list roles', which returned Rolekit is not running. So it failed to provide D-BUS activation functionality, which is problematic. I see the same bug on rawhide. When I manually ran the service, D-BUS communication between the client and the daemon seems to be working properly. Where is the proper place to file a bug? https://bugzilla.redhat.com/enter_bug.cgi?product=Fedoracomponent=systemdversion=rawhideshort_desc=kdbus:+ or https://github.com/systemd/systemd/issues, whatever works better for you. Zbyszek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On Thu, 2015-07-30 at 19:57 +0200, 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. This stuff is opt-in, and we are very keen on getting feedback and testing for this. The version of kdbus in Rawhide we consider API stable, there is a complete client side available now in systemd, with a client API in sd-bus. Compatibility with good old dbus1 is provided by the systemd-bus-proxy service. The folks involved in kdbus development have been running this code on their systems for more than half a year now. There were occasional hiccups, but we fixed everything we ran into, and it works pretty well now. Our focus was specifically on providing the best possible compatibility with dbus1. Now we'd like to increase the testing audience and added this to Rawhide because of this. Further information about kdbus and how to get started you may find here: http://www.freedesktop.org/wiki/Software/systemd/kdbus/ We'd very thankful for every Fedora developer testing this and providing bug reports! Any feedback is highly appreciated. Also, should you attend our upcoming conference, we might return the favour by buying you a beer or two: https://systemd.events/ Thank you, Lennart OK, I spun up a Fedora Server 23 Alpha TC2 system and installed the Rawhide kernel, then rebooted with kdbus=1 I then tried to run 'rolectl list roles', which returned Rolekit is not running. So it failed to provide D-BUS activation functionality, which is problematic. When I manually ran the service, D-BUS communication between the client and the daemon seems to be working properly. Where is the proper place to file a bug? signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On Thu, Jul 30, 2015 at 2:05 PM, Stephen Gallagher sgall...@redhat.com wrote: On Thu, 2015-07-30 at 19:57 +0200, 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. This stuff is opt-in, and we are very keen on getting feedback and testing for this. The version of kdbus in Rawhide we consider API stable, there is a complete client side available now in systemd, with a client API in sd-bus. Compatibility with good old dbus1 is provided by the systemd-bus-proxy service. The folks involved in kdbus development have been running this code on their systems for more than half a year now. There were occasional hiccups, but we fixed everything we ran into, and it works pretty well now. Our focus was specifically on providing the best possible compatibility with dbus1. Now we'd like to increase the testing audience and added this to Rawhide because of this. Further information about kdbus and how to get started you may find here: http://www.freedesktop.org/wiki/Software/systemd/kdbus/ We'd very thankful for every Fedora developer testing this and providing bug reports! Any feedback is highly appreciated. Also, should you attend our upcoming conference, we might return the favour by buying you a beer or two: https://systemd.events/ Thank you, Lennart For folks not keen to jump headfirst into Rawhide, is it expected that this should work on Fedora 23 or Fedora 22 if one installs only the kernel and systemd packages from Rawhide? That might make people more comfortable trying it out (and get you more feedback), if so. You'll probably only need the rawhide kernel. IIRC, the systemd package was kdbus ready before the branch was created. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On Thu, Jul 30, 2015 at 11:20 AM, Josh Boyer jwbo...@fedoraproject.org wrote: On Thu, Jul 30, 2015 at 2:05 PM, Stephen Gallagher sgall...@redhat.com wrote: On Thu, 2015-07-30 at 19:57 +0200, 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. This stuff is opt-in, and we are very keen on getting feedback and testing for this. The version of kdbus in Rawhide we consider API stable, there is a complete client side available now in systemd, with a client API in sd-bus. Compatibility with good old dbus1 is provided by the systemd-bus-proxy service. The folks involved in kdbus development have been running this code on their systems for more than half a year now. There were occasional hiccups, but we fixed everything we ran into, and it works pretty well now. Our focus was specifically on providing the best possible compatibility with dbus1. Now we'd like to increase the testing audience and added this to Rawhide because of this. Further information about kdbus and how to get started you may find here: http://www.freedesktop.org/wiki/Software/systemd/kdbus/ We'd very thankful for every Fedora developer testing this and providing bug reports! Any feedback is highly appreciated. Also, should you attend our upcoming conference, we might return the favour by buying you a beer or two: https://systemd.events/ Thank you, Lennart For folks not keen to jump headfirst into Rawhide, is it expected that this should work on Fedora 23 or Fedora 22 if one installs only the kernel and systemd packages from Rawhide? That might make people more comfortable trying it out (and get you more feedback), if so. You'll probably only need the rawhide kernel. IIRC, the systemd package was kdbus ready before the branch was created. The last time I tried this (maybe a month ago in Rawhide), booting with kdbus=1 hung very quickly. I was told that it needed newer systemd to work, so I'd be a bit surprised if F22 is reliable. --Andy -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
Hello Andrew, Yes I'm Real. To prove I'm real first off.. You are Development discussions related to Fedora and your mail Id devel@lists.fedoraproject.org I was just taking a quick shower and I heard my phone vibrate, my hair isnt even close to being dry yet but I wanted to quickly check my email to see if it was you writing me back. I guess since you responded you are not a faker haha, that is a big relief. Not sure if you were wanting to get together tonight, tomorrow ..or maybe wait until the weekend? I am not going to lie though I was really hoping to get some as soon as possible.. All you have do is verify on this website HERE http://www.bcmeetnow.com/userms/olivia/ where I am a member and do a safety verification. It only costs a dollar and just takes a sec. My cell number is on there and I have some other photos on there too. Get my cell number and give me a text or call me. Let's make this happen.. I have lots of free time. call me now! Sorry if it seems like I'm being a bitch and making you work too hard, but I have to look out for my own safety. There are tons of weirdos out there and I just want to have a good time. Hope you understand cause I really want to meet you.. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On Thu, Jul 30, 2015 at 12:05 PM, Stephen Gallagher sgall...@redhat.com wrote: For folks not keen to jump headfirst into Rawhide, is it expected that this should work on Fedora 23 or Fedora 22 if one installs only the kernel and systemd packages from Rawhide? That might make people more comfortable trying it out (and get you more feedback), if so. I think this is in systemd 222 which is in Fedora 23, because kdbus is API stable in systemd 221. ? -- Chris Murphy -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[HEADS-UP] Please test kdbus in Rawhide!
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. This stuff is opt-in, and we are very keen on getting feedback and testing for this. The version of kdbus in Rawhide we consider API stable, there is a complete client side available now in systemd, with a client API in sd-bus. Compatibility with good old dbus1 is provided by the systemd-bus-proxy service. The folks involved in kdbus development have been running this code on their systems for more than half a year now. There were occasional hiccups, but we fixed everything we ran into, and it works pretty well now. Our focus was specifically on providing the best possible compatibility with dbus1. Now we'd like to increase the testing audience and added this to Rawhide because of this. Further information about kdbus and how to get started you may find here: http://www.freedesktop.org/wiki/Software/systemd/kdbus/ We'd very thankful for every Fedora developer testing this and providing bug reports! Any feedback is highly appreciated. Also, should you attend our upcoming conference, we might return the favour by buying you a beer or two: https://systemd.events/ Thank you, Lennart -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [HEADS-UP] Please test kdbus in Rawhide!
On Thu, 2015-07-30 at 19:57 +0200, 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. This stuff is opt-in, and we are very keen on getting feedback and testing for this. The version of kdbus in Rawhide we consider API stable, there is a complete client side available now in systemd, with a client API in sd-bus. Compatibility with good old dbus1 is provided by the systemd-bus-proxy service. The folks involved in kdbus development have been running this code on their systems for more than half a year now. There were occasional hiccups, but we fixed everything we ran into, and it works pretty well now. Our focus was specifically on providing the best possible compatibility with dbus1. Now we'd like to increase the testing audience and added this to Rawhide because of this. Further information about kdbus and how to get started you may find here: http://www.freedesktop.org/wiki/Software/systemd/kdbus/ We'd very thankful for every Fedora developer testing this and providing bug reports! Any feedback is highly appreciated. Also, should you attend our upcoming conference, we might return the favour by buying you a beer or two: https://systemd.events/ Thank you, Lennart For folks not keen to jump headfirst into Rawhide, is it expected that this should work on Fedora 23 or Fedora 22 if one installs only the kernel and systemd packages from Rawhide? That might make people more comfortable trying it out (and get you more feedback), if so. signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
