Description of problem: rtkit-daemon[1141]: Failed to make ourselves RT: Operation not permitted Version-Release number of selected component (if applicable): kernel-2.6.36-5.fc15.x86_64 pulseaudio-0.9.21-6.fc13.x86_64 pulseaudio-gdm-hooks-0.9.21-6.fc13.x86_64 pulseaudio-libs-0.9.21-6.fc13.x86_64 pulseaudio-libs-glib2-0.9.21-6.fc13.x86_64 pulseaudio-libs-zeroconf-0.9.21-6.fc13.x86_64 pulseaudio-module-bluetooth-0.9.21-6.fc13.x86_64 pulseaudio-module-gconf-0.9.21-6.fc13.x86_64 pulseaudio-module-lirc-0.9.21-6.fc13.x86_64 pulseaudio-module-x11-0.9.21-6.fc13.x86_64 pulseaudio-utils-0.9.21-6.fc13.x86_64 selinux-policy-3.9.9-3.fc15.noarch selinux-policy-targeted-3.9.9-3.fc15.noarch systemd-13-1.fc15.x86_64 systemd-gtk-13-1.fc15.x86_64 systemd-units-13-1.fc15.x86_64
I'm not on Fedora/RedHat, so take this with a grain of salt: I noticed that this problem is systemd specific, when booting with SysVInit (ceteris paribus) it does not occur. @Nicolas: maybe worth checking what happens if you do not use systemd?
The problem occurs when CONFIG_RT_GROUP_SCHED is enabled, and should also apply to any other RT, non-root processes. The reason should be clear from Documentation/scheduler/sched-rt-group.txt.
Hi Tom Thanks very much for the advice. Unfortunately I'm not sure switching to and from systemd is really possible anymore in rawhide, with all the stuff being half converted. If I read you correctly systemd group scheduling broke pulseaudio rt scheduling. That makes it something for Lennart to fix :(
Yup, I'm sure Lennart will know what to do. In the meantime, you can avoid the problem by disabling the cpu cgroup from /etc/systemd/system.conf. That is, change #DefaultControllers=cpu into DefaultControllers=
Fixed now in systemd git and rtkit git. Will be uploaded to rawhide shortly.
After installing the new upstream packages i found this error messages in message.log Feb 18 12:18:00 mother kernel: [ 24.318044] rtkit-daemon[875]: Successfully made thread 1525 of process 1525 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11. Feb 18 12:18:00 mother kernel: [ 24.318058] rtkit-daemon[875]: Supervising 1 threads of 1 processes of 1 users. Feb 18 12:18:00 mother kernel: [ 24.380345] rtkit-daemon[875]: Failed to make thread 1526 RT: Operation not permitted Feb 18 12:18:00 mother kernel: [ 24.383959] rtkit-daemon[875]: Failed to make thread 1526 RT: Operation not permitted Feb 18 12:18:00 mother kernel: [ 24.422493] rtkit-daemon[875]: Failed to make thread 1527 RT: Operation not permitted Feb 18 12:18:00 mother kernel: [ 24.425170] rtkit-daemon[875]: Failed to make thread 1527 RT: Operation not permitted Feb 18 12:18:00 mother kernel: [ 24.434661] rtkit-daemon[875]: Failed to make thread 1528 RT: Operation not permitted Feb 18 12:18:00 mother kernel: [ 24.438025] rtkit-daemon[875]: Failed to make thread 1528 RT: Operation not permitted Is this bad or not?
This finally completely fixed with the rtkit and systemd packages I uploaded yesterday and which are currently waiting in bodhi. (rtkit 0.10, systemd 18)
*** Bug 656054 has been marked as a duplicate of this bug. ***
Ok, with rtkit-0.10-1.fc15.x86_64 and systemd-18-1.fc15.x86_64 the bug is fixed. PS: Give it a site or a mail-list where i can ask questions about funktion and work of systemd?
I've forgot........thx for your work and your quick reactions for user questions. :)
(In reply to comment #9) > Ok, with rtkit-0.10-1.fc15.x86_64 and systemd-18-1.fc15.x86_64 the bug is > fixed. I do not see it. I do have now systemd-18-1.fc16.x86_64 and rtkit-0.10-1.fc16.x86_64 and this is from the last boot: [ 21.446122] rtkit-daemon[861]: Successfully called chroot. [ 21.538830] rtkit-daemon[861]: Successfully dropped privileges. [ 21.572074] rtkit-daemon[861]: Successfully limited resources. [ 21.604706] rtkit-daemon[861]: Running. [ 21.637053] rtkit-daemon[861]: Watchdog thread running. [ 21.669402] rtkit-daemon[861]: Canary thread running. [ 1972.627152] rtkit-daemon[861]: Failed to make thread 2886 RT: Operation not permitted [ 1972.636937] rtkit-daemon[861]: Failed to make thread 2886 RT: Operation not permitted [ 1972.687571] rtkit-daemon[861]: Failed to make thread 2888 RT: Operation not permitted [ 1972.697583] rtkit-daemon[861]: Failed to make thread 2888 RT: Operation not permitted Is this a diffence between f15 and f16 or the bug is still there? If yes that should this be reopened?
(In reply to comment #11) > (In reply to comment #9) > > Ok, with rtkit-0.10-1.fc15.x86_64 and systemd-18-1.fc15.x86_64 the bug is > > fixed. > > > I do not see it. I do have now systemd-18-1.fc16.x86_64 and > rtkit-0.10-1.fc16.x86_64 and this is from the last boot: > > [ 21.446122] rtkit-daemon[861]: Successfully called chroot. > [ 21.538830] rtkit-daemon[861]: Successfully dropped privileges. > [ 21.572074] rtkit-daemon[861]: Successfully limited resources. > [ 21.604706] rtkit-daemon[861]: Running. > [ 21.637053] rtkit-daemon[861]: Watchdog thread running. > [ 21.669402] rtkit-daemon[861]: Canary thread running. > [ 1972.627152] rtkit-daemon[861]: Failed to make thread 2886 RT: Operation not > permitted > [ 1972.636937] rtkit-daemon[861]: Failed to make thread 2886 RT: Operation not > permitted > [ 1972.687571] rtkit-daemon[861]: Failed to make thread 2888 RT: Operation not > permitted > [ 1972.697583] rtkit-daemon[861]: Failed to make thread 2888 RT: Operation not > permitted > > Is this a diffence between f15 and f16 or the bug is still there? If yes that > should this be reopened? Are you sure you rebooted after upgrading? Ist it possible that pam_systemd is not enabled for you? Could you run "authconfig" and exit it, so that the PAM files are written correctly, then relogin? If this all doesn't help, please paste the following two outputs: cat /proc/$(pidof pulseaudio)/cgroup cat /proc/$(pidof rtkit-daemon)/cgroup Thanks!
(In reply to comment #9) > Ok, with rtkit-0.10-1.fc15.x86_64 and systemd-18-1.fc15.x86_64 the bug is > fixed. > > PS: > Give it a site or a mail-list where i can ask questions about funktion and > work of systemd? Links to mailing lists and IRC channels you find on systemd's web site: http://www.freedesktop.org/wiki/Software/systemd
*** Bug 679091 has been marked as a duplicate of this bug. ***
(In reply to comment #12) > (In reply to comment #11) > > Is this a diffence between f15 and f16 or the bug is still there? If yes that > > should this be reopened? > > Are you sure you rebooted after upgrading? I am sure. A machine was rebooted to run a new kernel. > Ist it possible that pam_systemd is not enabled for you? Could you run > "authconfig" and exit it, so that the PAM files are written correctly, then > relogin? I think that you mean "authconfig --update", right? Running "authconfig" by itself dumped 150 lines of help. That could be it. AFAICT "Failed to make thread 1874 RT: Operation not permitted" messages were showing up on an attempt to start a desktop session and "updating" /etc/pam.d/ files apparently made that error to go away. What was supposed to force that operation? This is an updated rawhide installation and not "from scratch". > If this all doesn't help, please paste the following two outputs: > > cat /proc/$(pidof pulseaudio)/cgroup > cat /proc/$(pidof rtkit-daemon)/cgroup These differ, at least now, by one line: 1:name=systemd:/user/michal/1c in the first case and 1:name=systemd:/system/rtkit-daemon.service in the second one.
> I think that you mean "authconfig --update", right? Running "authconfig" > by itself dumped 150 lines of help. Yupp, that should work too. I was mostly actually thinking of authconfig-gtk, which works without args. But it's all doing the same thing. > That could be it. AFAICT "Failed to make thread 1874 RT: Operation not > permitted" messages were showing up on an attempt to start a desktop session > and "updating" /etc/pam.d/ files apparently made that error to go away. > What was supposed to force that operation? This is an updated rawhide > installation and not "from scratch". Well, tbh I am not sure what part is responsible for rewriting those files. Might make sense to file a bug against the authconfig package to make sure atuthconfig executes the same command during upgrade or so, if it doesn't do so yet. > > If this all doesn't help, please paste the following two outputs: > > > > cat /proc/$(pidof pulseaudio)/cgroup > > cat /proc/$(pidof rtkit-daemon)/cgroup > > These differ, at least now, by one line: > 1:name=systemd:/user/michal/1c in the first case and > 1:name=systemd:/system/rtkit-daemon.service in the second one. More interesting are actually the lines with ":cpu:" in the middle. They should both have a suffix of / if everything works correctly. Anyway, I am assuming that the issue is fixed by the PAM config file rewrite. Please file a bug against authconfig to ensure that this rewrite is done automatically.
(In reply to comment #16) > More interesting are actually the lines with ":cpu:" in the middle. They should > both have a suffix of / if everything works correctly. In both cases they look like this: "4:cpu:/". > Anyway, I am assuming that the issue is fixed by the PAM config file rewrite. I am not absolutely sure. We never heard from a person who filed bug 679091 and, that looked like a new installation and not an update. > Please file a bug against authconfig to ensure that this rewrite is done > automatically. All right. Bug 679517.
(In reply to comment #17) > (In reply to comment #16) > > > More interesting are actually the lines with ":cpu:" in the middle. They should > > both have a suffix of / if everything works correctly. > > In both cases they look like this: "4:cpu:/". That looks correct.
The error comes again....... Today i found this in message log. Feb 26 12:56:08 mother kernel: [ 45.527261] rtkit-daemon[906]: Successfully made thread 2142 of process 2142 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11. Feb 26 12:56:08 mother kernel: [ 45.527275] rtkit-daemon[906]: Supervising 1 threads of 1 processes of 1 users. Feb 26 12:56:08 mother kernel: [ 45.566876] rtkit-daemon[906]: Failed to make thread 2144 RT: Operation not permitted Feb 26 12:56:08 mother kernel: [ 45.570354] rtkit-daemon[906]: Failed to make thread 2144 RT: Operation not permitted Feb 26 12:56:08 mother kernel: [ 45.607600] rtkit-daemon[906]: Failed to make thread 2145 RT: Operation not permitted Feb 26 12:56:08 mother kernel: [ 45.610460] rtkit-daemon[906]: Failed to make thread 2145 RT: Operation not permitted Feb 26 12:56:08 mother kernel: [ 45.619582] rtkit-daemon[906]: Failed to make thread 2146 RT: Operation not permitted Feb 26 12:56:08 mother kernel: [ 45.624173] rtkit-daemon[906]: Failed to make thread 2146 RT: Operation not permitted [root@mother rave]# rpm -qa rtkit rtkit-0.10-1.fc15.x86_64 [root@mother rave]# rpm -qa systemd systemd-18-1.fc15.x86_64
pls reopen the threat again.
raveit65, can you check whether 679517 fixes your problem?
No, i don't think btw i'm not shure, because i updated systemd to 19.1 at Mar 01 16:50:52 Updated: systemd-19-1.fc15.x86_64 Next reboot was at Mar 1 23:15:00 But in my messages log i found this entries since Mar 1 23:15:00. Mar 1 23:27:48 mother gdm-simple-slave[2648]: DEBUG(+): GdmSlave: Got timed login details: 0 rave 0 Mar 1 23:27:49 mother kernel: [ 720.849155] rtkit-daemon[869]: Successfully made thread 2720 of process 2720 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11. Mar 1 23:27:49 mother kernel: [ 720.849171] rtkit-daemon[869]: Supervising 1 threads of 1 processes of 1 users. Mar 1 23:27:49 mother kernel: [ 720.882969] rtkit-daemon[869]: Failed to make thread 2722 RT: Operation not permitted Mar 1 23:27:49 mother kernel: [ 720.886477] rtkit-daemon[869]: Failed to make thread 2722 RT: Operation not permitted Mar 1 23:27:49 mother kernel: [ 720.924605] rtkit-daemon[869]: Failed to make thread 2723 RT: Operation not permitted Mar 1 23:27:49 mother kernel: [ 720.927978] rtkit-daemon[869]: Failed to make thread 2723 RT: Operation not permitted Mar 1 23:27:49 mother kernel: [ 720.938122] rtkit-daemon[869]: Failed to make thread 2724 RT: Operation not permitted Mar 1 23:27:49 mother kernel: [ 720.941446] rtkit-daemon[869]: Failed to make thread 2724 RT: Operation not permitted It happends again at Mar 1 23:29:29 and etc. Last found was Mar 2 09:21:59 mother kernel: [ 52.067779] rtkit-daemon[935]: Successfully made thread 2158 of process 2158 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11. Mar 2 09:21:59 mother kernel: [ 52.067790] rtkit-daemon[935]: Supervising 1 threads of 1 processes of 1 users. Mar 2 09:21:59 mother kernel: [ 52.236989] rtkit-daemon[935]: Failed to make thread 2161 RT: Operation not permitted Mar 2 09:21:59 mother kernel: [ 52.240191] rtkit-daemon[935]: Failed to make thread 2161 RT: Operation not permitted Mar 2 09:21:59 mother kernel: [ 52.276510] rtkit-daemon[935]: Failed to make thread 2162 RT: Operation not permitted Mar 2 09:21:59 mother kernel: [ 52.279031] rtkit-daemon[935]: Failed to make thread 2162 RT: Operation not permitted Mar 2 09:21:59 mother kernel: [ 52.287898] rtkit-daemon[935]: Failed to make thread 2163 RT: Operation not permitted Mar 2 09:21:59 mother kernel: [ 52.291254] rtkit-daemon[935]: Failed to make thread 2163 RT: Operation not permitted Since this time i booted the system one time again but it doesn't happend.
Don't have this problem any-more on the kde-x86_64-20110315.01.iso nightly. systemd-20-1.fc15.x86_64 rtkit-0.10-1.fc15.x86_64
systemd-20-1.fc15.x86_64 rtkit-0.10-1.fc15.x86_64 initscripts-9.27-1.fc15.x86_64 $ dmesg | grep rtkit [...] [ 125.096816] rtkit-daemon[1026]: Failed to make thread 2222 RT: Operation not permitted [ 125.102192] rtkit-daemon[1026]: Failed to make thread 2222 RT: Operation not permitted [ 125.115916] rtkit-daemon[1026]: Failed to make thread 2223 RT: Operation not permitted [ 125.121381] rtkit-daemon[1026]: Failed to make thread 2223 RT: Operation not permitted .... $ uname -r 2.6.38-1.fc15.x86_64
Freshly updated Fedora 15: systemd-26-1.fc15.x86_64 rtkit-0.10-1.fc15.x86_64 initscripts-9.30-2.fc15.x86_64 from /var/log/messages: May 24 15:37:41 gallagher pulseaudio[1644]: socket-server.c: bind(): Address already in use May 24 15:37:41 gallagher pulseaudio[1644]: module.c: Failed to load module "module-esound-protocol-unix" (argument: ""): initialization failed. May 24 15:37:41 gallagher pulseaudio[1644]: main.c: Module load failed. May 24 15:37:41 gallagher pulseaudio[1644]: main.c: Failed to initialize daemon. May 24 15:37:41 gallagher pulseaudio[1642]: main.c: Daemon startup failed. May 24 12:37:42 gallagher rtkit-daemon[1288]: Successfully made thread 1657 of process 1657 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11. May 24 12:37:42 gallagher rtkit-daemon[1288]: Failed to make thread 1658 RT: Operation not permitted May 24 12:37:42 gallagher rtkit-daemon[1288]: Failed to make thread 1658 RT: Operation not permitted May 24 12:37:42 gallagher rtkit-daemon[1288]: Failed to make thread 1659 RT: Operation not permitted May 24 12:37:42 gallagher rtkit-daemon[1288]: Failed to make thread 1659 RT: Operation not permitted The other thing I noticed was the following regarding the /proc/<pid>/cgroup attributes of pulseaudio and rtkit: pulseaudio: 10:blkio:/ 9:net_cls:/ 8:freezer:/ 7:devices:/ 6:memory:/ 5:cpuacct:/ 4:cpu:/system/prefdm.service 3:ns:/ 2:cpuset:/ 1:name=systemd:/system/prefdm.service rtkit: 10:blkio:/ 9:net_cls:/ 8:freezer:/ 7:devices:/ 6:memory:/ 5:cpuacct:/ 4:cpu:/ 3:ns:/ 2:cpuset:/ 1:name=systemd:/system/rtkit-daemon.service
Today sound works, rtkit does not print any error messages, and pulseaudio /proc/<pid>/cgroup has the the following info: 10:blkio:/ 9:net_cls:/ 8:freezer:/ 7:devices:/ 6:memory:/ 5:cpuacct:/ 4:cpu:/ 3:ns:/ 2:cpuset:/ 1:name=systemd:/user/sarantis/34 I don't know what was changed except login/logout. Please note that several login/logout exchanges were also performed yesterday (re comment 25).
have the following errors in /var/log/messages: Jun 4 17:44:50 localhost rtkit-daemon[1245]: Successfully made thread 1244 of process 1244 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11. Jun 4 17:44:50 localhost rtkit-daemon[1245]: Failed to make thread 1249 RT: Operation not permitted Jun 4 17:44:50 localhost rtkit-daemon[1245]: Failed to make thread 1249 RT: Operation not permitted Jun 4 17:44:50 localhost rtkit-daemon[1245]: Failed to make thread 1250 RT: Operation not permitted Jun 4 17:44:50 localhost rtkit-daemon[1245]: Failed to make thread 1250 RT: Operation not permitted Jun 4 17:44:50 localhost rtkit-daemon[1245]: Failed to make thread 1251 RT: Operation not permitted Jun 4 17:44:50 localhost rtkit-daemon[1245]: Failed to make thread 1251 RT: Operation not permitted Fedora 15, 2.6.38.6-27.fc15.x86_64 systemd-26-2.fc15.x86_64 rtkit-0.10-1.fc15.x86_64 initscripts-9.30-2.fc15.x86_64
I'm also seeing this. Have tried the authconfig fix to no avail. # grep rtkit /var/log/messages Jul 4 08:58:10 localhost rtkit-daemon[1820]: Failed to make thread 1825 RT: Operation not permitted Jul 4 08:58:10 localhost rtkit-daemon[1820]: Failed to make thread 1825 RT: Operation not permitted Jul 4 08:58:10 localhost rtkit-daemon[1820]: Failed to make thread 1826 RT: Operation not permitted Jul 4 08:58:10 localhost rtkit-daemon[1820]: Failed to make thread 1826 RT: Operation not permitted # rpm -q systemd rtkit initscripts systemd-26-5.fc15.x86_64 rtkit-0.10-1.fc15.x86_64 initscripts-9.30-2.fc15.x86_64 # cat /proc/$(pidof pulseaudio)/cgroup 10:blkio:/ 9:net_cls:/ 8:freezer:/ 7:devices:/ 6:memory:/ 5:cpuacct:/ 4:cpu:/ 3:ns:/ 2:cpuset:/ 1:name=systemd:/user/username/3 # cat /proc/$(pidof rtkit-daemon)/cgroup 10:blkio:/ 9:net_cls:/ 8:freezer:/ 7:devices:/ 6:memory:/ 5:cpuacct:/ 4:cpu:/ 3:ns:/ 2:cpuset:/ 1:name=systemd:/system/rtkit-daemon.service
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
My system has ceased to function, and this is the only clue I find in the logs Nov 11 05:44:41 godmachine rtkit-daemon[1257]: Successfully made thread 7576 of process 7576 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11. Nov 10 23:44:41 godmachine pulseaudio[7576]: pid.c: Daemon already running. Nov 11 05:44:41 godmachine rtkit-daemon[1257]: Successfully made thread 7580 of process 7580 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11. Nov 10 23:44:41 godmachine pulseaudio[7580]: pid.c: Daemon already running. <snip> Nov 10 23:44:45 godmachine pulseaudio[7600]: pid.c: Daemon already running. Nov 11 05:44:45 godmachine rtkit-daemon[1257]: Warning: Reached burst limit for user '500', denying request. Nov 11 05:44:45 godmachine rtkit-daemon[1257]: Warning: Reached burst limit for user '500', denying request. Nov 11 05:44:45 godmachine rtkit-daemon[1257]: Warning: Reached burst limit for user '500', denying request. Nov 11 05:44:45 godmachine rtkit-daemon[1257]: Warning: Reached burst limit for user '500', denying request. Nov 11 05:44:45 godmachine rtkit-daemon[1257]: Warning: Reached burst limit for user '500', denying request. Nov 11 05:44:45 godmachine rtkit-daemon[1257]: Warning: Reached burst limit for user '500', denying request. Nov 11 05:44:45 godmachine rtkit-daemon[1257]: Warning: Reached burst limit for user '500', denying request. Nov 11 05:44:45 godmachine rtkit-daemon[1257]: Warning: Reached burst limit for user '500', denying request. Nov 11 05:44:45 godmachine rtkit-daemon[1257]: Warning: Reached burst limit for user '500', denying request. Nov 11 05:44:45 godmachine rtkit-daemon[1257]: Warning: Reached burst limit for user '500', denying request. Nov 11 05:44:45 godmachine rtkit-daemon[1257]: Warning: Reached burst limit for user '500', denying request. Just performed yum update and problem presists rtkit.x86_64 0.10-1.fc15 @fedora systemd.x86_64 26-13.fc15 @updates systemd-sysv.x86_64 26-13.fc15 @updates systemd-units.x86_64 26-13.fc15 @updates pulseaudio.x86_64 0.9.22-5.fc15 @updates-testing pulseaudio-gdm-hooks.x86_64 0.9.22-5.fc15 @updates-testing pulseaudio-libs.i686 0.9.22-5.fc15 @fedora pulseaudio-libs.x86_64 0.9.22-5.fc15 @updates-testing pulseaudio-libs-glib2.x86_64 0.9.22-5.fc15 @updates-testing pulseaudio-module-bluetooth.x86_64 0.9.22-5.fc15 @updates-testing pulseaudio-module-gconf.x86_64 0.9.22-5.fc15 @updates-testing pulseaudio-module-x11.x86_64 0.9.22-5.fc15 @updates-testing pulseaudio-utils.x86_64 0.9.22-5.fc15 @updates-testing In an attempt to rule out SELinux I did "restorecon -Rv /" , rebooted and still persists.
(In reply to comment #30) I'm getting a similar problem under Fedora 16 with user '1000' instead. Another symptom in my case is that I don't have any audio support once logged in. (Oddly enough, my audio works at the login screen.) Whatever the issue is, it's causing my system (an AMD Phenom II 1090T with 16 GB RAM) to bog down without even running anything. Below is one full cycle of logged messages from just after the last "denying request" to the end of the next cycle. Just as a point of interest, the machine that this is occurring on is a desktop without BlueTooth support, and yet I see messages related to BlueTooth and bluez in this output. Nov 27 20:44:09 aragorn dbus[1028]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 27 20:44:09 aragorn dbus-daemon[1028]: dbus[1028]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 27 20:44:09 aragorn dbus[1028]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Nov 27 20:44:09 aragorn dbus-daemon[1028]: dbus[1028]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Nov 27 20:44:09 aragorn pulseaudio[13788]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.systemd1.LoadFailed Nov 27 20:44:09 aragorn pulseaudio[13788]: module-ladspa-sink.c: Master sink not found Nov 27 20:44:09 aragorn pulseaudio[13788]: module.c: Failed to load module "module-ladspa-sink" (argument: "sink_name=ladspa_output.mbeq_1197.mbeq master=alsa_output.pci-0000_04_09.0.analog-surround-51 plugin=mbeq_1197 label=mbeq control=0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0"): initialization failed. Nov 27 20:44:09 aragorn pulseaudio[13788]: main.c: Module load failed. Nov 27 20:44:09 aragorn pulseaudio[13788]: main.c: Failed to initialize daemon. Nov 27 20:44:09 aragorn pulseaudio[13786]: main.c: Daemon startup failed. Nov 28 01:44:11 aragorn rtkit-daemon[1343]: Successfully made thread 13805 of process 13805 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11. Nov 28 01:44:11 aragorn rtkit-daemon[1343]: Successfully made thread 13806 of process 13805 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:11 aragorn rtkit-daemon[1343]: Successfully made thread 13807 of process 13805 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:11 aragorn rtkit-daemon[1343]: Successfully made thread 13810 of process 13805 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:11 aragorn rtkit-daemon[1343]: Successfully made thread 13811 of process 13805 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 27 20:44:11 aragorn dbus[1028]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 27 20:44:11 aragorn dbus-daemon[1028]: dbus[1028]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 27 20:44:11 aragorn dbus[1028]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Nov 27 20:44:11 aragorn dbus-daemon[1028]: dbus[1028]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Nov 27 20:44:11 aragorn pulseaudio[13805]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.systemd1.LoadFailed Nov 27 20:44:11 aragorn pulseaudio[13805]: module-ladspa-sink.c: Master sink not found Nov 27 20:44:11 aragorn pulseaudio[13805]: module.c: Failed to load module "module-ladspa-sink" (argument: "sink_name=ladspa_output.mbeq_1197.mbeq master=alsa_output.pci-0000_04_09.0.analog-surround-51 plugin=mbeq_1197 label=mbeq control=0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0"): initialization failed. Nov 27 20:44:11 aragorn pulseaudio[13805]: main.c: Module load failed. Nov 27 20:44:11 aragorn pulseaudio[13805]: main.c: Failed to initialize daemon. Nov 27 20:44:11 aragorn pulseaudio[13803]: main.c: Daemon startup failed. Nov 28 01:44:14 aragorn rtkit-daemon[1343]: Successfully made thread 13836 of process 13836 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11. Nov 28 01:44:14 aragorn rtkit-daemon[1343]: Successfully made thread 13837 of process 13836 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:14 aragorn rtkit-daemon[1343]: Successfully made thread 13838 of process 13836 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:14 aragorn rtkit-daemon[1343]: Successfully made thread 13839 of process 13836 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:14 aragorn rtkit-daemon[1343]: Successfully made thread 13840 of process 13836 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 27 20:44:14 aragorn dbus[1028]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 27 20:44:14 aragorn dbus-daemon[1028]: dbus[1028]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 27 20:44:14 aragorn dbus[1028]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Nov 27 20:44:14 aragorn dbus-daemon[1028]: dbus[1028]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Nov 27 20:44:14 aragorn pulseaudio[13836]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.systemd1.LoadFailed Nov 27 20:44:14 aragorn pulseaudio[13836]: module-ladspa-sink.c: Master sink not found Nov 27 20:44:14 aragorn pulseaudio[13836]: module.c: Failed to load module "module-ladspa-sink" (argument: "sink_name=ladspa_output.mbeq_1197.mbeq master=alsa_output.pci-0000_04_09.0.analog-surround-51 plugin=mbeq_1197 label=mbeq control=0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0"): initialization failed. Nov 27 20:44:14 aragorn pulseaudio[13836]: main.c: Module load failed. Nov 27 20:44:14 aragorn pulseaudio[13836]: main.c: Failed to initialize daemon. Nov 27 20:44:14 aragorn pulseaudio[13834]: main.c: Daemon startup failed. Nov 28 01:44:17 aragorn rtkit-daemon[1343]: Successfully made thread 13864 of process 13864 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11. Nov 28 01:44:17 aragorn rtkit-daemon[1343]: Successfully made thread 13865 of process 13864 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:17 aragorn rtkit-daemon[1343]: Successfully made thread 13866 of process 13864 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:17 aragorn rtkit-daemon[1343]: Successfully made thread 13867 of process 13864 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:17 aragorn rtkit-daemon[1343]: Successfully made thread 13868 of process 13864 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 27 20:44:17 aragorn dbus[1028]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 27 20:44:17 aragorn dbus-daemon[1028]: dbus[1028]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 27 20:44:17 aragorn dbus[1028]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Nov 27 20:44:17 aragorn dbus-daemon[1028]: dbus[1028]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Nov 27 20:44:17 aragorn pulseaudio[13864]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.systemd1.LoadFailed Nov 27 20:44:17 aragorn pulseaudio[13864]: module-ladspa-sink.c: Master sink not found Nov 27 20:44:17 aragorn pulseaudio[13864]: module.c: Failed to load module "module-ladspa-sink" (argument: "sink_name=ladspa_output.mbeq_1197.mbeq master=alsa_output.pci-0000_04_09.0.analog-surround-51 plugin=mbeq_1197 label=mbeq control=0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0"): initialization failed. Nov 27 20:44:17 aragorn pulseaudio[13864]: main.c: Module load failed. Nov 27 20:44:17 aragorn pulseaudio[13864]: main.c: Failed to initialize daemon. Nov 27 20:44:17 aragorn pulseaudio[13862]: main.c: Daemon startup failed. Nov 28 01:44:20 aragorn rtkit-daemon[1343]: Successfully made thread 13878 of process 13878 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11. Nov 28 01:44:20 aragorn rtkit-daemon[1343]: Successfully made thread 13879 of process 13878 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:20 aragorn rtkit-daemon[1343]: Successfully made thread 13880 of process 13878 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:20 aragorn rtkit-daemon[1343]: Successfully made thread 13881 of process 13878 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:20 aragorn rtkit-daemon[1343]: Successfully made thread 13882 of process 13878 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 27 20:44:20 aragorn dbus[1028]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 27 20:44:20 aragorn dbus-daemon[1028]: dbus[1028]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 27 20:44:20 aragorn dbus[1028]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Nov 27 20:44:20 aragorn dbus-daemon[1028]: dbus[1028]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Nov 27 20:44:20 aragorn pulseaudio[13878]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.systemd1.LoadFailed Nov 27 20:44:20 aragorn pulseaudio[13878]: module-ladspa-sink.c: Master sink not found Nov 27 20:44:20 aragorn pulseaudio[13878]: module.c: Failed to load module "module-ladspa-sink" (argument: "sink_name=ladspa_output.mbeq_1197.mbeq master=alsa_output.pci-0000_04_09.0.analog-surround-51 plugin=mbeq_1197 label=mbeq control=0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0"): initialization failed. Nov 27 20:44:20 aragorn pulseaudio[13878]: main.c: Module load failed. Nov 27 20:44:20 aragorn pulseaudio[13878]: main.c: Failed to initialize daemon. Nov 27 20:44:20 aragorn pulseaudio[13876]: main.c: Daemon startup failed. Nov 28 01:44:23 aragorn rtkit-daemon[1343]: Successfully made thread 13910 of process 13910 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11. Nov 28 01:44:23 aragorn rtkit-daemon[1343]: Successfully made thread 13911 of process 13910 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:23 aragorn rtkit-daemon[1343]: Successfully made thread 13915 of process 13910 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:23 aragorn rtkit-daemon[1343]: Successfully made thread 13916 of process 13910 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 28 01:44:23 aragorn rtkit-daemon[1343]: Successfully made thread 13917 of process 13910 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Nov 27 20:44:23 aragorn dbus[1028]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 27 20:44:23 aragorn dbus-daemon[1028]: dbus[1028]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 27 20:44:23 aragorn dbus[1028]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Nov 27 20:44:23 aragorn dbus-daemon[1028]: dbus[1028]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Nov 27 20:44:23 aragorn pulseaudio[13910]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.systemd1.LoadFailed Nov 27 20:44:23 aragorn pulseaudio[13910]: module-ladspa-sink.c: Master sink not found Nov 27 20:44:23 aragorn pulseaudio[13910]: module.c: Failed to load module "module-ladspa-sink" (argument: "sink_name=ladspa_output.mbeq_1197.mbeq master=alsa_output.pci-0000_04_09.0.analog-surround-51 plugin=mbeq_1197 label=mbeq control=0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0"): initialization failed. Nov 27 20:44:23 aragorn pulseaudio[13910]: main.c: Module load failed. Nov 27 20:44:23 aragorn pulseaudio[13910]: main.c: Failed to initialize daemon. Nov 27 20:44:23 aragorn pulseaudio[13908]: main.c: Daemon startup failed. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:26 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request. Nov 28 01:44:27 aragorn rtkit-daemon[1343]: Warning: Reached burst limit for user '1000', denying request.
Ping what's the current status of this? Are you still hitting this issue?
$ rpm -q systemd rtkit pulseaudio systemd-26-18.fc15.i686 rtkit-0.10-1.fc15.i686 pulseaudio-0.9.22-5.fc15.i686 "authconfig --updateall" didn't help here: $ grep pam_systemd /etc/pam.d/system-auth-ac -session optional pam_systemd.so Apr 15 09:26:59 greg dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' Apr 15 09:27:01 greg rtkit-daemon[1338]: Successfully made thread 1337 of process 1337 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11. Apr 15 09:27:02 greg rtkit-daemon[1338]: Failed to make thread 1341 RT: Operation not permitted Apr 15 09:27:02 greg rtkit-daemon[1338]: Failed to make thread 1341 RT: Operation not permitted Apr 15 09:27:03 greg rtkit-daemon[1338]: Failed to make thread 1342 RT: Operation not permitted Apr 15 09:27:03 greg rtkit-daemon[1338]: Failed to make thread 1342 RT: Operation not permitted Apr 15 09:27:03 greg rtkit-daemon[1338]: Failed to make thread 1343 RT: Operation not permitted Apr 15 09:27:03 greg rtkit-daemon[1338]: Failed to make thread 1343 RT: Operation not permitted The workaround ("DefaultControllers=") in comment#4 works though: Apr 15 10:17:07 greg dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' Apr 15 10:17:09 greg rtkit-daemon[1338]: Successfully made thread 1337 of process 1337 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11. Apr 15 10:17:09 greg rtkit-daemon[1338]: Successfully made thread 1341 of process 1337 (/usr/bin/pulseaudio) owned by '42' RT at priority 5. Apr 15 10:17:11 greg rtkit-daemon[1338]: Successfully made thread 1342 of process 1337 (/usr/bin/pulseaudio) owned by '42' RT at priority 5. Apr 15 10:17:11 greg rtkit-daemon[1338]: Successfully made thread 1343 of process 1337 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
This appears to be specific to F15, which is not supported anymore. Closing. Please reopen if this issue continues to exist on newer installations.
$ rpm -q systemd rtkit systemd-212-2.fc21.x86_64 rtkit-0.11-8.fc21.x86_64 $ journalctl -ab -u rtkit-daemon -o short-monotonic … [ 5.287671] lenovo rtkit-daemon[721]: Failed to make ourselves RT: Operation not permitted … [ 5.296861] lenovo rtkit-daemon[721]: Failed to make ourselves RT: Operation not permitted [ 5.308243] lenovo rtkit-daemon[721]: Failed to make ourselves RT: Operation not permitted [ 5.318488] lenovo rtkit-daemon[721]: Failed to make ourselves RT: Operation not permitted … [ 5.826855] lenovo rtkit-daemon[721]: Warning: Reached burst limit for user '1000', denying request. ~$ cat /proc/$(pidof pulseaudio)/cgroup 10:hugetlb:/ 9:perf_event:/ 8:blkio:/ 7:net_cls,net_prio:/ 6:freezer:/ 5:devices:/ 4:memory:/ 3:cpu,cpuacct:/ 2:cpuset:/ 1:name=systemd:/user.slice/user-1000.slice/session-1.scope ~$ cat /proc/$(pidof rtkit-daemon)/cgroup 10:hugetlb:/ 9:perf_event:/ 8:blkio:/ 7:net_cls,net_prio:/ 6:freezer:/ 5:devices:/system.slice 4:memory:/ 3:cpu,cpuacct:/system.slice 2:cpuset:/ 1:name=systemd:/system.slice/rtkit-daemon.service
I am pretty sure the right fix for this is bug 1229700.
Closing because bug 1229700 resolves the issue.
Finding the same error in my logs on RHEL 8.2