Bug 1723065

Summary: PULSE_SERVER and PULSE_COOKIE properties are not published to the X server
Product: Red Hat Enterprise Linux 8 Reporter: Greg Hughes <greg.hughes>
Component: pulseaudioAssignee: Wim Taymans <wtaymans>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 8.1CC: csoriano, desktop-qa-list, hprhelbugzilla, jeff.burrell, jkachuck, jkoten, jshortt, mknutson, tpelka, wchadwic, wtaymans
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: pulseaudio-11.1-23.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 21:27:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1654309, 1699081, 1710589, 1719385    

Description Greg Hughes 2019-06-22 16:07:58 UTC
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:

Comment 1 Jeff Burrell 2019-07-17 16:38:07 UTC
Any updates on this since we're approaching the 8.1 beta season?

Comment 2 Wim Taymans 2019-07-19 07:57:04 UTC
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.

Comment 6 Jeff Burrell 2019-09-06 19:34:19 UTC
FYI:  This issue has not been addressed in SS2(-128).  Are there plans to include the debian solution?

Comment 16 Jeff Burrell 2019-09-13 15:26:22 UTC
Can anyone tell me what kernel version to look for this fix in?

Comment 17 Wim Taymans 2019-09-13 15:49:56 UTC
(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.

Comment 18 Jeff Burrell 2019-09-13 16:06:55 UTC
Yes, please do.  We'll test the updated package.

Comment 20 Tomas Pelka 2019-09-16 13:21:11 UTC
I can see 

PULSE_COOKIE(STRING)
PULSE_SERVER(STRING)
PULSE_ID(STRING)

I can't see PULSE_SESSION_ID(STRING). Is that expected?

Comment 21 Wim Taymans 2019-09-16 13:42:29 UTC
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?

Comment 22 hprhelbugzilla 2019-09-16 15:47:25 UTC
The only variables that are known to be requires are PULSE_COOKIE and PULSE_SERVER.

Comment 23 Tomas Pelka 2019-09-17 07:00:36 UTC
(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.

Comment 24 Jeff Burrell 2019-09-18 15:51:43 UTC
We'd like to test this.  Can someone make the pulseaudio package (pulseaudio-11.1-23.el8)available to us, please?

Comment 25 Wim Taymans 2019-09-19 15:22:50 UTC
(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?

Comment 26 Jeff Burrell 2019-09-20 14:32:34 UTC
yes

Comment 27 Jeff Burrell 2019-09-24 17:04:22 UTC
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

Comment 29 errata-xmlrpc 2019-11-05 21:27:38 UTC
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 30 Red 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