Bug 1270767 - Failed to open module module-bluez5-device.so
Summary: Failed to open module module-bluez5-device.so
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-12 10:56 UTC by Harald Hoyer
Modified: 2015-10-12 11:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-12 11:00:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Harald Hoyer 2015-10-12 10:56:08 UTC
pulseaudio[1411]: [pulseaudio] ltdl-bind-now.c: Failed to open module module-bluez5-device.so: module-bluez5-device.so: cannot open shared object file: No such file or directory
pulseaudio[1411]: [pulseaudio] module.c: Failed to open module "module-bluez5-device".
pulseaudio[1411]: [pulseaudio] module-bluez5-discover.c: Failed to load module for device /org/bluez/hci0/dev_C4_3A_BE_0B_8E_13


$ ls -l /usr/lib64/pulse-7.0/modules/module-bluez5-device.so
-rwxr-xr-x 1 root root 56360 28. Sep 01:37 /usr/lib64/pulse-7.0/modules/module-bluez5-device.so

$ rpm -qf /usr/lib64/pulse-7.0/modules/module-bluez5-device.so
pulseaudio-module-bluetooth-7.0-2.fc24.x86_64

$ rpm -q pulseaudio
pulseaudio-7.0-2.fc24.x86_64

Comment 1 Harald Hoyer 2015-10-12 10:57:26 UTC
$ sudo strace -f -e file -p 989 -p 1411
Process 989 attached with 3 threads
Process 1411 attached with 5 threads
[pid  1411] open("/usr/lib64/pulse-6.99/modules/module-bluez5-device.la", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid  1411] open("/lib64/module-bluez5-device.la", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid  1411] open("/usr/lib64/module-bluez5-device.la", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid  1411] open("/lib/module-bluez5-device.la", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid  1411] open("/usr/lib/module-bluez5-device.la", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid  1411] access("/usr/lib64/pulse-6.99/modules/module-bluez5-device.so", R_OK) = -1 ENOENT (No such file or directory)
[pid  1411] access("/lib64/module-bluez5-device.so", R_OK) = -1 ENOENT (No such file or directory)
[pid  1411] access("/usr/lib64/module-bluez5-device.so", R_OK) = -1 ENOENT (No such file or directory)
[pid  1411] access("/lib/module-bluez5-device.so", R_OK) = -1 ENOENT (No such file or directory)
[pid  1411] access("/usr/lib/module-bluez5-device.so", R_OK) = -1 ENOENT (No such file or directory)
[pid  1411] open("/usr/lib64/pulseaudio/module-bluez5-device.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid  1411] open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 23
[pid  1411] open("/lib64/tls/module-bluez5-device.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid  1411] open("/lib64/module-bluez5-device.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid  1411] open("/usr/lib64/tls/module-bluez5-device.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid  1411] open("/usr/lib64/module-bluez5-device.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid  1411] open("/usr/lib64/pulseaudio/module-bluez5-device.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid  1411] open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 23
[pid  1411] open("/lib64/tls/module-bluez5-device.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid  1411] open("/lib64/module-bluez5-device.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid  1411] open("/usr/lib64/tls/module-bluez5-device.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid  1411] open("/usr/lib64/module-bluez5-device.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

Comment 2 Harald Hoyer 2015-10-12 11:00:27 UTC
meh, that was after an update... sorry..


Note You need to log in before you can comment on or make changes to this bug.