Created attachment 860204 [details] u powerlog just before suspend, afther connecting Description of problem: when connectiong to a HP slim keyboard(bluetooth) upower things its a laptop battery thats empy and supsends afther 5 seconds Version-Release number of selected component (if applicable): UPower client version 0.99.0 UPower daemon version 0.99.0 How reproducible: always Steps to Reproduce: 1. boot pc 2. connect bluetooth keyboard 3. Actual results: goes in suspend, on recover still the battery icon empty sign ,device disconnected Expected results: no suspend because its not laptop battery (using desktop) Additional info: the upower findings are in attachment upower.log
added the bluetooth control log , it indicates a UUIDs has unsupported type don't know if this relevant? furthermore when resuming from standby and reconnecting the keyboard i can type and the pc does not go into suspend although there is an battery critical icon. [bluetooth]# connect 90:7F:61:92:5F:89 Attempting to connect to 90:7F:61:92:5F:89 [CHG] Device 90:7F:61:92:5F:89 Connected: yes [CHG] Device 90:7F:61:92:5F:89 Paired: yes Connection successful [CHG] Device 90:7F:61:92:5F:89 Modalias: usb:v03F0p034Cd0200 [CHG] Device 90:7F:61:92:5F:89 Modalias: usb:v03F0p034Cd0200 this is the run after the suspend and it seems no error of the UUIDs has unsupported type?
Created attachment 860235 [details] the Bluetooth log from connect to restore from suspend
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.