Crashes on M1 Mac at the end of firmware flashing #100
Labels
bug
Something isn't working
Comments
|
Thank you for providing all of the crash logs. There is a pattern in them worth investigating. There is a chance that it is somehow connected to Rosetta though, an can truly be fixed only by migrating qFlipper to Qt6 series (which is planned, but cannot be done very easily and will impact users with older hardware/OSes). The good thing is now that the firmware is updated, it supports the newer update method, which is much more stable, so this should not happen anymore. |
|
Same thing is happening on mine. Tried moving to my older i7 Macbook, still crashing. After trying lots of combinations, turns out installling the Development firmware fixes the issue, so this may be firmware-related. |
|
The same crash happened to me. I tried more than five times but had no luck. Changing the update channel to dev ( Crash Report |
|
I was able to use qFlipper version 1.0.2 to do the initial update flash of my Flipper, after that I was able to use the latest version of qFlipper without issues to upload newer firmware or alternate firmwares on my flipper. Might be an option to downgrade qFlipper first (ignore the "this is not the latest version" warning). |
|
Thank you @bertjwregeer !!! Using 1.0.2 (download link) I was also able to get mine flashed and then just tested again in latest qFlipper that I could install the RC ok for 0.64.0. Hopefully others with the same issue see this. |
|
Working on this issue, will release separate mac M1 version of qFlipper. |
|
I just got my Flipper today and the same issue happend to me too, but I'm using a Intel Mac?! (Macmini8,1) |
|
Since the majority of the crashes seem to happen inside libusb, and also some evidence that downgrading the application version is helping, there is a chance that it was at least partially caused by upgrading to libusb 1.0.26 on the build server which happened mid June. Just to be safe, I have rolled it back to 1.0.24 and the upcoming qFlipper version will be bundled with it instead. Hope this helps. Everything said earlier still stands: Qt6 and the native M1 version are a priority, which indirectly will help fixing problems like this one. |
|
Not sure if this is just a quirk of my update failure case though (stuck at "Updating resources" even after reboot) but I tried repairing with 1.3.2 and also got this crash, however when i tried 1.0.2: edit: well, after that failed, going back to 1.3.2 seems to complete firmware repair without crashing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I got my Flipper delivered a few hours back today. Happily, I turned it on, connected to my MBP (M1 Max, running macOS 12.5), downloaded and launched qFlipper (1.1.1), and clicked “update” (to release 0.63.3), and… got a crash on 100%. I tried to repair it, again and again, three times in a row, with the same outcome. On the fifth time, it made it somehow, when it wasn’t an active window (maybe it’s relevant, maybe not). Also, I didn’t try rebooting or reconnecting my Flipper because it was in recovery mode anyway.
More structured issue answers, closer to the template
Steps to reproduce the behavior
Expected behavior
A finished firmware update process, a running application, and a happy dolphin.
Actual behavior
A crashed application and a Flipper device in recovery mode.
Additional troubleshooting
Here’s the latest crash report. I got all four reports if it’ll help. Let me know if you need those as well.
Crash Report 2022-08-04-185623 (Translated)
And here’re the full logs (four of crashes and one of success). They are a bit different; it might be worth including them all.
qFlipper-20220804-184407 (Crash)
qFlipper-20220804-184528 (Crash)
qFlipper-20220804-184646 (Crash)
qFlipper-20220804-185341 (Crash)
qFlipper-20220804-185824 (Success)
The text was updated successfully, but these errors were encountered: