http://bugzilla.opensuse.org/show_bug.cgi?id=1074361 Bug ID: 1074361 Summary: No sound with pulseaudio and huge CPU usage Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai@suse.com Reporter: fniepelt@takios.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 754552 --> http://bugzilla.opensuse.org/attachment.cgi?id=754552&action=edit Strace of pulseaudio strace Hello, after updating to snapshot 20171213 or later, I don't have sound anymore. Rollbacking to a snapshot before that one restores sound. `top` reports high CPU usage for pulseaudio (~50%) and X11 (~95 to 100%). Pulseaudio cannot be killed except with a SIGKILL at which point X11 calms down too. `strace` on the running pulseaudio process seems to indicate that it is in some kind of loop (see attachment). `journalct -t pulseaudio` yields the following: Jan 02 13:51:47 linux-0yez pulseaudio[2620]: [pulseaudio] alsa-mixer.c: Volume element Speaker has 8 channels. That's too much! I can't handle that! Jan 02 13:51:47 linux-0yez pulseaudio[2620]: [pulseaudio] alsa-mixer.c: Volume element Speaker has 8 channels. That's too much! I can't handle that! Jan 02 13:51:47 linux-0yez pulseaudio[2620]: [pulseaudio] alsa-mixer.c: Volume element Speaker has 8 channels. That's too much! I can't handle that! Jan 02 13:51:47 linux-0yez pulseaudio[2620]: [pulseaudio] alsa-mixer.c: Volume element PCM has 8 channels. That's too much! I can't handle that! Jan 02 13:51:47 linux-0yez pulseaudio[2620]: [pulseaudio] alsa-mixer.c: Volume element PCM has 8 channels. That's too much! I can't handle that! Jan 02 13:51:47 linux-0yez pulseaudio[2620]: [pulseaudio] alsa-mixer.c: Volume element PCM has 8 channels. That's too much! I can't handle that! Jan 02 13:51:47 linux-0yez pulseaudio[2620]: [pulseaudio] alsa-mixer.c: Volume element PCM has 8 channels. That's too much! I can't handle that! Jan 02 13:51:48 linux-0yez pulseaudio[2620]: [pulseaudio] x11wrap.c: XOpenDisplay() failed Jan 02 13:51:48 linux-0yez pulseaudio[2620]: [pulseaudio] module.c: Failed to load module "module-x11-publish" (argument: "display=:0"): initialization failed. Jan 02 13:52:12 linux-0yez pulseaudio[2620]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out ":0" is the correct display (`echo $DISPLAY` in konsole also shows ":0"). Manually starting pulseaudio with `/usr/bin/pulseaudio --start --log-target=syslog` after killing it does *not* reproduce the error. The error occurs on two different systems of mine (others don't use oS) with no overlapping hardware so far. Greetings Fabian -- You are receiving this mail because: You are on the CC list for the bug.