Unable to connect to Pebble #52
Comments
Please provide:
|
It's hard to copy and paste from the Jolla terminal, but I'll type over Active: failed (result: start-limit) since Mon 2015-04-20 14:12:06 CEST; 9h /usr/bin/pebbled gives: Symbol lookup error: /usr/bin/pebbled: undefined symbol: Thanks!
|
This really looks like your system is broken. QtBluetooth should be pulled-in by package dependency. |
I simply installed via Warehouse - everything else works fine. Can I 2015-04-21 16:12 GMT+02:00 Tomasz Sterna notifications@github.com:
Reinout van Schouwen |
Further info: 'pkcon search qtbluetooth' confirms that 2015-04-21 21:28 GMT+02:00 Reinout van Schouwen reinout@gmail.com:
Reinout van Schouwen |
I have shown that QtBluetooth is actually installed, so my system isn't broken (at least not in that respect). What else can I do to resolve this problem? |
Are the files there? You should have the following in /usr/lib/: libQt5Bluetooth.so.5 libQt5Bluetooth.so.5.2 libQt5Bluetooth.so.5.2.2 The first two are symlinks to the third. |
Confirmed, they are there. libQtBluetooth.so.5.2.2 has a size of 327464 2015-04-28 23:31 GMT+02:00 Andrew Branson notifications@github.com:
Reinout van Schouwen |
Mine is: -rwxr-xr-x 1 root root 324332 Apr 8 22:31 libQt5Bluetooth.so.5.2.2 I don't know what the significance of that difference is. I just updated to the 1.1.4.29 jolla update this evening. |
I'm still on 1.1.2.16 waiting for the GA of the update. My 2015-04-28 23:53 GMT+02:00 Andrew Branson notifications@github.com:
Reinout van Schouwen |
Looks to me that it should be the same. Pkcon tells me I have the same version installed as you do: qt5-qtconnectivity-qtbluetooth-5.2.0+git0-1.4.6.armv7hl. That package isn't on the release notes for 1.1.4, Zypper will reinstall: zypper in -f qt5-qtconnectivity-qtbluetooth That's probably a bit dangerous without knowing why your version is wrong though. Do you have any other warehouse apps installed that may have bundled the bluetooth? People were getting similar errors to you last year when the SDK was updated, so if someone bundled an older BT version as a workaround at that time, you could get in this mess. |
I first had to install zypper, but once that was done I did what you suggested. qt5-qtconnectivity-qtbluetooth-5.2.0+git0-1.4.6.armv7h1 was reinstalled. However I keep getting the same error when running pebbled. :( |
Did the libQtBluetooth.so.5.2.2 file get changed? |
327464 bytes, dated Feb 6 15:27. I even tried disabling all openrepos 2015-04-29 17:16 GMT+02:00 Andrew Branson notifications@github.com:
Reinout van Schouwen |
Try: pkcon search file /usr/lib/libQt5Bluetooth.so.5.2.2 to see if there are any other packages holding that file. I get: pkcon search file /usr/lib/libQt5Bluetooth.so.5.2.2 |
Executed that, and I have the exact same output as you do. 2015-04-30 11:56 GMT+02:00 Andrew Branson notifications@github.com:
Reinout van Schouwen |
Maybe you should compare the md5sum of the file? |
The date and size already indicates the file is different, md5sum confirms 2015-04-30 14:46 GMT+02:00 awlx notifications@github.com:
Reinout van Schouwen |
201c1142d8d26fd0945babdadb6cdc5b /usr/lib/libQt5Bluetooth.so.5.2.2 here too, so we've confirmed that his file is the wrong one. His package version is right, so what's going on? |
@abranson The other repos are: openrepos-veskuh, openrepos-netvandal, openrepos-ellefj, openrepos-localhost, openrepos-basil, openrepos-Schturman, and openrepos-HtheB. After disabling them all, deinstalling QtBluetooth and pebble, and then reinstalling, apparently the right version is pulled in because pebbled actually starts up! It still doesn't connect to my Pebble though, it's just "waiting for watch" indefinitely. But this specific issue is solved now. |
Pebble firmware: 2.9.1
Sailfish OS: 1.1.2.16
My Pebble and Jolla phone are properly paired and Bluetooth is enabled on both devices.
However, Pebble Manager is unable to connect to the watch.
When I press 'Active', the screen flashes a few times with a message 'Waiting for watch..' and then immediately returns to the initial screen in 'Dead' state. Pressing 'Connection' has no effect.
What can I do to (help you to) debug this?
The text was updated successfully, but these errors were encountered: