2

I have noticed that this problem has been asked about many times but none of the answers that I have seen so far work for me.

Today in the morning I went to my computer and tried listening to some music but there was no sound. At first I just thought that volume was low or that it was muted but when I tried to turn up the volume it didn't work. I tried looking around the Internet for solutions but sadly nothing works.

Screen Shot of Volume menu:

Click here to see the screen shot

Results of fgrep -i pulse /var/log/syslog:

Failed to open module /usr/lib/pulse-8.0/modules/module-bluetooth-policy.so: /usr/lib/pulse-8.0/modules/module-bluetooth-policy.so: wrong ELF class: ELFCLASS64
Jul 11 14:04:09 d3faulto-comp pulseaudio[1363]: [pulseaudio] module.c: Failed to open module "module-bluetooth-policy".
Jul 11 14:04:09 d3faulto-comp pulseaudio[1363]: [pulseaudio] main.c: Module load failed.
Jul 11 14:04:09 d3faulto-comp pulseaudio[1363]: [pulseaudio] main.c: Failed to initialize daemon.
Jul 11 14:04:09 d3faulto-comp pulseaudio[1360]: [pulseaudio] main.c: Daemon startup failed.
Jul 11 14:04:10 d3faulto-comp pulseaudio[1374]: [pulseaudio] ltdl-bind-now.c: Failed to open module /usr/lib/pulse-8.0/modules/module-bluetooth-policy.so: /usr/lib/pulse-8.0/modules/module-bluetooth-policy.so: wrong ELF class: ELFCLASS64
Jul 11 14:04:10 d3faulto-comp pulseaudio[1374]: [pulseaudio] module.c: Failed to open module "module-bluetooth-policy".
Jul 11 14:04:10 d3faulto-comp pulseaudio[1374]: [pulseaudio] main.c: Module load failed.
Jul 11 14:04:10 d3faulto-comp pulseaudio[1374]: [pulseaudio] main.c: Failed to initialize daemon.
Jul 11 14:04:10 d3faulto-comp pulseaudio[1371]: [pulseaudio] main.c: Daemon startup failed.
Jul 11 14:04:11 d3faulto-comp pulseaudio[1381]: [pulseaudio] ltdl-bind-now.c: Failed to open module /usr/lib/pulse-8.0/modules/module-bluetooth-policy.so: /usr/lib/pulse-8.0/modules/module-bluetooth-policy.so: wrong ELF class: ELFCLASS64
Jul 11 14:04:11 d3faulto-comp pulseaudio[1381]: [pulseaudio] module.c: Failed to open module "module-bluetooth-policy".
Jul 11 14:04:11 d3faulto-comp pulseaudio[1381]: [pulseaudio] main.c: Module load failed.
Jul 11 14:04:11 d3faulto-comp pulseaudio[1381]: [pulseaudio] main.c: Failed to initialize daemon.
Jul 11 14:04:11 d3faulto-comp pulseaudio[1378]: [pulseaudio] main.c: Daemon startup failed.
Jul 11 14:04:12 d3faulto-comp pulseaudio[1388]: [pulseaudio] ltdl-bind-now.c: Failed to open module /usr/lib/pulse-8.0/modules/module-bluetooth-policy.so: /usr/lib/pulse-8.0/modules/module-bluetooth-policy.so: wrong ELF class: ELFCLASS64
Jul 11 14:04:12 d3faulto-comp pulseaudio[1388]: [pulseaudio] module.c: Failed to open module "module-bluetooth-policy".
Jul 11 14:04:12 d3faulto-comp pulseaudio[1388]: [pulseaudio] main.c: Module load failed.
Jul 11 14:04:12 d3faulto-comp pulseaudio[1388]: [pulseaudio] main.c: Failed to initialize daemon.
Jul 11 14:04:12 d3faulto-comp pulseaudio[1385]: [pulseaudio] main.c: Daemon startup failed.
Jul 11 14:04:13 d3faulto-comp pulseaudio[1395]: [pulseaudio] ltdl-bind-now.c: Failed to open module /usr/lib/pulse-8.0/modules/module-bluetooth-policy.so: /usr/lib/pulse-8.0/modules/module-bluetooth-policy.so: wrong ELF class: ELFCLASS64
Jul 11 14:04:13 d3faulto-comp pulseaudio[1395]: [pulseaudio] module.c: Failed to open module "module-bluetooth-policy".
Jul 11 14:04:13 d3faulto-comp pulseaudio[1395]: [pulseaudio] main.c: Module load failed.
Jul 11 14:04:13 d3faulto-comp pulseaudio[1395]: [pulseaudio] main.c: Failed to initialize daemon.
Jul 11 14:04:13 d3faulto-comp pulseaudio[1392]: [pulseaudio] main.c: Daemon startup failed.
Jul 11 14:04:14 d3faulto-comp pulseaudio[1405]: [pulseaudio] ltdl-bind-now.c: Failed to open module /usr/lib/pulse-8.0/modules/module-bluetooth-policy.so: /usr/lib/pulse-8.0/modules/module-bluetooth-policy.so: wrong ELF class: ELFCLASS64

