file system errors : invalid memory address or nil pointer #64
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#64
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 have been trying to update resources but when I do things just hang.
itctl res load infinitime-resources.zip
Uploading bebas.bin 0 / 4420 B | | 0.00% 0s
wondering what was going on I decided to check the file system:
itctl fs ls
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x72ac34]
goroutine 1 [running]:
go.elara.ws/itd/api.(*FSClient).ReadDir(0xc0001633e8, {0x867248, 0xc00010a740}, {0x7dce31, 0x1})
/woodpecker/src/gitea.elara.ws/Elara6331/itd/api/fs.go:45 +0x94
main.fsList(0xc0000ac300)
/woodpecker/src/gitea.elara.ws/Elara6331/itd/cmd/itctl/fs.go:19 +0x171
github.com/urfave/cli/v2.(*Command).Run(0xc0000a6500, 0xc0000ac300, {0xc000096660, 0x1, 0x1})
/go/pkg/mod/github.com/urfave/cli/v2@v2.23.7/command.go:271 +0xa42
github.com/urfave/cli/v2.(*Command).Run(0xc0000a63c0, 0xc0000ac1c0, {0xc0000a2360, 0x2, 0x2})
/go/pkg/mod/github.com/urfave/cli/v2@v2.23.7/command.go:264 +0xc97
github.com/urfave/cli/v2.(*Command).Run(0xc0000ae640, 0xc0000ac100, {0xc000014180, 0x3, 0x3})
/go/pkg/mod/github.com/urfave/cli/v2@v2.23.7/command.go:264 +0xc97
github.com/urfave/cli/v2.(*App).RunContext(0xc00009c000, {0x867248?, 0xc00010a740}, {0xc000014180, 0x3, 0x3})
/go/pkg/mod/github.com/urfave/cli/v2@v2.23.7/app.go:333 +0x665
main.main()
/woodpecker/src/gitea.elara.ws/Elara6331/itd/cmd/itctl/main.go:297 +0x24a5
I am assuming because I can't do file system operations this is causing the issue with loading the resources. I tried rebooting my computer ( Ubuntu 20.04 ) and my pinetime watch and neither of those resolved the issues.
I am running pinetime 1.13.0
and I am trying to upload the resources from here: https://github.com/InfiniTimeOrg/InfiniTime/releases
Hello, thanks for reporting this. I would like some information from you to help me debug this. What version of ITD are you using? If you don't know, you can get it using
itd -version
. Also, if you try to runsystemctl --user status itd
, does that show any errors? If not, try runningitctl fs ls
and check again.itd version is 1.1.0
I don't see any errors
itd.service - InfiniTime Daemon (itd)
Loaded: loaded (/usr/lib/systemd/user/itd.service; enabled; vendor preset:>
Active: active (running) since Tue 2023-06-27 20:33:03 EDT; 20s ago
Main PID: 14099 (itd)
CGroup: /user.slice/user-1001.slice/user@1001.service/itd.service
└─14099 /usr/bin/itd
Jun 27 20:33:03 mcardoza-XPS-9315 systemd[2948]: Started InfiniTime Daemon (itd>
Jun 27 20:33:05 mcardoza-XPS-9315 itd[14099]: 8:33PM INF Connected to InfiniTim>
Jun 27 20:33:06 mcardoza-XPS-9315 itd[14099]: 8:33PM INF Initialized InfiniTime>
Jun 27 20:33:06 mcardoza-XPS-9315 itd[14099]: 8:33PM INF Relaying calls to Infi>
Jun 27 20:33:06 mcardoza-XPS-9315 itd[14099]: 8:33PM INF Relaying notifications>
Jun 27 20:33:08 mcardoza-XPS-9315 itd[14099]: 8:33PM INF Starting control socke
itctl fs ls
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x72ac34]
goroutine 1 [running]:
go.elara.ws/itd/api.(*FSClient).ReadDir(0xc0001993e8, {0x867248, 0xc0000b2740}, {0x7dce31, 0x1})
/woodpecker/src/gitea.elara.ws/Elara6331/itd/api/fs.go:45 +0x94
main.fsList(0xc000118300)
/woodpecker/src/gitea.elara.ws/Elara6331/itd/cmd/itctl/fs.go:19 +0x171
github.com/urfave/cli/v2.(*Command).Run(0xc000112500, 0xc000118300, {0xc000102660, 0x1, 0x1})
/go/pkg/mod/github.com/urfave/cli/v2@v2.23.7/command.go:271 +0xa42
github.com/urfave/cli/v2.(*Command).Run(0xc0001123c0, 0xc0001181c0, {0xc000110360, 0x2, 0x2})
/go/pkg/mod/github.com/urfave/cli/v2@v2.23.7/command.go:264 +0xc97
github.com/urfave/cli/v2.(*Command).Run(0xc00011a640, 0xc000118100, {0xc0000a0150, 0x3, 0x3})
/go/pkg/mod/github.com/urfave/cli/v2@v2.23.7/command.go:264 +0xc97
github.com/urfave/cli/v2.(*App).RunContext(0xc00010a000, {0x867248?, 0xc0000b2740}, {0xc0000a0150, 0x3, 0x3})
/go/pkg/mod/github.com/urfave/cli/v2@v2.23.7/app.go:333 +0x665
main.main()
/woodpecker/src/gitea.elara.ws/Elara6331/itd/cmd/itctl/main.go:297 +0x24a5
If you run
bluetoothctl info
, it should show information about your PineTime. One of the UUIDs that it shows should beadaf0200-4669-6c65-5472-616e73666572
. Do you have that UUID listed?nope here is my UUID list
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)
That would do it. Your watch isn't exposing the BLE characteristics for the filesystem protocol. Can you make sure that the firmware hasn't rolled back to a previous version? 1.13.0 should expose those.
the version is 1.13.0 and I even marked it verified on the watch. It has not backdated from what I can tell. Could it be an infinitime bug?
Tiny change in https://gitea.elara.ws/Elara6331/itd/pulls/69/files fixed issue for me.