Closed howels closed 2 years ago
Cannot reproduce using Ubuntu 20.04 LTS.
Did you select a unified or local config before flashing the local hex?
https://askubuntu.com/questions/1360148/skia-shader-compilation-error
Cannot reproduce using Ubuntu 20.04 LTS.
Did you select a unified or local config before flashing the local hex?
https://askubuntu.com/questions/1360148/skia-shader-compilation-error
Bug only appeared after upgrade to 22.04, likely related to libraries. I can flash using the same binary and config on a different Ubuntu system.
I am selecting a board with a unified config and a local hex for e.g. STM32H743 or STM32F7X2.
Is it possible to obtain more verbose output on the CLI?
The error "Skia shader compilation error" is not relevant. I can run with --disable-gpu
and that solves the skia error but the same behaviour exists - hangs when loading firmware.
Remaining errors seem to talk about a DB... possible an sqlite instance in here somewhere?
[195199:195221:0502/143901.887785:ERROR:login_database.cc(704)] Password store database is too new, kCurrentVersionNumber=29, GetCompatibleVersionNumber=31
[195199:195209:0502/143901.887813:ERROR:login_database.cc(704)] Password store database is too new, kCurrentVersionNumber=29, GetCompatibleVersionNumber=31
[195199:195221:0502/143901.887844:ERROR:password_store_impl.cc(56)] Could not create/open login database.
[195199:195209:0502/143901.887877:ERROR:password_store_impl.cc(56)] Could not create/open login database.
[195230:195238:0502/143927.964078:ERROR:nss_util.cc(286)] After loading Root Certs, loaded==false: NSS error code: -8018
[195230:195238:0502/143927.964432:ERROR:cert_verify_proc_builtin.cc(559)] No net_fetcher for performing AIA chasing.
[195199:195285:0502/143931.886593:ERROR:database.cc(1709)] History sqlite error 1, errno 0: no such column: publicly_routable, sql: SELECT id,url,visit_time,from_visit,transition,segment_id,visit_duration,incremented_omnibox_typed_score,publicly_routable FROM visits WHERE visit_time >= ? AND visit_time < ?ORDER BY visit_time LIMIT ?
[195199:195285:0502/144001.900475:ERROR:database.cc(1709)] History sqlite error 1, errno 0: no such column: publicly_routable, sql: SELECT id,url,visit_time,from_visit,transition,segment_id,visit_duration,incremented_omnibox_typed_score,publicly_routable FROM visits WHERE visit_time >= ? AND visit_time < ? AND (transition & ?) == ?ORDER BY visit_time LIMIT ?
Cleared ~/.config/betaflight-configurator and ~/.cache/betaflight-configurator. Messages are gone (bad DB replaced) but error persists.
Did you follow the steps here: https://github.com/betaflight/betaflight/blob/master/docs/development/Building%20in%20Ubuntu.md#flashing-a-target-with-betaflight-configurator-on-ubuntu-2004
Yes, of course I followed the steps and set the permissions, I have done this before. This is some new strangeness that isn't present on my other laptop, and wasn't present prior to upgrade. My /etc/udev/rules.d is the same on this broken system as on my working system. I can also work in configurator fine up until I load local firmware. I can configure the board and save configuration with no issues.
I cannot even hit the flash button to trigger DFU. If I enter to DFU prior to loading the flash screen I see the same lockup - as soon as I load local firmware.
I have added logging in the hope that it explains the problem.
FWIW this is a fresh 22.04 install with only 2 udev rules set for STM32 and stLinkv2 devices:
$ cat /etc/udev/rules.d/45-stdfu-permissions.rules
# DFU (Internal bootloader for STM32 MCUs) Stephen
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="df11", MODE="0664", GROUP="plugdev"
# non-DFU mode
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="5740", MODE="0664", GROUP="plugdev"
$ cat /etc/udev/rules.d/49-stlinkv2.rules
# stm32 discovery boards, with onboard st/linkv2
# ie, STM32L, STM32F4.
# STM32VL has st/linkv1, which is quite different
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3748", \
GROUP:="dialout", \
SYMLINK+="stlinkv2_%n"
I kept my profile but the rest of the install is fresh with no old libraries at all. By contrast the working system is an older one that has been upgraded and kept all the old cruft - and is still working. So something happened in 22.04 I think.
Will check later on another machine with Ubuntu 22.04 LTS.
Ubuntu 22.04 LTS requires NW.js 0.60 to solve the flashing issue locking up configurator.
EDIT found a fix for https://github.com/betaflight/betaflight-configurator/pull/2856 but Node 16 is scheduled for 10.9 😞
Only can test on Windows and Linux. But sure there are problems with latest OSX versions reported.
Another pitfall on Ubuntu 22.04 LTS is it's using clang
v14 as firmware is not compatible yet (need v7 - v13) used for make test
@howels please check this build: https://github.com/betaflight/betaflight-configurator/pull/2913#issuecomment-1115557255
@howels please check this build: #2913 (comment)
Confirm that https://github.com/betaflight/betaflight-configurator/pull/2913 fixes the issue. Flashing works normally now. Thanks!
Tested this issue with latest nightly under MacOS (Mojave) without any problems. Did this with several differnent FC and for every FC several times.
Works as designed
Describe the bug
UI stops responding after loading local firmware on RC6.
On console these errors are seen:
To Reproduce
Load local firmware with board connected, UI stops responding.
Expected behavior
Firmware file is loaded and can click "Flash Firmware" button.
Configurator version
be4a9e1 (4.3.0 RC6)
Flight controller configuration
Add any other context about the problem that you think might be relevant here
OS is Ubuntu Linux 22.04