the recent availability of dbus-0.6*, hald 0.5* has broken some of the media management functionality in newly installed and existing systems here. Working still are dvds and audio cds, which play as expected when choosing play from the media icon. broken is the ability to mount and view the contents of a mass storage device or data cd/dvd. reverting to dbus-0.23.4* and hal-0.4.8 resolves the problem, but leaves gnome-vfs wanting pmount and the newer packages, which is why the newer packages were made stable. is there documentation available describing the change and what must be done, or is there some simple configuration necessary for these packages to function correctly in kde 3.4.3?
As far as I know these packages CAN'T function correctly in kde 3.4.x. You have to either upgrate to kde 3.5 or downgrade dbus and hal. I think it should be added at least a warning in the dbus and hal ebuilds about this problem.
i read this while researching the problem: http://bugs.gentoo.org/show_bug.cgi?id=105553
Created attachment 81543 [details] sys-apps/dbus-0.60-r5.ebuild
Created attachment 81544 [details] ChangeLog
updated ebuild, error message added.
This is interesting. Packages are marked as stable when they will break a another very common major package (KDE in this case). I am not sure I understand. Maybe someone can explain to me why dbus 0.60 marked as stable when it breaks the stable version of KDE? I think adding a warning to the ebuild does not do much good. Many users will be getting this version of dbus as part of an emerge world. If KDE <3.5 is installed on the machine then the dbus 0.60 ebuild should exit not just flash an error message on the screen.
My sentiments exactly. Last month I began the lengthly process of updating my clients to Gentoo's unstable kde 3.5. The availability of 3.5 in the stable software branch would clean things up nicely.
The reason is other packages depended on it. It would have held back Gnome 2.14 and several other packages. The API is no longer stable or security and is not supported. So we dropped the old one. The KDE team was asked to look at it and consider it but I guess that their comments either didn't make it to the hands of the people doing the stablizing or they didn't make any.
I agree that is was very important to allow these packages to go to the stable branch, but what has been stopping kde 3.5 from also going this route? After months of using it, I still believe it to be more stable than 3.4. I don't believe there could be security issues with dbus 0.23, hal 0.4.7, as they are still available as stable packages in portage. These versions should be removed altogether if there are concerns.
No idea why this bug was not closed ages ago.. But it's been fixed.
