Summary: | media-sound/pulseaudio-2.99.3 USE=-system-wide - * Starting D-BUS system messagebus ... Unknown username "pulse" in message bus configuration file | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Francesco Turco <fturco> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | adaptee, alex, alexander, balint, oldium.pro, poncho, sound, staff, vikraman, wfdawson |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Updated ebuild to fix the non-system-wide dbus usage
Patch to remove installation of dbus configuration in non-system-wide mode patch of the original ebuild - to see the changes |
Description
Francesco Turco
2012-12-18 10:30:37 UTC
The same happens for me as well with media-sound/pulseaudio-3.0 The /etc/dbus-1/system.d/pulseaudio-system.conf file should not be installed with USE="-system-wide" according to the comment in the .conf file. the build system is somehow broken, pulse, pulse-access groups supposed to be created only if system-wide flag used. This flag is profile masked, despite this /etc/dbus-1/system.d/pulseaudio-system.conf is installed. Removing 'if use systemd-wide' in ebuild, makes dbus behave normally. Obviosuly it looks like wrong fix. *** Bug 481504 has been marked as a duplicate of this bug. *** Still an issue with pulseaudio-4.0. Devs please look into this, it should be trivial to fix. Created attachment 366714 [details]
Updated ebuild to fix the non-system-wide dbus usage
Created attachment 366716 [details, diff]
Patch to remove installation of dbus configuration in non-system-wide mode
Created attachment 366718 [details, diff]
patch of the original ebuild - to see the changes
I faced the same problem, so I tried to provide a fix - see attachments. I used the latest multilib ebuild and tested it on amd64 (only 64bit version - not multilib actually). use system-wide || rm "${ED}"/etc/dbus-1/system.d/pulseaudio-system.conf If nobody objects, I will commit it. (In reply to Vikraman from comment #9) > use system-wide || rm "${ED}"/etc/dbus-1/system.d/pulseaudio-system.conf That looks good. Please also remove line "# Create the state directory" and the following one (see my patch) - it just does nothing and is only confusing (remainder from previous ebuild versions). any updates on this? Fixed in 4.99.4 sorry, but this only 4.99.4 version, which is not fixed for older (and stable) ebuilds, this bug is still valid for these. (In reply to Oleg from comment #13) > sorry, but this only 4.99.4 version, which is not fixed for older (and > stable) ebuilds, this bug is still valid for these. Of course. Like almost all bugfixes in Gentoo. The issue gets fixed in the latest ~arch ebuild, and some time later the latest ~arch ebuild will be marked as stable. If you want the latest bugfixes without waiting - and the latest bugs too! - then set unstable ACCEPT_KEYWORDS in your make.conf Sorry, this is unacceptable policy, also there is no such policy in Gentoo that forcing user to switch to unstable branch, just because it's fixed only for unstable ebuilds. Stable pusleaudio and stable dbus is affected by this bug and it's clear fix for these. (In reply to Oleg from comment #15) > Sorry, this is unacceptable policy, also there is no such policy in Gentoo > that forcing user to switch to unstable branch, just because it's fixed only > for unstable ebuilds. Stable pusleaudio and stable dbus is affected by this > bug and it's clear fix for these. Nobody is forcing you to switch to unstable. But there *is* a policy that stable ebuilds normally get only cosmetic/stylistic changes (and preferably even those are kept to a minimum). Bugs are fixed in ~arch. Lots of ~arch users immediately install the new ebuild, and if the bugfix was wrong or made things worse, they will report the problem. Some days or weeks later, when the maintainer is confident that the time is right, he asks for an unstable ebuild with the fix to be stabilized, and the stabilization process is handled by arch teams. This has always been the process. In fact, this is reason why stable and unstable keywords exist. I apologize for delivering this lecture, but since you seem to be a developer for a Gentoo-derived distro, I think it's important to clear up any misconceptions you might have about the Gentoo development process works. (In reply to Alexandre Rostovtsev from comment #16) > stable ebuilds normally get only cosmetic/stylistic changes Better wording: changes which clearly will not affect what gets installed/modified on the user's filesystem. users don't need any lectures, i know what Gentoo policy about stable is, and it's horribly wrong policy. No commentso this. Should I mention that Gentoo is deliberately cheating on system-wide usage, when it's clearly said NOT to use by upstream. If Gentoo does so, please, make it working on ALL ebuilds. |