[Bug 586231] New: Bluetooth not avaliable for users trough d-bus

newer
[Bug 586583] New: Some ACPI ASUS...

older
[Bug 540246] New: Charset problem...

bugzilla_noreply＠novell.com

8 Mar 2010 8 Mar '10

12:06

http://bugzilla.novell.com/show_bug.cgi?id=586231 http://bugzilla.novell.com/show_bug.cgi?id=586231#c0 Summary: Bluetooth not avaliable for users trough d-bus Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: i686 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team@suse.de ReportedBy: highwaystar.ru@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.10 Firefox/3.6 Currently users forom group "users" cant access bluetooth device trough d-bus with graphic frontends such as kbluetooth Reproducible: Always Steps to Reproduce: 1. Swith on or plugin bluetooth dongle 2. Try to search devices or simple change settings in kbluetooth 3. Actual Results: Kbluetooth will find nothing or even crash. This happens due <policy group="lp"> <allow send_destination="org.bluez"/> </policy> in /etc/dbus-1/system.d/bluetooth.conf Expected Results: When i changed group lp to users I able to search and work with bluetooth devices from kbluetooth. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

8 Mar 8 Mar

12:14

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

http://bugzilla.novell.com/show_bug.cgi?id=586231 http://bugzilla.novell.com/show_bug.cgi?id=586231#c1 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |seife@novell.slipkontur.de, | |vbotka@novell.com Info Provider| |jsmeix@novell.com --- Comment #1 from Ludwig Nussel 2010-03-08 13:14:15 CET --- you're automatically able to use bluetooth when you are logged in locally if you use a displaymanager or stay at the console. Anyways, I'm curious about that lp group exception. What's that needed for? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

9 Mar 9 Mar

08:45

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

http://bugzilla.novell.com/show_bug.cgi?id=586231 http://bugzilla.novell.com/show_bug.cgi?id=586231#c2 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |jsmeix@novell.com Info Provider|jsmeix@novell.com | --- Comment #2 from Johannes Meixner 2010-03-09 08:45:19 UTC --- I am afraid, I cannot answer questions regarding bluetooth because I don't know about bluetooth - in particular I do not have bluetooth hardware and I don't know about the current state of the bluez-cups or similar packages. Regarding printer access via bluetooth, have a look at bug #467220 In general, any CUPS backend is by default run by the cupsd as user "lp" (see "man 7 backend" how to run it as root) so that device nodes which are used for printer access must have read/write permissions for the user "lp" (or the group "lp"). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:15

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

http://bugzilla.novell.com/show_bug.cgi?id=586231 http://bugzilla.novell.com/show_bug.cgi?id=586231#c3 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |highwaystar.ru@gmail.com --- Comment #3 from Ludwig Nussel 2010-03-09 11:15:19 CET --- that gives cups full access to bluetooth but well.. I'd recommend to move the dbus rule from cups to bluez-cups so it only gets applied if it's actually needed. Anyways, back to the original report. How did you login? output of ck-list-sessions? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:42

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

