The current dbus in stable gentoo is fairly dated, even by the permissive standards. I've been testing this on a few systems, and have not noticed any negative effects. Reproducible: Always
DBus 1.3.X is a development version. The next stable release will be 1.4. Are you sure in mark DBus 1.3 as stable is gentoo?
All, what is the status of this,will there be a stable 1.3.x? Thanks, William
This was filed while 1.2.x wasn't actively being bumped. Now that 1.2.20 is in-tree, perhaps it makes sense to focus on this as the stable candidate? 1.2.20 is their latest stable release, while 1.3.0 is still considered development. Downgrading to 1.2.20 seems to work great here.
Correct - 1.3.x is the development version, and was only added to the tree to ease some of the security issue pains. 1.2.20 will be the one that should go stable, alas, it has only been in the tree for a few days.
(In reply to comment #4) > Correct - 1.3.x is the development version, and was only added to the tree to > ease some of the security issue pains. 1.2.20 will be the one that should go > stable, alas, it has only been in the tree for a few days. > I can't spot any bugs that have popped up from 1.2.20 - any thoughts on stablizing this one?
I'd like to talk with Doug (Cardoe) about it first - the issue is really, that 1.3.x is in the tree, as ~ as is this one - most people have moved on to 1.3.x, so I'm not sure how much testing this has gotten - I use it on 4 different architectures (x86, ppc, amd64, arm), but only with Gnome and not with NetworkManager/wpa_supplicant (this one is a biggie) and not with KDE or anything XFCEish - it has been 30 days, true, I'm just not sure its gotten the testing it needs.
(In reply to comment #6) > I'd like to talk with Doug (Cardoe) about it first - the issue is really, that > 1.3.x is in the tree, as ~ as is this one - most people have moved on to 1.3.x, > so I'm not sure how much testing this has gotten - I use it on 4 different > architectures (x86, ppc, amd64, arm), but only with Gnome and not with > NetworkManager/wpa_supplicant (this one is a biggie) and not with KDE or > anything XFCEish - it has been 30 days, true, I'm just not sure its gotten the > testing it needs. > Like I discussed with Steev off Bugzilla, I'd tend to agree here. Can we have some confirmation that all the various desktop users are not affected by anything?
It was suggested on IRC that the 1.2.22 bump be done (which watches config dirs for changes so you don't need to reload dbus), and then the 1.3 series masked so that 1.2* gets testing. 30 days later, we can stabilize 1.2.22. afaik, there's only two packages in-tree that specifically depend on >=dbus-1.3; net-misc/connman and net-misc/ofono (a dep of connman). I doubt anyone uses connman; so IMO it can be masked alongwith dbus-1.3 (after consulting dagger [the maintainer] of course).
Arches, please stable sys-apps/dbus-1.2.24
Arches, please stable sys-apps/dbus-1.2.24 (Improved message by actually adding the arches this time!)
x86 stable
amd64 stable
ppc stable
sys-apps/dbus-1.2.24 is NOT STABLE. After upgrading to dbus-1.2.24 xfdesktop will not start on XFCE4 and USB stick will not mount automatically. Downgrading to dbus-1.2.3-r1 and now everything is working.
Ther is a problem with /etc/dbus-1/session.conf: Everything with fds has to be commented out/erased.
ppc64 stable
alpha/arm/ia64/s390/sh/sparc stable, closing