Elara6331
/
itd
4
6
Fork 11
Code Issues 8 Pull Requests 1 Projects Releases 11 Wiki Activity

/tmp/itd/socket not found #65

New Issue
Open
opened 2023-06-30 18:12:21 +00:00 by blargson · 8 comments
blargson commented 2023-06-30 18:12:21 +00:00
Copy Link

I installed by downloading latest deb for itd-1.1.0-linux-x86_64.

In itgui:
dial unix /tmp/itd/socket: connect: no such file or directory

Running itctl get:
11:08AM FTL Error while running app error="dial unix /tmp/itd/socket: connect: no such file or directory"

Output of systemctl status --user itd:

● itd.service - InfiniTime Daemon (itd)
     Loaded: loaded (/usr/lib/systemd/user/itd.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2023-06-30 11:01:07 PDT; 7min ago
   Main PID: 493515 (itd)
      Tasks: 5 (limit: 4449)
     Memory: 6.0M
        CPU: 69ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/itd.service
             └─493515 itd

Jun 30 11:01:07 zeroth systemd[675]: Started InfiniTime Daemon (itd).

uname -a:
Linux blarg 5.10.0-23-amd64 #1 SMP Debian 5.10.179-1 (2023-05-12) x86_64 GNU/Linux

I installed by downloading latest deb for itd-1.1.0-linux-x86_64. In itgui: `dial unix /tmp/itd/socket: connect: no such file or directory` Running `itctl get`: `11:08AM FTL Error while running app error="dial unix /tmp/itd/socket: connect: no such file or directory" ` Output of `systemctl status --user itd`: ``` ● itd.service - InfiniTime Daemon (itd) Loaded: loaded (/usr/lib/systemd/user/itd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2023-06-30 11:01:07 PDT; 7min ago Main PID: 493515 (itd) Tasks: 5 (limit: 4449) Memory: 6.0M CPU: 69ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/itd.service └─493515 itd Jun 30 11:01:07 zeroth systemd[675]: Started InfiniTime Daemon (itd). ``` uname -a: `Linux blarg 5.10.0-23-amd64 #1 SMP Debian 5.10.179-1 (2023-05-12) x86_64 GNU/Linux `
Ghost commented 2023-07-27 11:52:30 +00:00
Copy Link

Hi,

Same issue here. I tried using rpm and the makefile, same problem.

uname -a:

Linux rd-66-176 6.4.4-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jul 19 16:32:49 UTC 2023 x86_64 GNU/Linux

/etc/os-release:

NAME="Fedora Linux"
VERSION="38 (Workstation Edition)"
ID=fedora
VERSION_ID=38
VERSION_CODENAME=""
PLATFORM_ID="platform:f38"
PRETTY_NAME="Fedora Linux 38 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:38"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f38/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=38
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=38
SUPPORT_END=2024-05-14
VARIANT="Workstation Edition"
VARIANT_ID=workstation

EDIT: after reading #51, I forgot to mention that I am able to connect to the watch manually with bluetooth. Device "InifiniTime" appears with bluetoothctl devices Connected, but socket issue is still present.

Hi, Same issue here. I tried using rpm and the makefile, same problem. `uname -a`: ``` Linux rd-66-176 6.4.4-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jul 19 16:32:49 UTC 2023 x86_64 GNU/Linux ``` `/etc/os-release`: ``` NAME="Fedora Linux" VERSION="38 (Workstation Edition)" ID=fedora VERSION_ID=38 VERSION_CODENAME="" PLATFORM_ID="platform:f38" PRETTY_NAME="Fedora Linux 38 (Workstation Edition)" ANSI_COLOR="0;38;2;60;110;180" LOGO=fedora-logo-icon CPE_NAME="cpe:/o:fedoraproject:fedora:38" DEFAULT_HOSTNAME="fedora" HOME_URL="https://fedoraproject.org/" DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f38/system-administrators-guide/" SUPPORT_URL="https://ask.fedoraproject.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Fedora" REDHAT_BUGZILLA_PRODUCT_VERSION=38 REDHAT_SUPPORT_PRODUCT="Fedora" REDHAT_SUPPORT_PRODUCT_VERSION=38 SUPPORT_END=2024-05-14 VARIANT="Workstation Edition" VARIANT_ID=workstation ``` EDIT: after reading [#51](https://gitea.elara.ws/Elara6331/itd/issues/51), I forgot to mention that I am able to connect to the watch manually with bluetooth. Device "InifiniTime" appears with `bluetoothctl devices Connected`, but socket issue is still present.
Elara6331 commented 2023-08-05 19:53:49 +00:00
Owner
Copy Link

The watch must be connected and paired before ITD will start its socket. ITD should show you a dialog where you can enter a pairing code. If it doesn't, try pairing (not just connecting) manually and then start ITD.

The watch must be connected and paired before ITD will start its socket. ITD should show you a dialog where you can enter a pairing code. If it doesn't, try pairing (not just connecting) manually and then start ITD.
Ghost commented 2023-08-06 13:17:23 +00:00
Copy Link

Hi,

Thanks for your comment.

However, I tried what you said, and it does not work. I can even get informations from bluetoothctl, that seems to be correct:

[InfiniTime]# info
Device D7:B4:7B:0E:42:C5 (random)
	Name: InfiniTime
	Alias: InfiniTime
	Appearance: 0x00c2 (194)
	Paired: yes
	Bonded: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	LegacyPairing: no
	UUID: Vendor specific           (00000000-78fc-48fe-8e23-433b3a1942d0)
	UUID: Vendor specific           (00001530-1212-efde-1523-785feabcd123)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Immediate Alert           (00001802-0000-1000-8000-00805f9b34fb)
	UUID: Current Time Service      (00001805-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	UUID: Heart Rate                (0000180d-0000-1000-8000-00805f9b34fb)
	UUID: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
	UUID: Alert Notification Serv.. (00001811-0000-1000-8000-00805f9b34fb)
	UUID: adafruit industries       (0000febb-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (00010000-78fc-48fe-8e23-433b3a1942d0)
	UUID: Vendor specific           (00030000-78fc-48fe-8e23-433b3a1942d0)
	UUID: Vendor specific           (00040000-78fc-48fe-8e23-433b3a1942d0)
	Battery Percentage: 0x50 (80)

It worked the first time I tried it, with the previous version of itd; but now that my laptop is known by the watch, I can remove the device and add it back on my laptop, connect to it, pair and trust it, but I do not have any new BT code from the watch...

How could I remove the laptop from the known devices on the watch to get a new code ?

Hi, Thanks for your comment. However, I tried what you said, and it does not work. I can even get informations from bluetoothctl, that seems to be correct: ``` [InfiniTime]# info Device D7:B4:7B:0E:42:C5 (random) Name: InfiniTime Alias: InfiniTime Appearance: 0x00c2 (194) Paired: yes Bonded: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Vendor specific (00000000-78fc-48fe-8e23-433b3a1942d0) UUID: Vendor specific (00001530-1212-efde-1523-785feabcd123) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Immediate Alert (00001802-0000-1000-8000-00805f9b34fb) UUID: Current Time Service (00001805-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) UUID: Heart Rate (0000180d-0000-1000-8000-00805f9b34fb) UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb) UUID: Alert Notification Serv.. (00001811-0000-1000-8000-00805f9b34fb) UUID: adafruit industries (0000febb-0000-1000-8000-00805f9b34fb) UUID: Vendor specific (00010000-78fc-48fe-8e23-433b3a1942d0) UUID: Vendor specific (00030000-78fc-48fe-8e23-433b3a1942d0) UUID: Vendor specific (00040000-78fc-48fe-8e23-433b3a1942d0) Battery Percentage: 0x50 (80) ``` It worked the first time I tried it, with the previous version of itd; but now that my laptop is known by the watch, I can remove the device and add it back on my laptop, connect to it, pair and trust it, but I do not have any new BT code from the watch... How could I remove the laptop from the known devices on the watch to get a new code ?
erinarbleiz commented 2023-10-19 15:41:30 +00:00
Copy Link

I confirm I have the problem too.

bluetoothctl info:

[InfiniTime]# info
Device D1:D1:6A:75:D5:C0 (random)
	Name: InfiniTime
	Alias: InfiniTime
	Appearance: 0x00c2 (194)
	Paired: yes
	Bonded: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	LegacyPairing: no
	UUID: Vendor specific           (00000000-78fc-48fe-8e23-433b3a1942d0)
	UUID: Vendor specific           (00001530-1212-efde-1523-785feabcd123)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Immediate Alert           (00001802-0000-1000-8000-00805f9b34fb)
	UUID: Current Time Service      (00001805-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	UUID: Heart Rate                (0000180d-0000-1000-8000-00805f9b34fb)
	UUID: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
	UUID: Alert Notification Serv.. (00001811-0000-1000-8000-00805f9b34fb)
	UUID: adafruit industries       (0000febb-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (00010000-78fc-48fe-8e23-433b3a1942d0)
	UUID: Vendor specific           (00030000-78fc-48fe-8e23-433b3a1942d0)
	UUID: Vendor specific           (00040000-78fc-48fe-8e23-433b3a1942d0)
	Battery Percentage: 0x47 (71)
[InfiniTime]#

dmesg:

oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: chip_type status=0 type=5
oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8703
oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8723cs_xx_fw.bin
oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8723cs_xx_config.bin
oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: cfg_sz 63, total sz 19427
oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: fw version 0xaa5ca4dc

inxi -Eaz:

[alarm@danctnix ~]$ inxi -Eaz
Bluetooth:
  Device-1: dw-apb-uart driver: dw_apb_uart bus-ID: N/A chip-ID: snps:1c28400 class-ID: serial
  Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 4.1 lmp-v: 7 status:
    discoverable: no pairing: no class-ID: 7c0110
  Device-2: dw-apb-uart driver: N/A bus-ID: N/A chip-ID: snps:serial0 class-ID: serial

no dialog appear on connection. pinetime show a connected status and siglo manage to sync time and date. I tried from a clean install without siglo (in case both apps were in conflict) but nothing new, ITD seems to keep failing to create the socket.

I installed the ITD from AUR (itd-bin)

edit: after a few debug in the code, it seems that itd block on the infinitime.Init(k.String("bluetooth.adapter")), line 64 of the file main.go. I managed to found out by adding fmt.Println() before and after the call, and the second never print so the defer Infinitime.exit() never reach meaning startSocket that create the socket that is after that defer is never reached too.

edit 2: I found that the Init fail at the daMgmt.SetPowered(true)

edit 3: commenting the 2 lines:

        daMgmt := btmgmt.NewBtMgmt(adapterID)
        daMgmt.SetPowered(true)

and the import line for that lib fix the problem and I have a itd successfully connected on the pinetime

I confirm I have the problem too. bluetoothctl info: ``` [InfiniTime]# info Device D1:D1:6A:75:D5:C0 (random) Name: InfiniTime Alias: InfiniTime Appearance: 0x00c2 (194) Paired: yes Bonded: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Vendor specific (00000000-78fc-48fe-8e23-433b3a1942d0) UUID: Vendor specific (00001530-1212-efde-1523-785feabcd123) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Immediate Alert (00001802-0000-1000-8000-00805f9b34fb) UUID: Current Time Service (00001805-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) UUID: Heart Rate (0000180d-0000-1000-8000-00805f9b34fb) UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb) UUID: Alert Notification Serv.. (00001811-0000-1000-8000-00805f9b34fb) UUID: adafruit industries (0000febb-0000-1000-8000-00805f9b34fb) UUID: Vendor specific (00010000-78fc-48fe-8e23-433b3a1942d0) UUID: Vendor specific (00030000-78fc-48fe-8e23-433b3a1942d0) UUID: Vendor specific (00040000-78fc-48fe-8e23-433b3a1942d0) Battery Percentage: 0x47 (71) [InfiniTime]# ``` dmesg: ``` oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: chip_type status=0 type=5 oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8703 oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8723cs_xx_fw.bin oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8723cs_xx_config.bin oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: cfg_sz 63, total sz 19427 oct. 19 15:47:37 danctnix kernel: Bluetooth: hci0: RTL: fw version 0xaa5ca4dc ``` inxi -Eaz: ``` [alarm@danctnix ~]$ inxi -Eaz Bluetooth: Device-1: dw-apb-uart driver: dw_apb_uart bus-ID: N/A chip-ID: snps:1c28400 class-ID: serial Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 4.1 lmp-v: 7 status: discoverable: no pairing: no class-ID: 7c0110 Device-2: dw-apb-uart driver: N/A bus-ID: N/A chip-ID: snps:serial0 class-ID: serial ``` no dialog appear on connection. pinetime show a connected status and siglo manage to sync time and date. I tried from a clean install without siglo (in case both apps were in conflict) but nothing new, ITD seems to keep failing to create the socket. I installed the ITD from AUR (itd-bin) **edit: after a few debug in the code, it seems that itd block on the infinitime.Init(k.String("bluetooth.adapter")), line 64 of the file main.go. I managed to found out by adding fmt.Println() before and after the call, and the second never print so the defer Infinitime.exit() never reach meaning startSocket that create the socket that is after that defer is never reached too.** **edit 2: I found that the Init fail at the daMgmt.SetPowered(true)** edit 3: commenting the 2 lines: ``` daMgmt := btmgmt.NewBtMgmt(adapterID) daMgmt.SetPowered(true) ``` and the import line for that lib fix the problem and I have a itd successfully connected on the pinetime
prurigro commented 2024-03-29 19:55:22 +00:00
Copy Link

@erinarbleiz Thank you! I was actually starting to think that the watch was broken :)

Just to clarify the solution- here's how you can build the working package (the gist link below is a patch with @erinarbleiz's changes, and most of the build itself was ported from the archlinux PKGBUILD):

mkdir build
cd build
wget https://gist.githubusercontent.com/prurigro/934bd7a3aaa0dbf016829c295c32f251/raw/8fb1396658e288f52ad618bac34513446c21746e/itd-fix-connect.patch
export GOPATH="$PWD"
git clone https://gitea.elara.ws/Elara6331/itd
cd itd
printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)" > version.txt
go get -modcacherw -d
cd ../pkg
chmod a+rw -R ./*
patch -p1 < ../itd-fix-connect.patch
cd ../itd
go build -modcacherw
go build -modcacherw ./cmd/itctl
go build -modcacherw ./cmd/itgui
@erinarbleiz Thank you! I was actually starting to think that the watch was broken :) Just to clarify the solution- here's how you can build the working package (the gist link below is a patch with @erinarbleiz's changes, and most of the build itself was ported from the archlinux PKGBUILD): ``` mkdir build cd build wget https://gist.githubusercontent.com/prurigro/934bd7a3aaa0dbf016829c295c32f251/raw/8fb1396658e288f52ad618bac34513446c21746e/itd-fix-connect.patch export GOPATH="$PWD" git clone https://gitea.elara.ws/Elara6331/itd cd itd printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)" > version.txt go get -modcacherw -d cd ../pkg chmod a+rw -R ./* patch -p1 < ../itd-fix-connect.patch cd ../itd go build -modcacherw go build -modcacherw ./cmd/itctl go build -modcacherw ./cmd/itgui ```
fez1 commented 2024-04-02 02:54:45 +00:00
Copy Link

I'm having this issue too, even after pairing - not just connecting - the pinetime, using itd 1.1.0.

I'm having this issue too, even after pairing - not just connecting - the pinetime, using itd 1.1.0.
fez1 commented 2024-04-02 06:33:07 +00:00
Copy Link

More details: I was having this issue when using the packages from the latest release - I was able to pair with the Pinetime using an x86_64 laptop running Fedora (rpm package) and an aarch64 Pinetime running Mobian (deb package) and saw the missing socket issue both times.

After some hiccups in the build process as I tried following the suggested commands from @prurigro, I decided I'd try building the latest commit to master without this patch first and see if it worked. I cross compiled for aarch64 on an x86_64 machine, put itd on an SD card, and put it in the Pinetime. With itd running in one terminal window, I was able to connect to the Pinetime and update the resources to the latest version in another window. The connection was a little flaky, so I made sure to keep both devices' screens awake by touching them every few seconds throughout the upload process, but it worked.

More details: I was having this issue when using the packages from the latest release - I was able to pair with the Pinetime using an x86_64 laptop running Fedora (rpm package) and an aarch64 Pinetime running Mobian (deb package) and saw the missing socket issue both times. After some hiccups in the build process as I tried following the suggested commands from @prurigro, I decided I'd try building the latest commit to master without this patch first and see if it worked. I cross compiled for aarch64 on an x86_64 machine, put itd on an SD card, and put it in the Pinetime. With `itd` running in one terminal window, I was able to connect to the Pinetime and update the resources to the latest version in another window. The connection was a little flaky, so I made sure to keep both devices' screens awake by touching them every few seconds throughout the upload process, but it worked.
prurigro commented 2024-04-02 18:31:54 +00:00
Copy Link

@fez1 it looks like the patch I created is no longer necessary as @Elara6331 has updated it to fix the issue: 8961780053

@fez1 it looks like the patch I created is no longer necessary as @Elara6331 has updated it to fix the issue: https://gitea.elara.ws/Elara6331/infinitime/commit/89617800536fd30cffe9e4e7abd097cbc952a98e
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
v1.1.0
v1.0.0
v0.0.9
v0.0.8
v0.0.7
v0.0.6
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels   
Bug

Something is not working

  
Cantfix

This issue cannot be fixed in ITD

  
Duplicate

This issue or pull request already exists

  
Enhancement

New feature

  
External

This issue is not in ITD

  
Help Wanted

Need some help

  
In Progress

This issue is currently being worked on

  
Invalid

Something is wrong

  
Question

More information is needed

  
Waiting

Waiting for something external to be completed to allow completion of issue

  
Waiting For Info

Waiting for additional information about issue

  
Waiting for Upstream

Waiting for an upstream project to fix an issue

  
Wontfix

This won't be fixed

No Label
Bug
Cantfix
Duplicate
Enhancement
External
Help Wanted
In Progress
Invalid
Question
Waiting
Waiting For Info
Waiting for Upstream
Wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
6 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Elara6331/itd#65
No description provided.
Delete Branch "%!s(<nil>)"

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?