Hide Forgot
Description of problem: Didn't do anything specific to trigger this, may happen on start/shutdown. Version-Release number of selected component: pulseaudio-4.0-9.gitf81e3.fc21 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/pulseaudio --start --log-target=syslog crash_function: pa_drop_caps executable: /usr/bin/pulseaudio kernel: 3.13.0-0.rc3.git3.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1004 Truncated backtrace: Thread no. 1 (2 frames) #2 pa_drop_caps at daemon/caps.c:85 #3 pa_drop_root at daemon/caps.c:77
Created attachment 839404 [details] File: backtrace
Created attachment 839405 [details] File: cgroup
Created attachment 839406 [details] File: core_backtrace
Created attachment 839407 [details] File: dso_list
Created attachment 839408 [details] File: environ
Created attachment 839409 [details] File: limits
Created attachment 839410 [details] File: maps
Created attachment 839411 [details] File: open_fds
Created attachment 839412 [details] File: proc_pid_status
Created attachment 839413 [details] File: var_log_messages
Same happening on F20 as well. Thanks, V.
SELinux is preventing /usr/bin/pulseaudio from using the setcap access on a process. ***** Plugin mozplugger (99.1 confidence) suggests ************************ If you want to use the plugin package Then you must turn off SELinux controls on the Firefox plugins. Do # setsebool -P unconfined_mozilla_plugin_transition 0 ***** Plugin catchall (1.81 confidence) suggests ************************** If you believe that pulseaudio should be allowed setcap access on processes labeled mozilla_plugin_t by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep pulseaudio /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c 0.c1023 Target Context unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c 0.c1023 Target Objects [ process ] Source pulseaudio Source Path /usr/bin/pulseaudio Port <Unknown> Host black.localnet Source RPM Packages pulseaudio-4.0-9.gitf81e3.fc20.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-122.fc20.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name black.localnet Platform Linux black.localnet 3.13.3-201.fc20.x86_64 #1 SMP Fri Feb 14 19:08:32 UTC 2014 x86_64 x86_64 Alert Count 2 First Seen 2014-02-24 18:15:02 MSK Last Seen 2014-02-24 18:16:07 MSK Local ID f73354f7-6756-4d9c-8c28-3d52fe89402f Raw Audit Messages type=AVC msg=audit(1393251367.345:463): avc: denied { setcap } for pid=20609 comm="pulseaudio" scontext=unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c0.c1023 tclass=process type=SYSCALL msg=audit(1393251367.345:463): arch=x86_64 syscall=capset success=no exit=EACCES a0=25cd044 a1=25cd04c a2=25cd040 a3=386061c310 items=0 ppid=20574 pid=20609 auid=1001 uid=1001 gid=1001 euid=1001 suid=1001 fsuid=1001 egid=1001 sgid=1001 fsgid=1001 ses=1 tty=(none) comm=pulseaudio exe=/usr/bin/pulseaudio subj=unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c0.c1023 key=(null) Hash: pulseaudio,mozilla_plugin_t,mozilla_plugin_t,process,setcap
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.