Bug 1371415

Summary: [DELL-7.3 BUG] pulseaudio: fail to open cookie file /var/lib/gdm/.config/pulse/cookies
Product: Red Hat Enterprise Linux 7 Reporter: Purnendu Bhushan <purnendu_bhushan_mis>
Component: pulseaudioAssignee: Wim Taymans <wtaymans>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: kasmith, linux-bugs, purnendu_bhushan_mis, wtaymans, yzheng
Target Milestone: rcKeywords: Reopened
Target Release: 7.4   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-11 21:51:12 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:
Bug Depends On:    
Bug Blocks: 1304042    
Attachments:
Description Flags
/var/log/messages file showing the issue none

Description Purnendu Bhushan 2016-08-30 07:53:38 UTC
Created attachment 1195652 [details]
/var/log/messages file showing the issue

Description of problem:
After successful installation and boot into RHEL-7.3 beta in BIOS mode, /var/log/messages shows the following messages:
" pulseaudio[5175]: [pulseaudio] authkey.c: Failed to open cookie file '/var/lib/gdm/.config/pulse/cookie': No such file or directory
 pulseaudio[5175]: [pulseaudio] authkey.c: Failed to load authentication key '/var/lib/gdm/.config/pulse/cookie': No such file or directory "


Version-Release number of selected component (if applicable):


How reproducible:
 Always

Steps to Reproduce:
1.install RHEL 7.3 beta on x86_64
2.boot into OS and check for /var/log/messages


Actual results:
Fail to load cookies files

Expected results:
no such fail should be there

Additional info:

Comment 1 Purnendu Bhushan 2016-08-30 08:05:10 UTC
version-Release number of selected component
 pulseaudio-gdm-hook-6.0-8.el7.x86_64

Comment 3 Purnendu Bhushan 2016-09-24 18:10:01 UTC
Few observations:
-issue is seen in RHEL 7.3 snapshort 4 
- issue is seen only for first boot only ,consecutive reboot doesn't produce  this log message is /var/log/messages 

can you please explain this behavior

Comment 4 Wim Taymans 2016-09-28 11:10:25 UTC
Quite normal, the first boot there is no cookie file so it fails to load it, then it creates one and successive boots can pick it up without errors.

Comment 5 Karl Hastings 2016-09-28 15:40:51 UTC
Purnendu,

Does something not work on the first boot, or are you just concerned about the failure in the log file?

If it's just the failure message, do you have further questions, or can we close this BZ?

Comment 6 Purnendu Bhushan 2016-09-29 07:03:29 UTC
Karl,
As there is no functionality loss, also I was just concerned about the failure in log file so we can close this BZ

Comment 7 yzheng 2019-07-02 01:33:46 UTC
I'm sorry that I want to reopen this ticket because one of my customer's issue(case 02381618):

My customer found that the server outputted these messages after login through the teraterm:
~~~
May  7 21:33:09 SVAP1111 pulseaudio[14809]: [pulseaudio] authkey.c: Failed to open cookie file '/home/hdaadm/.config/pulse/cookie': No such file or directory    < ======
May  7 21:33:09 SVAP1111 pulseaudio[14809]: [pulseaudio] authkey.c: Failed to load authentication key '/home/hdaadm/.config/pulse/cookie': No such file or directory    < ======
May  7 21:33:09 SVAP1111 pulseaudio[14809]: [pulseaudio] authkey.c: Failed to open cookie file '/home/hdaadm/.pulse-cookie': No such file or directory    < ======
May  7 21:33:09 SVAP1111 pulseaudio[14809]: [pulseaudio] authkey.c: Failed to load authentication key '/home/hdaadm/.pulse-cookie': No such file or directory    < ======
~~~

But customer said that this user(hdaadm) was not the first login user and another user which was new created did not output these messages. And customer found that the user(hdaadm)'s home directory has no '.pulse-cookie' or '.config' file at all even after logging into the OS.

Customer wants to know the reason of these behaviors.

Comment 11 Chris Williams 2020-11-11 21:51:12 UTC
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed. 

From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."

If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook  

Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product. 

Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.  

[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7