http://bugzilla.novell.com/show_bug.cgi?id=586231 http://bugzilla.novell.com/show_bug.cgi?id=586231#c4 Vitaliy Tomin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|highwaystar.ru@gmail.com | --- Comment #4 from Vitaliy Tomin 2010-03-09 13:42:54 UTC --- I'm login trough kdm, autologin enabled. output of ck-list-sessions: user@linux-tlu3:~> ck-list-sessions Session1: unix-user = '1000' realname = 'user' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2010-03-09T13:36:03.768291Z' login-session-id = '' /var/log/messages when bluetooth dongle inserted: Mar 9 21:38:47 linux-tlu3 kernel: [ 190.520080] usb 4-1: new full speed USB device using ohci_hcd and address 2 Mar 9 21:38:47 linux-tlu3 kernel: [ 190.687235] usb 4-1: New USB device found, idVendor=0a12, idProduct=0001 Mar 9 21:38:47 linux-tlu3 kernel: [ 190.687245] usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Mar 9 21:38:47 linux-tlu3 kernel: [ 190.760285] Bluetooth: Core ver 2.15 Mar 9 21:38:47 linux-tlu3 kernel: [ 190.760490] NET: Registered protocol family 31 Mar 9 21:38:47 linux-tlu3 kernel: [ 190.760497] Bluetooth: HCI device and connection manager initialized Mar 9 21:38:47 linux-tlu3 kernel: [ 190.760504] Bluetooth: HCI socket layer initialized Mar 9 21:38:47 linux-tlu3 kernel: [ 190.785750] Bluetooth: Generic Bluetooth USB driver ver 0.6 Mar 9 21:38:47 linux-tlu3 kernel: [ 190.785937] usbcore: registered new interface driver btusb Mar 9 21:38:47 linux-tlu3 bluetoothd[3743]: Bluetooth daemon 4.61 Mar 9 21:38:47 linux-tlu3 bluetoothd[3744]: Starting SDP server Mar 9 21:38:47 linux-tlu3 kernel: [ 190.878173] Bluetooth: L2CAP ver 2.14 Mar 9 21:38:47 linux-tlu3 kernel: [ 190.878179] Bluetooth: L2CAP socket layer initialized Mar 9 21:38:47 linux-tlu3 bluetoothd[3744]: Starting experimental netlink support Mar 9 21:38:47 linux-tlu3 bluetoothd[3744]: Failed to find Bluetooth netlink family Mar 9 21:38:47 linux-tlu3 bluetoothd[3744]: Failed to init netlink plugin Mar 9 21:38:47 linux-tlu3 bluetoothd[3744]: Parsing /etc/bluetooth/network.conf failed: No such file or directory Mar 9 21:38:47 linux-tlu3 kernel: [ 190.917835] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Mar 9 21:38:47 linux-tlu3 kernel: [ 190.917842] Bluetooth: BNEP filters: protocol multicast Mar 9 21:38:47 linux-tlu3 bluetoothd[3744]: bridge pan0 created Mar 9 21:38:47 linux-tlu3 bluetoothd[3744]: Parsing /etc/bluetooth/input.conf failed: No such file or directory Mar 9 21:38:47 linux-tlu3 bluetoothd[3744]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory Mar 9 21:38:47 linux-tlu3 kernel: [ 190.958705] Bridge firewalling registered Mar 9 21:38:47 linux-tlu3 bluetoothd[3744]: HCI dev 0 registered Mar 9 21:38:47 linux-tlu3 kernel: [ 190.969206] Bluetooth: SCO (Voice Link) ver 0.6 Mar 9 21:38:47 linux-tlu3 kernel: [ 190.969212] Bluetooth: SCO socket layer initialized Mar 9 21:38:47 linux-tlu3 bluetoothd[3744]: HCI dev 0 up Mar 9 21:38:47 linux-tlu3 bluetoothd[3744]: Starting security manager 0 Mar 9 21:38:52 linux-tlu3 bluetoothd[3744]: Can't read address for hci0: Connection timed out (110) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:46

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

http://bugzilla.novell.com/show_bug.cgi?id=586231 http://bugzilla.novell.com/show_bug.cgi?id=586231#c5 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@novell.com Component|Security |KDE4 Workspace AssignedTo|security-team@suse.de |kde-maintainers@suse.de --- Comment #5 from Ludwig Nussel 2010-03-09 14:46:24 CET --- no idea. maybe a dup of bug 574547 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:47

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

http://bugzilla.novell.com/show_bug.cgi?id=586231 http://bugzilla.novell.com/show_bug.cgi?id=586231#c6 Vladimir Botka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Component|KDE4 Workspace |Security Info Provider| |highwaystar.ru@gmail.com AssignedTo|kde-maintainers@suse.de |security-team@suse.de --- Comment #6 from Vladimir Botka 2010-03-09 13:47:41 UTC --- There is no such a problem with gnome-applet in 11.3 MS2 [1]. gnome-applet is running as user [2] but when the applet is scanning I can see the d-bus messages in "dbus-monitor --system" instead of "--session". Maybe kbluetooth could adopt the same approach as gnome-applet did. # uname -a Linux gucci 2.6.33-rc7-3-desktop #1 SMP PREEMPT 2010-02-12 17:37:20 +0100 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/SuSE-release openSUSE 11.3 Milestone 2 (x86_64) VERSION = 11.3 # ps aux | grep bluetooth-applet vlado 488 0.0 1.2 218016 12980 ? S 14:18 0:00 bluetooth-applet -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14:19

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

