Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: On a RHEL 8 system with Wayland disabled in /etc/gdm/custom.conf, the X Pulse Audio properties are not published to the X server.
To see the pulseaudio properties, run the command ‘xprop -root | grep PULSE’. The properties that we need are PULSE_SERVER, which points to the socket, and PULSE_COOKIE, which is the hex dump of the file that is usually stored in ~/.config/pulse/cookie. These properties get published to the X server by loading a module called module-x11-publish. On EL8, this is done in the script /usr/bin/start-pulseaudio-x11. After logging in, you can see the list of loaded modules by running the command ‘pactl list short modules’. What I find on my systems is module-x11-publish is not in the list.
The pulseaudio daemon isn’t really started by /usr/bin/start-pulseaudio-x11 on RHEL8. It’s started as a user service. The start-pulseaudio-x11 process is started by an autostart script that is run after the service starts. The failure to load module-x11-publish can be seen by looking at the status of the service.
I looked around for this error and found this link
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593746
The bug says there is a problem with Xauthority. Some version of pulseaudio is expecting to find it in ~/.Xauthority. I ran the command ‘ln -s $XAUTHORITY ~/.Xauthority’ and rebooted. The start-pulseaudio-x11 script worked and I was able to see module-x11-publish when I ran ‘pactl list modules’
Version-Release number of selected component (if applicable):
pulseaudio-module-x11-11.1-22.el8.x86_64
How reproducible: consistently.
Steps to Reproduce:
1. login to Xorg Gnome session
2. run the command xprop -root | grep PULSE
Actual results:
no matches
Expected results:
PULSE_COOKIE(STRING) = ...
PULSE_SERVER(STRING) = ...
PULSE_SESSION_ID(STRING) = ...
PULSE_ID(STRING) = ...
Additional info:
It seems debian choose to add a new (local) xorg script instead. Any reason we should not do
that as well? I also reads xorg doesn't want to fix this (or is it even their problem)?
I'm ok with the patch in general. Even if this is maybe not exactly the perfect fix, it's
not very complicated and only temporarily.
(In reply to Jeff Burrell from comment #16)
> Can anyone tell me what kernel version to look for this fix in?
It's not in a kernel update but in an update of the pulseaudio package (pulseaudio-11.1-23.el8)
that will be in 8.1.0 if all goes well.
I think I can make the rpms available to you already, if you want to test it.
The session id comes from another environment variable (XDG_SESSION_ID) not available
at startup. It's an optional variable, it should not cause problems.
Greg, does HP require this variable in the X root properties as well or is it enough to
get this from the environment variable?
(In reply to hprhelbugzilla from comment #22)
> The only variables that are known to be requires are PULSE_COOKIE and
> PULSE_SERVER.
Thanks moving to verified.
(In reply to Jeff Burrell from comment #24)
> We'd like to test this. Can someone make the pulseaudio package
> (pulseaudio-11.1-23.el8)available to us, please?
Can I email them to you on the email in this bug?
Wim,
The initial testing has been successful. The RGS engineer using the updated packages reports that the audio properties they needed are, indeed, now published in the X server. They'll be doing more testing but good results so far.
Jeff
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:3508
Comment 30Red Hat Bugzilla
2023-09-14 05:30:45 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days