On Thu, May 26, 2016 at 5:08 AM, Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx> wrote: > hello, > I have a Samsung S Action Mouse ET-MP900D that I'm trying to connect from my > laptop: Asus U36SD with Fedora 23. > > I can pair and connect to the mouse both from a Samsung S2 phone and from a > Samsung Pro 12.2 tablet. > > I remember in the past on the same PC with Fedora 21 I was able to connect > to this mouse. > > But now on fedora 23 I get: > > [root@ope46 ~]# bluetoothctl > [NEW] Controller 74:2F:68:83:D4:3F ChromeLinux_D1F5 [default] > [NEW] Device E4:B0:21:98:DB:CA GT-I9100 > [NEW] Device F0:65:DD:80:A3:0E Samsung S Action Mouse ET-MP900D > [bluetooth]# > > [bluetooth]# info F0:65:DD:80:A3:0E > Device F0:65:DD:80:A3:0E > Name: Samsung S Action Mouse ET-MP900D > Alias: Samsung S Action Mouse ET-MP900D > Class: 0x002580 > Icon: input-mouse > Paired: yes > Trusted: yes > Blocked: no > Connected: no > LegacyPairing: no > UUID: Service Discovery Serve.. (00001000-0000-1000-8000-00805f9b34fb) > UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb) > UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) > Modalias: usb:v04E8pA004d0216 > [bluetooth]# > > But > > [bluetooth]# connect F0:65:DD:80:A3:0E > Attempting to connect to F0:65:DD:80:A3:0E > Failed to connect: org.bluez.Error.Failed > [bluetooth]# > > [root@ope46 ~]# systemctl status bluetooth -l > ● bluetooth.service - Bluetooth service > Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; > vendor preset: enabled) > Active: active (running) since Thu 2016-05-26 12:43:46 CEST; 20min ago > Docs: man:bluetoothd(8) > Main PID: 789 (bluetoothd) > Status: "Running" > CGroup: /system.slice/bluetooth.service > └─789 /usr/libexec/bluetooth/bluetoothd > > May 26 12:44:37 ope46 bluetoothd[789]: Can't get HIDP connection info > May 26 12:44:37 ope46 bluetoothd[789]: connect error: Connection refused > (111) > May 26 12:44:57 ope46 bluetoothd[789]: Can't get HIDP connection info > May 26 12:44:57 ope46 bluetoothd[789]: connect error: Connection refused > (111) > May 26 12:58:41 ope46 bluetoothd[789]: Can't get HIDP connection info > May 26 12:58:46 ope46 bluetoothd[789]: connect error: Host is down (112) > May 26 12:59:26 ope46 bluetoothd[789]: Can't get HIDP connection info > May 26 12:59:31 ope46 bluetoothd[789]: connect error: Host is down (112) > May 26 13:03:07 ope46 bluetoothd[789]: Can't get HIDP connection info > May 26 13:03:12 ope46 bluetoothd[789]: connect error: Host is down (112) > > Tried also from mate and from kde sessio s with same results. > > Device added successfully, but failed to connect > > Connection Failed: blueman.bluez.errors.DBusFailedError: Input/output error > > I also found some reference to create file /etc/sysconfig/bluetooth and > include > > HID2HCI_ENABLE=true > > But after done and reboot same behavior. > > How to debug further? I have the same problems with Fedora 23 and 24. The bluetooth mouse business is sort of a mess. bluetooth mouse isn't active at login window after booting https://bugzilla.redhat.com/show_bug.cgi?id=1337353 bluetooth mouse randomly stops working, manual reconnection is required https://bugzilla.redhat.com/show_bug.cgi?id=1340659 can't connect to bluetooth devices unless wireless is disabled first https://bugzilla.redhat.com/show_bug.cgi?id=1340620 bluetooth cannot be enabled in the GUI, doesn't see hardware, bluetoothctl works OK https://bugzilla.redhat.com/show_bug.cgi?id=1318441 The last comment in the last bug might have a hint for your situation, which is $ sudo systemctl --global enable obex; but I've only just used that and it's too soon to tell if it'll fix any of the problems I'm having. -- Chris Murphy -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