http://bugzilla.novell.com/show_bug.cgi?id=586231 http://bugzilla.novell.com/show_bug.cgi?id=586231#c7 --- Comment #7 from Vitaliy Tomin 2010-03-09 14:19:01 UTC --- now I reattach bluetooth adapter and it starts working there is another output from in messages ar 9 21:54:55 linux-tlu3 kernel: [ 1158.344082] usb 4-1: new full speed USB device using ohci_hcd and address 3 Mar 9 21:54:55 linux-tlu3 kernel: [ 1158.511236] usb 4-1: New USB device found, idVendor=0a12, idProduct=0001 Mar 9 21:54:55 linux-tlu3 kernel: [ 1158.511245] usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Mar 9 21:54:55 linux-tlu3 bluetoothd[11394]: Bluetooth daemon 4.61 Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: Starting SDP server Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: Starting experimental netlink support Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: Failed to find Bluetooth netlink family Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: Failed to init netlink plugin Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: Parsing /etc/bluetooth/network.conf failed: No such file or directory Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: bridge pan0 created Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: Parsing /etc/bluetooth/input.conf failed: No such file or directory Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: HCI dev 0 registered Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: HCI dev 0 up Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: Starting security manager 0 Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory Mar 9 21:54:55 linux-tlu3 kernel: [ 1158.671298] Bluetooth: RFCOMM TTY layer initialized Mar 9 21:54:55 linux-tlu3 kernel: [ 1158.671310] Bluetooth: RFCOMM socket layer initialized Mar 9 21:54:55 linux-tlu3 kernel: [ 1158.671315] Bluetooth: RFCOMM ver 1.11 Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: Adapter /org/bluez/11394/hci0 has been enabled ------------------------ now no "Can't read address for hci0:" strings but reattaching again make bluetooth not work -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14:28

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

http://bugzilla.novell.com/show_bug.cgi?id=586231 http://bugzilla.novell.com/show_bug.cgi?id=586231#c8 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Component|Security |KDE4 Workspace Info Provider|highwaystar.ru@gmail.com | AssignedTo|security-team@suse.de |kde-maintainers@suse.de --- Comment #8 from Ludwig Nussel 2010-03-09 15:28:54 CET --- in any case it's not a security issue -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13 Aug 13 Aug

20:47

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

http://bugzilla.novell.com/show_bug.cgi?id=586231 http://bugzilla.novell.com/show_bug.cgi?id=586231#c9 Christian Trippe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |ctrippe@gmx.net InfoProvider| |highwaystar.ru@gmail.com --- Comment #9 from Christian Trippe 2010-08-13 20:47:12 UTC --- Is this still a problem with the final version of openSUSE 11.3? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

20 Sep 20 Sep

19:51

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

https://bugzilla.novell.com/show_bug.cgi?id=586231 https://bugzilla.novell.com/show_bug.cgi?id=586231#c10 Christian Trippe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|highwaystar.ru@gmail.com | Resolution| |NORESPONSE --- Comment #10 from Christian Trippe 2010-09-20 19:51:15 UTC --- No reply in more than 4 weeks. Please reopen if you are able to provide the requested information. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

21 Sep 21 Sep

05:36

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

https://bugzilla.novell.com/show_bug.cgi?id=586231 https://bugzilla.novell.com/show_bug.cgi?id=586231#c11 Vladimir Botka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NORESPONSE | --- Comment #11 from Vladimir Botka 2010-09-21 05:36:55 UTC --- (In reply to comment #7)

...

now I reattach bluetooth adapter and it starts working Mar 9 21:54:55 linux-tlu3 bluetoothd[11396]: Adapter /org/bluez/11394/hci0 has been enabled

now no "Can't read address for hci0:" strings but reattaching again make bluetooth not work

The bt adapter seems to be not initialized properly. This may be the reason for "Can't read address for hci0:" For the record it would be good know the brand of the bt adapter. Would it be possible to post the output of "hwinfo --bluetooth" and "hciconfig -a". Besides reattaching the bt adapter, does "hciconfig hci0 reset" help too ? I reopened to gather the info. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

05:39

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

https://bugzilla.novell.com/show_bug.cgi?id=586231 https://bugzilla.novell.com/show_bug.cgi?id=586231#c12 Vladimir Botka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |highwaystar.ru@gmail.com --- Comment #12 from Vladimir Botka 2010-09-21 05:39:02 UTC --- Vitaliy, could you post the info from C#11 ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

06:56

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

