I ran a strace on the xfsettingsd pid, logged out, logged in and I could
see a lot of these repeating:
poll([{fd=3, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=3,
revents=POLLOUT}])
writev(3, [{"\20\0\3\0\3\0\0\0AltL", 12}, {NULL, 0}, {"", 0}], 3) = 12
poll([{fd=3, events=POLLIN}], 1, 4294967295) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0\213\346\0\0\0\0\232\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(3, 0x7fffc492a350, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(3, 0x7fffc492a350, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=3,
revents=POLLOUT}])
writev(3, [{"\20\0\5\0\n\0\0\0LevelThree\0\0", 20}, {NULL, 0}, {"", 0}], 3) = 20
poll([{fd=3, events=POLLIN}], 1, 4294967295) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0\214\346\0\0\0\0\233\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(3, 0x7fffc492a350, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(3, 0x7fffc492a350, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=3,
revents=POLLOUT}])
writev(3, [{"\20\0\3\0\4\0\0\0LAlt", 12}, {NULL, 0}, {"", 0}], 3) = 12
poll([{fd=3, events=POLLIN}], 1, 4294967295) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0\215\346\0\0\0\0\234\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(3, 0x7fffc492a350, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(3, 0x7fffc492a350, 0) = -1 EAGAIN (Resource temporarily
unavailable)
The values are different between the calls as you can see (though
usually similar), but they seem to be repeating endlessly, till the
system settles down several minutes down the road, when it all stops.
Not sure if relevant, let me know if I can provide any information that
could help track the issue down.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395547
Title:
xfsettingsd and xfce4-volumed using a lot of CPU after screen lock /
unlock
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1395547/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs