BitBoxSwiss
BitBox2 not detected by app
Just tried to connect my BitBox2 after half a year. Updated the app and connected my device, but it doesn't get recognized.
BitBox2 says "See the BitBoxApp" but the app says "Please connect your device to get started".
I've enabled usb permissions as described in https://shiftcrypto.ch/download/ I read this article and verified that my device is connected. I can't seem to find any error in the logs, so I just give you everything which might be important. I also tried different usb ports. Everything works fine under Windows.
uname -a
Linux manjaro 5.13.1-3-MANJARO #1 SMP PREEMPT Sat Jul 10 20:15:35 UTC 2021 x86_64 GNU/Linux
dmesg when connecting the bitbox
[ 261.791416] usb 3-3: new full-speed USB device number 4 using xhci_hcd
[ 261.956566] usb 3-3: New USB device found, idVendor=03eb, idProduct=2403, bcdDevice= 1.00
[ 261.956570] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 261.956571] usb 3-3: Product: BitBox02
[ 261.956573] usb 3-3: Manufacturer: shiftcrypto.ch
[ 261.956573] usb 3-3: SerialNumber: v9.5.0
[ 261.968683] hid-generic 0003:03EB:2403.0009: hiddev99,hidraw6: USB HID v1.11 Device [shiftcrypto.ch BitBox02] on usb-0000:08:00.3-3/input0
[ 261.976680] hid-generic 0003:03EB:2403.000A: hiddev100,hidraw7: USB HID v1.11 Device [shiftcrypto.ch BitBox02] on usb-0000:08:00.3-3/input1
lsusb | grep "BitBox"
Bus 003 Device 005: ID 03eb:2403 Atmel Corp. BitBox02
bitbox log file
time="2021-07-22T22:08:04+02:00" level=info msg="Started Qt application" args="[./BitBox-4.28.2-x86_64.AppImage]" group=server
time="2021-07-22T22:08:04+02:00" level=info msg="--------------- Started application --------------" group=server
time="2021-07-22T22:08:04+02:00" level=info msg=environment goarch=amd64 goos=linux group=server version=4.28.2
time="2021-07-22T22:08:04+02:00" level=info msg="Arguments: &{mainDirectoryPath:/home/max/.config/bitbox bitbox02DirectoryPath:/home/max/.config/bitbox/bitbox02 bitboxBaseDirectoryPath:/home/max/.config/bitbox/bitboxBase cacheDirectoryPath:/home/max/.config/bitbox/cache notesDirectoryPath:/home/max/.config/bitbox/notes appConfigFilename:/home/max/.config/bitbox/config.json accountsConfigFilename:/home/max/.config/bitbox/accounts.json testing:false regtest:false devmode:false devservers:false gapLimits:<nil> log:0xc00024ab40}" group=arguments
time="2021-07-22T22:08:04+02:00" level=info msg="backend config: {Proxy:{UseProxy:false ProxyAddress:} DeprecatedBitcoinActive:true DeprecatedLitecoinActive:true DeprecatedEthereumActive:true BTC:{ElectrumServers:[0xc000111b00 0xc000111b30]} TBTC:{ElectrumServers:[0xc000111b60 0xc000111b90]} RBTC:{ElectrumServers:[0xc000111bc0]} LTC:{ElectrumServers:[0xc000111bf0 0xc000111c20]} TLTC:{ElectrumServers:[0xc000111c50 0xc000111c80]} ETH:{DeprecatedActiveERC20Tokens:[]} TETH:{DeprecatedActiveERC20Tokens:[]} RETH:{DeprecatedActiveERC20Tokens:[]} FiatList:[USD EUR CHF] MainFiat:CHF UserLanguage:}" group=backend
time="2021-07-22T22:08:04+02:00" level=info msg="frontend config: <nil>" group=backend
time="2021-07-22T22:08:04+02:00" level=info msg="ReconfigureHistory: coins=[]; fiats=[\"USD\" \"EUR\" \"CHF\"]" group=rates
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/rates
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/native-locale
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/native-locale
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/bitboxbases/detected
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/accounts
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/bitboxbases/registered
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/devices/registered
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/version
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/using-mobile-data
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/banners/bitbox01
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/update
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/keystores
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2021-07-22T22:08:04+02:00" level=debug msg=endpoint group=handlers method=POST path=/api/config
time="2021-07-22T22:08:07+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2021-07-22T22:08:07+02:00" level=debug msg=endpoint group=handlers method=POST path=/api/config
Hey there. It looks like everything's there but maybe the app cannot access (open) the device due to /dev/path permissions?
Could you plug in the bitbox, tap a side and execute this:
ls -l /dev/ | grep bitbox
It should show something like this:
lrwxrwxrwx 1 root root 7 Jul 23 09:51 bitbox02_1 -> hidraw1
lrwxrwxrwx 1 root root 15 Jul 23 09:51 bitbox02_2 -> bus/usb/001/017
That would be a good sign. It means udev rules are working. You can then check permissions on the dev files those symlinks point to. For me it looks like this:
$ ls -l /dev/hidraw1
crw-rw-r-- 1 root users 244, 1 Jul 23 09:51 /dev/hidraw1
$ ls -l /dev/bus/usb/001/017
crw-rw-r-- 1 root users 189, 16 Jul 23 09:51 /dev/bus/usb/001/017
If you get to this point, might as check if those dev files are writable, so to make sure permissions are ok:
$ sh -c "test -d /dev/hidraw1 && echo writable"
writable
$ sh -c "test -w /dev/bus/usb/001/017 && echo writable"
writable
If you don't see "writable" in the output, permissions are incorrect. You could then add , MODE="0666" to the udev rules to confirm this is a permissions issue:
# /etc/udev/rules.d/53-hid-bitbox02.rules
SUBSYSTEM=="usb", TAG+="uaccess", TAG+="udev-acl", SYMLINK+="bitbox02_%n", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2403", MODE="0666"
# /etc/udev/rules.d/54-hid-bitbox02.rules
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2403", TAG+="uaccess", TAG+="udev-acl", SYMLINK+="bitbox02_%n", MODE="0666"
Once you modified the rules, replug the bitbox and tap a side again.
Please let me know if this works. We'll then update the udev rules on the website.
Thanks for the answer. I checked the permissions and they look good to me but I can't get the "writeable" output. I then added the MODE="0666" to both rules, but it's still not writeable even after a PC reboot. (Also, I'm getting 3 devices.)
Here is what I did:
$ ls -l /dev/ | grep bitbox
lrwxrwxrwx 1 root root 7 24. Jul 00:12 bitbox02_1 -> hidraw1
lrwxrwxrwx 1 root root 7 24. Jul 00:12 bitbox02_2 -> hidraw2
lrwxrwxrwx 1 root root 15 24. Jul 00:12 bitbox02_3 -> bus/usb/003/002
$ ls -l /dev/hidraw1
crw-rw-rw-+ 1 root root 239, 1 24. Jul 00:12 /dev/hidraw1
$ ls -l /dev/hidraw2
crw-rw-rw-+ 1 root root 239, 2 24. Jul 00:12 /dev/hidraw2
$ ls -l /dev/bus/usb/003/002
crw-rw-rw-+ 1 root root 189, 257 24. Jul 00:12 /dev/bus/usb/003/002
$ sh -c "test -d /dev/hidraw1 && echo writable"
$ sh -c "test -d /dev/hidraw2 && echo writable"
$ sh -c "test -d /dev/bus/usb/003/002 && echo writable"
$ cat /etc/udev/rules.d/53-hid-bitbox02.rules
SUBSYSTEM=="usb", TAG+="uaccess", TAG+="udev-acl", SYMLINK+="bitbox02_%n", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2403", MODE="0666"
$ cat /etc/udev/rules.d/54-hid-bitbox02.rules
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2403", TAG+="uaccess", TAG+="udev-acl", SYMLINK+="bitbox02_%n", MODE="0666"
OMG so sorry, I suggested incorrect command with test -d. That would never work. I should've typed test -w. But I see the permissions show crw-rw-rw- so everything looks read/writable.
I have another idea. Let me double-check...
I noticed there's an ACL entry associated with the files, indicated by the plus sign at the end: crw-rw-rw-+. This might affect the actual permissions. To verify, could you run this on all three, /dev/hidraw1, /dev/hidraw2 and /dev/bus/... Note that /dev/bus/... path will most likely change after replugging the device:
getfacl /dev/...
Good news is, your system does seem to trigger udev rules when the bitbox is connected.
OMG so sorry, I suggested incorrect command with
test -d. That would never work. I should've typedtest -w. But I see the permissions showcrw-rw-rw-so everything looks read/writable.
Yes, with -w all devs show writeable now :)
Here is getfacl on all devices:
$ getfacl /dev/hidraw6
getfacl: Removing leading '/' from absolute path names
# file: dev/hidraw6
# owner: root
# group: root
user::rw-
user:max:rw-
group::rw-
mask::rw-
other::rw-
$ getfacl /dev/hidraw7
getfacl: Removing leading '/' from absolute path names
# file: dev/hidraw7
# owner: root
# group: root
user::rw-
user:max:rw-
group::rw-
mask::rw-
other::rw-
$ getfacl /dev/bus/usb/003/003
getfacl: Removing leading '/' from absolute path names
# file: dev/bus/usb/003/003
# owner: root
# group: root
user::rw-
user:max:rw-
group::rw-
mask::rw-
other::rw-
This is very strange. The app should definitely detect the bitbox. I would come back to the app's log file and check for any errors.
The log you posted in the beginning seems unusually short. Could you grab the whole thing and email it to support@shiftcrypto-dot-ch. If it's larger than 10Mb, please email only the last 10Mb. I'll let my colleagues know and they'll route the ticket to me.
The reason to continue on support@ is the log may contain some data I wouldn't want you to expose here in the public.
I just found out that there is indeed an error being logged. Either I didn't notice it the other day, or it's new now. Anyway, I sent the log to the email. It's very short, as I cleared it a few times to see when the error occurred.
Here's what I did in the log:
- Started the app
- Connected the Bitbox
- Touched a side
When touching a side, the error shows up. The app seems to want to send a request, but fails to do so.
Hi all,
Not sure it is the same problem on my end, but I am not able to use bitbox02 with the latest BitBox Linux App (bitbox_4.29.0_amd64.deb) on Ubuntu 20.04.2 LTS (kernel 5.11.0-27-generic) running on x86_64 desktop PC. I followed all Linux installation steps, including the python libraries and udev rules.
Curiously, I only experience this issue with the newer kernel v5.11, but not with the older kernel v4.14.
FWIW, I am getting the following warnings and errors on 5.11 kernel during bitbox02 connect/disconnect:
[11268.143051] hid-generic 0003:03EB:2403.0006: hiddev2,hidraw4: USB HID v1.11 Device [shiftcrypto.ch BitBox02] on usb-0000:07:00.3-4/input0
[11268.151024] hid-generic 0003:03EB:2403.0007: hiddev3,hidraw5: USB HID v1.11 Device [shiftcrypto.ch BitBox02] on usb-0000:07:00.3-4/input1
[11268.233478] xhci_hcd 0000:07:00.3: WARN urb submitted to disabled ep
[11268.233485] usb 3-4: usbfs: usb_submit_urb returned -2
[11268.234664] xhci_hcd 0000:07:00.3: WARN urb submitted to disabled ep
[11268.234669] usb 3-4: usbfs: usb_submit_urb returned -2
[11283.159802] usb 3-4: USB disconnect, device number 4
[11283.160106] xhci_hcd 0000:07:00.3: xHCI xhci_drop_endpoint called with disabled ep 000000003789b64d
[11283.160110] xhci_hcd 0000:07:00.3: xHCI xhci_drop_endpoint called with disabled ep 000000004d76f1e2
[11283.160112] xhci_hcd 0000:07:00.3: xHCI xhci_drop_endpoint called with disabled ep 0000000022cd6e5a
[11283.160114] xhci_hcd 0000:07:00.3: xHCI xhci_drop_endpoint called with disabled ep 00000000b0c80618
If anybody sees similar messages via dmesg, could there be a chance we are experiencing the same issue?
Hey, where exactly do you get stuck? Can you tap a side on the device and then the app doesn't recognize the device? I also tried booting with an older kernel (4.19.204), but it doesn't seem to make any difference. Also I'm not getting dmesg errors. Have you tried it on windows? @chatraed
Hi @seriousm4x
where exactly do you get stuck?
I basically go through the same sequence as described by you in https://github.com/digitalbitbox/bitbox-wallet-app/issues/1401#issuecomment-886168601 , i.e.
- Started the app on Ubuntu. The App GUI displays "Please connect your device to get started"
- Connected the Bitbox02 wallet to PC via USB-C port.
- No change in the GUI on Linux App.
- Touched a side on the wallet.
- Wallet now displays "See the BitBoxApp".
- Linux App GUI now displays "Enter BitBox02 password to unlock" and runs the howto animation
- [issue] => The wallet keeps displaying "See the BitBoxApp" instead of giving the possibility to enter the password
I also tried booting with an older kernel (4.19.204),
IMHO it's worth the effort to try 4.14.
Have you tried it on windows?
It's working fine for me on Windows 10.
I just figured out that my Bitbox02 HW wallet works without problems on Ubuntu 20.04 when connected to a normal USB3.0-typeA port on my x86 motherboard (through USB-typeA-USB-typeC adapter). Previously I was connecting the HW wallet to a native USB-typeC port on the motherboard.
All my findings shared previously still apply, but they are just limited to the native USB-C port on my desktop PC. In other words, the Bitbox02 wallet would communicate flawlessly with v4.14 (and presumably older) kernels via USB-C port, but would fail to communicate using newer Linux kernels on the same USB-C port. This means that there is either a culprit commit, a potential CONFIG change or kernel command line parameter update in the newer kernel (particularly v5.11 used by Ubuntu 20.04) which affected the Linux compatibility for the BitBox02 device. Some git bisecting would be appropriate in this case, but it hasn't been done.
@chatraed thanks so much for the info very useful. I'm on a voidlinux and its stock kernel 5.12.19_1 without issues. It's definitely possible Ubuntu is setting some CONFIG flags in their 20.04 release, although it seems @seriousm4x might have a different issue.
My next step would be to upgrade our libusb/libhid libraries. We're currently using https://github.com/karalabe/usb which contains an older copy of the upstream usb: https://github.com/karalabe/usb/issues/10. I'll temporary fork karalabe/usb to get the exact diff and see whether there are any potential changes relavant to this issue.
So, I've tried again today and it magically worked. Same hardware but updated arch. Steps are the same as on the website.
Run as root:
addgroup plugdev
usermod -aG plugdev max
printf "SUBSYSTEM==\"usb\", SYMLINK+=\"bitbox02_%%n\", GROUP=\"plugdev\", MODE=\"0664\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2403\"\n" | sudo tee /etc/udev/rules.d/53-hid-bitbox02.rules > /dev/null && printf "KERNEL==\"hidraw*\", SUBSYSTEM==\"hidraw\", SYMLINK+=\"bitbox02_%%n\", GROUP=\"plugdev\", MODE=\"0664\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2403\"\n" | sudo tee /etc/udev/rules.d/54-hid-bitbox02.rules > /dev/null
printf "SUBSYSTEM==\"usb\", SYMLINK+=\"dbb%%n\", GROUP=\"plugdev\", MODE=\"0664\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2402\"\n" | sudo tee /etc/udev/rules.d/51-hid-digitalbitbox.rules > /dev/null && printf "KERNEL==\"hidraw*\", SUBSYSTEM==\"hidraw\", SYMLINK+=\"dbbf%%n\", GROUP=\"plugdev\", MODE=\"0664\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2402\"\n" | sudo tee /etc/udev/rules.d/52-hid-digitalbitbox.rules > /dev/null
Reboot and all was working. I can't tell at all what caused the issue back then but it's working now. Thanks for the help though
Hello again :)
So i resurfaced this issue but now running on endeavourOS (basically arch) on same hardware. Exact same behavior as previously. Did all the setup setups like so:
- create plugdev group and add my user to it
- create udev rules for plugdev group
- reboot
- download app, chmod +x and run it
App wants me to enter the password while bitbox device tells me to "See the BitBoxApp".
Here is some updated terminal output from the above requests:
~ ❯❯❯ ls -l /dev/ | grep bitbox ✘ 130
lrwxrwxrwx 1 root root 8 22. Mai 19:27 bitbox02_10 -> hidraw10
lrwxrwxrwx 1 root root 15 22. Mai 19:27 bitbox02_2 -> bus/usb/003/015
~ ❯❯❯ ls -l /dev/hidraw10
crw-rw-r--+ 1 root plugdev 245, 10 22. Mai 19:27 /dev/hidraw10
~ ❯❯❯ ls -l /dev/bus/usb/003/015
crw-rw-r-- 1 root plugdev 189, 270 22. Mai 19:29 /dev/bus/usb/003/015
~ ❯❯❯ test -w /dev/hidraw10 && echo writable
writable
~ ❯❯❯ test -w /dev/bus/usb/003/015 && echo writable
writable
~ ❯❯❯ cat /etc/udev/rules.d/5*
SUBSYSTEM=="usb", SYMLINK+="dbb%n", GROUP="plugdev", MODE="0664", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2402"
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", SYMLINK+="dbbf%n", GROUP="plugdev", MODE="0664", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2402"
SUBSYSTEM=="usb", SYMLINK+="bitbox02_%n", GROUP="plugdev", MODE="0664", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2403"
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", SYMLINK+="bitbox02_%n", GROUP="plugdev", MODE="0664", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2403"
~ ❯❯❯ groups
sys libvirt docker rfkill wheel autologin max plugdev
~ ❯❯❯ getfacl /dev/hidraw10
getfacl: Removing leading '/' from absolute path names
# file: dev/hidraw10
# owner: root
# group: plugdev
user::rw-
user:max:rw-
group::rw-
mask::rw-
other::r--
~ ❯❯❯ getfacl /dev/bus/usb/003/015
getfacl: Removing leading '/' from absolute path names
# file: dev/bus/usb/003/015
# owner: root
# group: plugdev
user::rw-
group::rw-
other::r--
~ ❯❯❯ uname -a
Linux arch 6.9.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 17 May 2024 16:56:38 +0000 x86_64 GNU/Linux
Also, here is the bitbox log. I've replaced my device id:
~ ❯❯❯ cat .config/bitbox/log.txt
time="2024-05-22T19:35:20+02:00" level=info msg="BITBOXAPP_RENDER=software" group=qt-frontend
time="2024-05-22T19:35:21+02:00" level=info msg="Started Qt application" args="[./BitBox-4.42.0-x86_64.AppImage]" group=server
time="2024-05-22T19:35:21+02:00" level=info msg="--------------- Started application --------------" group=server
time="2024-05-22T19:35:21+02:00" level=info msg=environment goarch=amd64 goos=linux group=server version=4.42.0
time="2024-05-22T19:35:21+02:00" level=info msg="Arguments: &{mainDirectoryPath:/home/max/.config/bitbox bitbox02DirectoryPath:/home/max/.config/bitbox/bitbox02 cacheDirectoryPath:/home/max/.config/bitbox/cache notesDirectoryPath:/home/max/.config/bitbox/notes appConfigFilename:/home/max/.config/bitbox/config.json accountsConfigFilename:/home/max/.config/bitbox/accounts.json testing:false regtest:false devservers:false gapLimits:<nil> log:0xc00030b0a0}" group=arguments
time="2024-05-22T19:35:21+02:00" level=info msg="backend config: {Proxy:{UseProxy:false ProxyAddress:} DeprecatedBitcoinActive:true DeprecatedLitecoinActive:true DeprecatedEthereumActive:true Authentication:false BTC:{ElectrumServers:[btc1.shiftcrypto.io:443:s btc2.shiftcrypto.io:443:s]} TBTC:{ElectrumServers:[tbtc1.shiftcrypto.io:443:s tbtc2.shiftcrypto.io:443:s]} RBTC:{ElectrumServers:[127.0.0.1:52001:p 127.0.0.1:52002:p]} LTC:{ElectrumServers:[ltc1.shiftcrypto.io:443:s ltc2.shiftcrypto.io:443:s]} TLTC:{ElectrumServers:[tltc1.shiftcrypto.io:443:s tltc2.shiftcrypto.io:443:s]} ETH:{DeprecatedActiveERC20Tokens:[]} TETH:{} RETH:{} FiatList:[USD EUR CHF] MainFiat:USD UserLanguage: BtcUnit:default}" group=backend
time="2024-05-22T19:35:21+02:00" level=info msg="frontend config: map[]" group=backend
time="2024-05-22T19:35:21+02:00" level=info msg="ReconfigureHistory: coins=[]; fiats=[\"USD\" \"EUR\" \"CHF\"]" group=rates
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/native-locale
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/native-locale
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/aopp
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=POST path=/api/config
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=POST path=/api/authenticate
time="2024-05-22T19:35:21+02:00" level=info msg="Auth requested" group=backend
time="2024-05-22T19:35:21+02:00" level=info msg="Auth result: true" group=backend
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/keystores
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/update
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/banners/bitbox01
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/banners/bitbox02
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/using-mobile-data
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=POST path=/api/set-dark-theme
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/accounts
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/devices/registered
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/detect-dark-theme
time="2024-05-22T19:35:21+02:00" level=info msg="kde theme: \n" group=server
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/version
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/version
time="2024-05-22T19:35:21+02:00" level=info msg="Gnome/Ubuntu theme: 'default'\n" group=server
time="2024-05-22T19:35:21+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2024-05-22T19:35:34+02:00" level=info msg="Registering BitBox02" device-id=XXXXXXXXXX group=manager identifier=XXXXXXXXXX product=BitBox02 productID=9219 serial=v9.14.0 usagePage=0 vendorID=1003
time="2024-05-22T19:35:34+02:00" level=info msg="Plugged in device" deviceID=XXXXXXXXXX group=device product=bitbox02-multi productName=bitbox02
time="2024-05-22T19:35:34+02:00" level=debug msg=Init device=bitbox02 group=handlers
time="2024-05-22T19:35:34+02:00" level=info msg="fire event: statusChanged" deviceID=XXXXXXXXXX group=device product=bitbox02-multi productName=bitbox02
time="2024-05-22T19:35:34+02:00" level=info msg="fire event: statusChanged" deviceID=XXXXXXXXXX group=device product=bitbox02-multi productName=bitbox02
time="2024-05-22T19:35:34+02:00" level=debug msg="Device status: connected" deviceID=XXXXXXXXXX group=device product=bitbox02-multi productName=bitbox02
time="2024-05-22T19:35:34+02:00" level=error msg="attestation: could not perform request. challenge=a191896cf6a4032b8163ef865be41b9658a75469c3250d02af409bb1d6b6e1eb" deviceID=XXXXXXXXXX error="hidapi: hid_error is not implemented yet > github.com/digitalbitbox/bitbox02-api-go/communication/u2fhid.(*Communication).sendFrame.func1 > /opt/go/src/github.com/digitalbitbox/bitbox-wallet-app/vendor/github.com/digitalbitbox/bitbox02-api-go/communication/u2fhid/u2fhid.go:107 > github.com/digitalbitbox/bitbox02-api-go/communication/u2fhid.(*Communication).sendFrame > /opt/go/src/github.com/digitalbitbox/bitbox-wallet-app/vendor/github.com/digitalbitbox/bitbox02-api-go/communication/u2fhid/u2fhid.go:121 > github.com/digitalbitbox/bitbox02-api-go/communication/u2fhid.(*Communication).Query > /opt/go/src/github.com/digitalbitbox/bitbox-wallet-app/vendor/github.com/digitalbitbox/bitbox02-api-go/communication/u2fhid/u2fhid.go:185 > github.com/digitalbitbox/bitbox02-api-go/api/firmware.(*Device).rawQueryV7 > /opt/go/src/github.com/digitalbitbox/bitbox-wallet-app/vendor/github.com/digitalbitbox/bitbox02-api-go/api/firmware/query.go:63 > github.com/digitalbitbox/bitbox02-api-go/api/firmware.(*Device).rawQuery > /opt/go/src/github.com/digitalbitbox/bitbox-wallet-app/vendor/github.com/digitalbitbox/bitbox02-api-go/api/firmware/query.go:120 > github.com/digitalbitbox/bitbox02-api-go/api/firmware.(*Device).performAttestation > /opt/go/src/github.com/digitalbitbox/bitbox-wallet-app/vendor/github.com/digitalbitbox/bitbox02-api-go/api/firmware/attestation.go:84 > github.com/digitalbitbox/bitbox02-api-go/api/firmware.(*Device).Init > /opt/go/src/github.com/digitalbitbox/bitbox-wallet-app/vendor/github.com/digitalbitbox/bitbox02-api-go/api/firmware/device.go:254 > github.com/digitalbitbox/bitbox-wallet-app/backend/devices/bitbox02.(*Device).init.func1 > /opt/go/src/github.com/digitalbitbox/bitbox-wallet-app/backend/devices/bitbox02/device.go:96 > runtime.goexit > /opt/go_dist/go/src/runtime/asm_amd64.s:1650 > Failed to send message" group=device product=bitbox02-multi productName=bitbox02
time="2024-05-22T19:35:34+02:00" level=error msg="unknown IO error (most likely the device was unplugged)Failed to send message: hidapi: hid_error is not implemented yet" deviceID=XXXXXXXXXX group=device product=bitbox02-multi productName=bitbox02
time="2024-05-22T19:35:34+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/devices/registered
time="2024-05-22T19:35:34+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/banners/bitbox02
time="2024-05-22T19:35:34+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/config
time="2024-05-22T19:35:34+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/devices/bitbox02/XXXXXXXXXX/version
time="2024-05-22T19:35:34+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/devices/bitbox02/XXXXXXXXXX/attestation
time="2024-05-22T19:35:34+02:00" level=debug msg=Attestation device=bitbox02 group=handlers
time="2024-05-22T19:35:34+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/version
time="2024-05-22T19:35:34+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/devices/bitbox02/XXXXXXXXXX/status
time="2024-05-22T19:35:34+02:00" level=debug msg="Device status: connected" deviceID=XXXXXXXXXX group=device product=bitbox02-multi productName=bitbox02
time="2024-05-22T19:35:34+02:00" level=debug msg=endpoint group=handlers method=GET path=/api/version
There are two errors in the lower half of the log complaining about an hidapi error. Not really sure what to do with this.
Any help appreciated!