https://bugzilla.novell.com/show_bug.cgi?id=586231 https://bugzilla.novell.com/show_bug.cgi?id=586231#c13 Vitaliy Tomin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|highwaystar.ru@gmail.com | --- Comment #13 from Vitaliy Tomin 2010-09-21 06:56:38 UTC --- Sorry for late reply, when you ask first i have not bt sdapter, then forget to test. I have this BT adapter http://www.dealextreme.com/details.dx/sku.11866 hwinfo --bluetooth 12: USB 00.0: 11500 Bluetooth Device [Created at usb.122] Unique ID: mZxt.nQKjiuCfL84 Parent ID: uIhY.7qWCOCfUJwE SysFS ID: /devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.0 SysFS BusID: 3-2:1.0 Hardware Class: bluetooth Model: "Cambridge Silicon Radio Bluetooth Dongle (HCI mode)" Hotplug: USB Vendor: usb 0x0a12 "Cambridge Silicon Radio, Ltd" Device: usb 0x0001 "Bluetooth Dongle (HCI mode)" Revision: "19.15" Driver: "btusb" Driver Modules: "btusb" Speed: 12 Mbps Module Alias: "usb:v0A12p0001d1915dcE0dsc01dp01icE0isc01ip01" Driver Info #0: Driver Status: btusb is active Driver Activation Cmd: "modprobe btusb" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #3 (Hub) hciconfig -a hci0: Type: BR/EDR Bus: USB BD Address: 00:1F:81:00:02:50 ACL MTU: 1021:4 SCO MTU: 180:1 UP RUNNING RX bytes:68 acl:0 sco:0 events:6 errors:0 TX bytes:18 acl:0 sco:0 commands:8 errors:2 Features: 0xff 0x3e 0x0d 0x76 0x80 0x01 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: Link mode: SLAVE ACCEPT Can't read local name on hci0: Connection timed out (110) /var/log/messages on first attatch: ------------------------------------------------------------------------ Sep 21 15:32:24 linux-f4uk kernel: [15881.804082] usb 3-2: new full speed USB device using ohci_hcd and address 3 Sep 21 15:32:25 linux-f4uk kernel: [15881.952040] usb 3-2: New USB device found, idVendor=0a12, idProduct=0001 Sep 21 15:32:25 linux-f4uk kernel: [15881.952049] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Sep 21 15:32:25 linux-f4uk kernel: [15881.994821] Bluetooth: Core ver 2.15 Sep 21 15:32:25 linux-f4uk kernel: [15881.994913] NET: Registered protocol family 31 Sep 21 15:32:25 linux-f4uk kernel: [15881.994915] Bluetooth: HCI device and connection manager initialized Sep 21 15:32:25 linux-f4uk kernel: [15881.994919] Bluetooth: HCI socket layer initialized Sep 21 15:32:25 linux-f4uk kernel: [15882.007744] Bluetooth: Generic Bluetooth USB driver ver 0.6 Sep 21 15:32:25 linux-f4uk kernel: [15882.007887] usbcore: registered new interface driver btusb Sep 21 15:32:25 linux-f4uk bluetoothd[8269]: Bluetooth daemon 4.64 Sep 21 15:32:25 linux-f4uk bluetoothd[8270]: Starting SDP server Sep 21 15:32:25 linux-f4uk kernel: [15882.081215] Bluetooth: L2CAP ver 2.14 Sep 21 15:32:25 linux-f4uk kernel: [15882.081220] Bluetooth: L2CAP socket layer initialized Sep 21 15:32:25 linux-f4uk bluetoothd[8270]: Starting experimental netlink support Sep 21 15:32:25 linux-f4uk bluetoothd[8270]: Failed to find Bluetooth netlink family Sep 21 15:32:25 linux-f4uk bluetoothd[8270]: Failed to init netlink plugin Sep 21 15:32:25 linux-f4uk bluetoothd[8270]: Parsing /etc/bluetooth/network.conf failed: No such file or directory Sep 21 15:32:25 linux-f4uk kernel: [15882.134528] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Sep 21 15:32:25 linux-f4uk kernel: [15882.134534] Bluetooth: BNEP filters: protocol multicast Sep 21 15:32:25 linux-f4uk kernel: [15882.168832] Bridge firewalling registered Sep 21 15:32:25 linux-f4uk bluetoothd[8270]: bridge pan0 created Sep 21 15:32:25 linux-f4uk bluetoothd[8270]: Parsing /etc/bluetooth/input.conf failed: No such file or directory Sep 21 15:32:25 linux-f4uk bluetoothd[8270]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory Sep 21 15:32:25 linux-f4uk bluetoothd[8270]: HCI dev 0 registered Sep 21 15:32:25 linux-f4uk kernel: [15882.180222] Bluetooth: SCO (Voice Link) ver 0.6 Sep 21 15:32:25 linux-f4uk kernel: [15882.180228] Bluetooth: SCO socket layer initialized Sep 21 15:32:25 linux-f4uk bluetoothd[8270]: HCI dev 0 up Sep 21 15:32:25 linux-f4uk bluetoothd[8270]: Starting security manager 0 Sep 21 15:32:30 linux-f4uk bluetoothd[8270]: Can't read version info for /org/bluez/8269/hci0: Connection timed out (110) ------------------------------------------------------------------------ Trying to find phone via bluetooth or my pc from phone - without succes. messages after hciconfig hci0 reset ------------------------------------------------------------------------ Sep 21 15:35:45 linux-f4uk kernel: [16082.623794] hci_cmd_task: hci0 command tx timeout Sep 21 15:37:55 linux-f4uk su: (to root) user on /dev/pts/1 Sep 21 15:38:10 linux-f4uk kernel: [16227.739411] hci_cmd_task: hci0 command tx timeout Sep 21 15:38:39 linux-f4uk kernel: [16256.252636] hci_cmd_task: hci0 command tx timeout Sep 21 15:38:41 linux-f4uk kernel: [16258.237455] hci_cmd_task: hci0 command tx timeout Sep 21 15:38:50 linux-f4uk bluetoothd[8270]: HCI dev 0 down Sep 21 15:38:50 linux-f4uk bluetoothd[8270]: Adapter /org/bluez/8269/hci0 has been disabled Sep 21 15:38:50 linux-f4uk bluetoothd[8270]: Stopping security manager 0 ------------------------------------------------------------------------ Reset doesnt help, I still cant discovery phone via bluetooth. /var/log/messages after reattaching: ------------------------------------------------------------------------ Sep 21 15:41:45 linux-f4uk kernel: [16442.078069] usb 3-2: new full speed USB device using ohci_hcd and address 4 Sep 21 15:41:45 linux-f4uk kernel: [16442.226326] usb 3-2: New USB device found, idVendor=0a12, idProduct=0001 Sep 21 15:41:45 linux-f4uk kernel: [16442.226334] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Sep 21 15:41:45 linux-f4uk bluetoothd[8270]: HCI dev 0 registered Sep 21 15:41:45 linux-f4uk bluetoothd[8270]: HCI dev 0 up Sep 21 15:41:45 linux-f4uk bluetoothd[8270]: Starting security manager 0 Sep 21 15:41:45 linux-f4uk bluetoothd[8270]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory Sep 21 15:41:45 linux-f4uk kernel: [16442.357307] Bluetooth: RFCOMM TTY layer initialized Sep 21 15:41:45 linux-f4uk kernel: [16442.357319] Bluetooth: RFCOMM socket layer initialized Sep 21 15:41:45 linux-f4uk kernel: [16442.357324] Bluetooth: RFCOMM ver 1.11 Sep 21 15:41:45 linux-f4uk bluetoothd[8270]: Adapter /org/bluez/8269/hci0 has been enabled ------------------------------------------------------------------------ After reattaching BT starts work. Phone finded with KBluetooth without any problems. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:17

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

