I'd *really* like to be able to enable qt4 dbus bindings for FC-5 (and allow folks to start playing with kde4 there), but that requires (at least) dbus-0.62 (or so says qt4's %configure scriptlet)
FYI, I have built and installed D-Bus 0.62 for FC5 (replacing the official 0.61 RPM) and I didn't encounter any issues with it. (I based my specfile off the official one.)
Created attachment 137670 [details] patch to export DBUS_SESSION_BUS_PID in the "run another program" case I think we'll also need something like the attached patch, because KDE 4 (or QDBus?) expects DBUS_SESSION_BUS_PID to be set. (At least, that's what the startkde script claims.) This patch ensures that this will be set in the X11 session started through: /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients from the scripts in /etc/X11/xinit. (The goal is to make KDE 4 apps in non-KDE-4 sessions work.) Is this patch acceptable? (If so, can it go upstream?) Or is it wrong for KDE 4 to expect this to be set?
It really should not rely on the PID.
Davidz, can you update FC5 when you get a chance? This looks like a good reason for an update. Note, if Qt4 stops working with 0.62 we won't be able to update anymore.
Oh, by the way, please don't take the DBUS_SESSION_BUS_PID issue as a blocker for the upgrade, the 0.62 upgrade alone (without that patch) should be enough to get QDBus (and thus the KDE 4 snapshots) to work, the environment variable can always be set by hand when needed. > Note, if Qt4 stops working with 0.62 we won't be able to update anymore. Understood. I've seen the amount of fixes which were needed for newer versions of D-Bus in the Rawhide reports, so this is not a surprise to me.
Comment on attachment 137670 [details] patch to export DBUS_SESSION_BUS_PID in the "run another program" case I've looked into the Qt 4.2 D-Bus binding and the KDE 4 SVN: exporting the PID doesn't seem to be actually needed after all, I don't see it used anywhere. So the patch is probably safe to ignore, we only need the update. :-)
ping, it's been over a month...
ping, another 2 weeks. Anyone out there? echo... echo... echo...
Sorry, davidz and I have been busy swapping positions and getting running in our respective rolls. Give us another week to get this in, there are some bugfixes I would like to backport and it doesn't make sense to do two D-Bus releases since they require a reboot pre 1.0.
Thanks John.
dbus-0.62 has been pushed to FC-5 (and surely FC>5 too). dbus-qt should be upgraded, know, so that yum can upgrade everything: because dbus-qt has "Requires: dbus-%{version}".
yep, dbus-qt is (re)building now.
And what about qt4-dbus?
Oh, scratch that, I forgot it's part of the main qt4 package, not a subpackage, and I see you enabled it already.
update is in the wild, closing -> NEXTRELEASE.
Sorry for being pedantic, but IMHO this should be closed as ERRATA, not NEXTRELEASE. ;-)