Bug 683615 - fc14 kde bluez 'bluetoothd[1590]: Clearing blocked list failed: Invalid argument (22)'
fc14 kde bluez 'bluetoothd[1590]: Clearing blocked list failed: Invalid argum...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: bluez (Show other bugs)
14
x86_64 Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-03-09 16:04 EST by collura
Modified: 2011-05-18 18:01 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-05-18 18:01:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description collura 2011-03-09 16:04:26 EST
Description of problem:
 was looking through var log messages of a test install machine for something else and ran across this bluetooth errormessage about invalid argument which looks worth reporting.  didnt see it in any of the other bluez bugreports i skimmed so here it is.

Version-Release number of selected component (if applicable):
 bluez-4.77-1.fc14.x86_64

How reproducible:
 always; fedora 14 kde updates-test repo

Steps to Reproduce:
1. boot and read /var/log/messages
2.
3.
  
Actual results:
 get log entry about invalid argument error 

Expected results:
 no error

Additional info:

exerpt from /var/log/messages:

Mar  9 12:27:49 xxxxx bluetoothd[1586]: Bluetooth deamon 4.77
Mar  9 12:27:49 xxxxx bluetoothd[1590]: Starting SDP server
Mar  9 12:27:49 xxxxx kernel: [   31.529695] Bluetooth: L2CAP ver 2.14
Mar  9 12:27:49 xxxxx kernel: [   31.529707] Bluetooth: L2CAP socket layer initialized
Mar  9 12:27:49 xxxxx kernel: [   31.581621] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Mar  9 12:27:49 xxxxx kernel: [   31.581631] Bluetooth: BNEP filters: protocol multicast
Mar  9 12:27:49 xxxxx bluetoothd[1590]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Mar  9 12:27:49 xxxxx bluetoothd[1590]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Mar  9 12:27:49 xxxxx bluetoothd[1590]: HCI dev 0 registered
Mar  9 12:27:49 xxxxx kernel: [   31.619095] Bluetooth: SCO (Voice Link) ver 0.6
Mar  9 12:27:49 xxxxx kernel: [   31.619105] Bluetooth: SCO socket layer initialized
Mar  9 12:27:49 xxxxx NetworkManager[1267]: <warn> bluez error getting default adapter: No such adapter

...

Mar  9 12:27:49 xxxxx bluetoothd[1590]: HCI dev 0 up
Mar  9 12:27:49 xxxxx bluetoothd[1590]: Starting security manager 0
Mar  9 12:27:49 xxxxx bluetoothd[1590]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Mar  9 12:27:49 xxxxx kernel: [   31.888795] Bluetooth: RFCOMM TTY layer initialized
Mar  9 12:27:49 xxxxx kernel: [   31.888817] Bluetooth: RFCOMM socket layer initialized
Mar  9 12:27:49 xxxxx kernel: [   31.888823] Bluetooth: RFCOMM ver 1.11
Mar  9 12:27:49 xxxxx bluetoothd[1590]: Clearing blocked list failed: Invalid argument (22)
Mar  9 12:27:49 xxxxx bluetoothd[1590]: Adapter /org/bluez/1586/hci0 has been enabled
Comment 1 Bastien Nocera 2011-05-18 18:01:05 EDT
It's a harmless warning that the kernel doesn't support that functionality. Problem has fixed itself in Fedora 15 as the kernel support was merged.

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