Just kept on going with the same error for 6826 times.

13

1 Answer 1

1

It appears that that there is a bug report filed for this which might or might not be related to Skype.

The problem

The error message mentions that there's a problem with a PulseAudio module.

Solution 1: disabling the module

If you'd like to try disabling the module, which might make Bluetooth audio not work, open a terminal (press Ctrl+Alt+T), and run the following:

sudo sed -i 's/^load-module module-bluetooth-policy/#load-module module-bluetooth-policy/' /etc/pulse/default.pa
sudo service pulseaudio restart
sleep 15
pulseaudio -k
pulseaudio --start
pavucontrol

If the PulseAudio volume control shows up properly, you should have sound.

Reenabling the module

If that doesn't fix it, open a terminal and run:

sudo sed -i 's/^#load-module module-bluetooth-policy/load-module module-bluetooth-policy/' /etc/pulse/default.pa
sudo service pulseaudio restart
sleep 15
pulseaudio -k
pulseaudio --start

Solution 2: reinstalling the Bluetooth module

If you'd like to try reinstalling Ubuntu's version of the module, which might make Skype not work, open a terminal (press Ctrl+Alt+T) and run:

sudo apt update
sudo apt install --reinstall pulseaudio-module-bluetooth
sudo service pulseaudio restart
sleep 15
pulseaudio -k
pulseaudio --start
pavucontrol

If the PulseAudio volume control shows up properly, you should have sound.

8
  • sorry but it did not not the first or second solution. When I put in pulseaudio -k I get an erroe saying E: [pulseaudio] main.c: Failed to kill daemon: No such process
    – user487038
    Jul 12, 2016 at 2:15
  • Please put the results of fgrep -i pulse /var/log/syslog in your question. It might have a new error.
    – Olathe
    Jul 12, 2016 at 2:18
  • same error form last time when I run fpreg -i pulse /var/log/syslog the results were Jul 11 18:21:26 d3faulto-comp pulseaudio[13229]: [pulseaudio] module.c: Failed to open module "module-bluetooth-policy". Jul 11 18:21:26 d3faulto-comp pulseaudio[13229]: [pulseaudio] main.c: Module load failed. Jul 11 18:21:26 d3faulto-comp pulseaudio[13229]: [pulseaudio] main.c: Failed to initialize daemon.
    – user487038
    Jul 12, 2016 at 2:21
  • OK, that might be a bit different. Try the new solution 1. If it fails, see what fgrep -i pulse /var/log/syslog says.
    – Olathe
    Jul 12, 2016 at 2:29
  • whats the new solution?
    – user487038
    Jul 12, 2016 at 2:39

You must log in to answer this question.