Bug 829493 - pulseaudio not working for users, core-util.c: Failed to create secure directory: Operation not permitted
pulseaudio not working for users, core-util.c: Failed to create secure direct...
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: pulseaudio (Show other bugs)
17
x86_64 Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Lennart Poettering
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-06 17:32 EDT by Thomas Cameron
Modified: 2013-07-03 20:49 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-07-03 20:49:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
sosreport from this machine (370.93 KB, application/x-xz)
2012-06-06 17:38 EDT, Thomas Cameron
no flags Details

  None (edit)
Description Thomas Cameron 2012-06-06 17:32:57 EDT
Description of problem:
No sound for regular users, sound works at login screen and for root.


Version-Release number of selected component (if applicable):
pulseaudio-1.1-9.fc17.x86_64

How reproducible:
Log in as a regular user

Steps to Reproduce:
1. Boot up. Notice tha the sound control is there at the login screen
2. Log in as root. Notice sound works.
3. Log in as a regular user. Notice no volume control, and sound control shows no devices.
  
Actual results:
No sound for users

Expected results:
Sound for users

Additional info:
I'm seeing a bunch of lines like:

Jun  6 16:19:27 case pulseaudio[1667]: [autospawn] core-util.c: Failed to create secure directory: Operation not permitted
Jun  6 16:19:27 case pulseaudio[1667]: [autospawn] lock-autospawn.c: Cannot access autospawn lock.
Jun  6 16:19:27 case pulseaudio[1667]: [pulseaudio] main.c: Failed to acquire autospawn lock

These repeat when I try to log in.
Comment 1 Thomas Cameron 2012-06-06 17:38:11 EDT
Created attachment 590024 [details]
sosreport from this machine
Comment 2 Fedora End Of Life 2013-07-03 19:57:41 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Thomas Cameron 2013-07-03 20:49:49 EDT
I am closing this, as it worked in 18 and now 19. Not sure what the fix was, but it's fixed.

Note You need to log in before you can comment on or make changes to this bug.