https://bugzilla.novell.com/show_bug.cgi?id=586231 https://bugzilla.novell.com/show_bug.cgi?id=586231#c14 --- Comment #14 from Vladimir Botka 2010-09-21 09:17:24 UTC --- (In reply to comment #13)

...

Model: "Cambridge Silicon Radio Bluetooth Dongle (HCI mode)" Vendor: usb 0x0a12 "Cambridge Silicon Radio, Ltd" Device: usb 0x0001 "Bluetooth Dongle (HCI mode)"

There is a "bccmd" command line utility to manipulate CSR chips. This utility comes with the bluez package. You can try "bccmd warmreset" for example. Maybe other bccmd commands could help you too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

28 Jan 28 Jan

14:08

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

https://bugzilla.novell.com/show_bug.cgi?id=586231 https://bugzilla.novell.com/show_bug.cgi?id=586231#c15 Christian Trippe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |highwaystar.ru@gmail.com --- Comment #15 from Christian Trippe 2012-01-28 14:08:55 UTC --- openSUSE 11.3 is out of maintenance. Is this bug still valid with openSUSE 12.1? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19 Mar 19 Mar

19:42

New subject: [Bug 586231] Bluetooth not avaliable for users trough d-bus

https://bugzilla.novell.com/show_bug.cgi?id=586231 https://bugzilla.novell.com/show_bug.cgi?id=586231#c16 Christian Trippe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|highwaystar.ru@gmail.com | Resolution| |NORESPONSE --- Comment #16 from Christian Trippe 2012-03-19 19:42:36 UTC --- No reply in more than 4 weeks. Please reopen if you are able to provide the requested information. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

4422

Age (days ago)

5164

Last active (days ago)

List overview

Download

16 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 586231] New: Bluetooth not avaliable for users trough d-bus

tags

participants (1)