itctl and itgui both can't connect to socket #51
Labels
No Label
Bug
Cantfix
Duplicate
Enhancement
External
Help Wanted
In Progress
Invalid
Question
Waiting
Waiting For Info
Waiting for Upstream
Wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Elara6331/itd#51
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I am trying to run itd on my laptop and but whenever I try to use any itctl command or use itgui I get the following error
FTL Error while running app error="dial unix /tmp/itd/socket: connect: no such file or directory
When I run
systemctl --user status itd
it seems to be active thoughAm I just missing something here?
There aren't any log messages in your systemd output. That indicates to me that ITD is not connected to your PineTime. When it connects, you should get a notification on your PineTime. If it's not doing that, you can try connecting to it manually from your Bluetooth settings and then restarting ITD.
I am having the same issue, it seems - but my PineTime is indeed connected and paired.
I get the following when I try to run
itctl
:Running Fedora 36, with an ASUS USB-BT500 bluetooth module on a Dell OptiPlex 9020 full tower.
Ah, the device is called Pinetime-JF for you. I believe that's what it used to be called a very long time ago. ITD doesn't support firmware that old, so it won't connect.
I'm not sure if it would work if just the name ITD looks for is modified, that depends on how different the BLE services are
I'm not sure I want to gamble with "I'm not sure" with my sealed PineTime, so I might just have to scrounge up my old Android phone to install Gadgetbridge and get it up past 0.7.1 the way documented by the Pine64 wiki.
Still! Looking forward to giving ITD a shot once it's all updated and hunky dory! Your GUI application looks nice, and I'm always a fan of CLI access to my things. :)
Manually connecting to it worked for me now. Now I feel stupid for not having checked and tried that out beforehand. Thanks a lot for the help.