Suddenly broken after settings change #769
Comments
|
does it return segmentation fault? are you able to run it with gdb? the settings seem fine to me |
|
Yes, says segmentation fault. It runs without the -qml option, but not with. Gdb doesn't seem to do anything and won't run with - qml :-( The settings aren't persistent somehow are they? I deleted the whole directory before rebuilding, so it can't have been that? |
|
the settings are persistent. They are in a qt folder under your home. gdb --args ./qdomyos-zwift -qmlthen when it finish to load everything, type run it should start and it should give some information about the segmentation fault |
|
Here is the GDB output. It loaded QZ as a black screen and I Force Quit it once it had loaded. ubuntu@ubuntu:~/qdomyos-zwift/src$ sudo gdb --args ./qdomyos-zwift -qml For help, type "help". Thread 1 "qdomyos-zwift" received signal SIGSEGV, Segmentation fault. |
|
very strange..let's do in this way |
|
I don't have that in $Home/.config ! |
|
Maybe there is a qt subfolder before the qz one |
|
The plot thickens - my micro sd card is bent and the whole thing won't boot now. I don't know if that happened before or after, anyway I will reinstall. If I can replicate the bug then we can continue, if not, it may have been some corruption on my sd card. |
|
@jonathancolledge so sorry to hear this :( let me know how it will go |
|
So I flashed a new SD with a backup image with a QZ version from early April. I changed the settings and rebooted and it worked. I then rebuilt QZ with the newest version and it was broken, just like above. Next job is to reflash and see which setting it was that breaks the newest version. I think either start paused or heart rate pairing. |
|
or you can dont' change any settings and use the new version. if it doesn't work means that there is a regression. I'm on vacation so I don't have any raspberry with me to test it. If you want, we can have a teamviewer session in the next day |
|
Ah of course, I didn't think about no change. I'll update, but ignore and enjoy your vacation! |
|
@jonathancolledge QZ is part of my vacation ;) |
|
Got it! It is the Speed calculates on power setting. When I toggle it to on, it breaks QZ. I need to double check that it doesn't break with the old one. I have a lot of t trouble flashing the disc image as my computer doesn't seem to like it, but it does eventually work. Hopefully I'll know tomorrow. |
|
Oh no, it isn't speed calculates on power. I think it is heart rate sensor related. No changes and it isn't broken. All other changes don't break it. Changing the heart rate sensor does break both new and old version. |
|
Sorry Roberto, it isn't consistent. I have no idea what it is. Working right now... |
|
And now I've just updated to the new version and it's broken. It's there any way I can change the settings so I don't have to reflash the disk image? Then I can compare the changes quickly. |
there is for sure a qt folder on your home but you have to find it, usually it's the path that i mentioned some post ago |
|
Thanks. I have a qt folder, but nothing QZ related that I can find. What I
might do is copy the whole thing and restore that when needed then. Next
try now!
…On Fri, 15 Apr 2022, 08:52 Roberto Viola, ***@***.***> wrote:
And now I've just updated to the new version and it's broken. It's there
any way I can change the settings so I don't have to reflash the disk
image? Then I can compare the changes quickly.
there is for sure a qt folder on your home but you have to find it,
usually it's the path that i mentioned some post ago
—
Reply to this email directly, view it on GitHub
<#769 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBEFAFGGZCWJUPDPWAD6BTVFEN5RANCNFSM5TJO6VUQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
So strange, do you also check in the qz folder? You can easily find sorting them by date |
|
I'm getting more sure it is related to changing the heart rate from disabled to a heart rate sensor. I can send a copy of settings that work and then the only change is that. I replaced the whole QT folder in home and the ./config folder and that didn't reset the settings. I delete the whole QZ folder each time I rebuild too. |
|
unfortunately until i will be home i can't do a double check maybe you try to use the "bt" command after the segmentation fault on gdb. it should show the last function executed |
|
Ok I've done lots of tests. Here is all I have:
gdb log as above. gdb bt gives this: |
|
thanks @jonathancolledge the only commit that could be involved is this one f626227 but i don't see an actual correlation between the segfault and itself. Unfortunately bt doesn't provide any useful information, seems something hidden (maybe a corruption!?) |
|
Nearly there on the git bisect... Hopefully I'll have a little time to finish in the morning. |
|
wow thanks! sorry to bother you so much :( |
|
it's so strange, it doesn't affect at all to that setting. Since yesterday i changed the logic about the cc693cc did you also try the last master commit? Is it broken too? If so I guess there is a memory corruption, it's the only explanation |
|
maybe I got it @jonathancolledge are you still using the branch raspberry? the one that I created for you? If so I will add some debug output to confirm my idea. |
|
Yeah I can use that, pull and build again? I'll try tomorrow, or I'll try and start a video of the fan! |
|
let me do the modification first :P |
|
done @jonathancolledge |
|
Working debug file. No problems here. Heart rate monitor off before I started QZ. |
|
NOT working debug. Only difference is that I turned the heart rate monitor on before starting QZ. But after this I can't get it to work even with heart rate monitor off. I'll keep trying... |
|
after the non working debug you got a segmentation fault isn't it @jonathancolledge ? |
|
Yes, also see the update above. But to update the update, I then plugged the Fitfan in before starting Qz and it broke again. Now segmentation fault every time even with all devices unplugged. |
|
ok got it. i will fix on the afternoon. thanks |
|
done @jonathancolledge pull it and build it. finger crossed! |
|
Almost! Heart rate didn't connect |
|
@jonathancolledge but it doesn't crash anymore, isn't it? |
|
That's right! Doesn't crash! |
|
@jonathancolledge this is the issue did you try just one time or is it deterministic? |
I tried 3 times yesterday, but I think I just needed to turn it all off then on because today, it is perfect! All connecting. Heart rate working, tiles showing, and Fitfan working! Thank you! |
|
great! let's see if it is steady! |
|
debug-Tue_May_17_04_41_50_2022.log Today it took a lot of tries to connect to heart rate, but it did in the end. What it never connected to was the Fitfan. I was displaying the intended fan speed though. |
|
@jonathancolledge for the FAN: I didn't see the advertising frame from the fan here. Are you sure it's not connected to your phone? for the HR: it seems a DBUS issue. Did you try to reboot the raspberry? |
|
Maybe it was the reboot. Connections all fine this morning. Though I sent you other news on messenger. |
|
yeah bluetooth is very weak on linux. so i suggest always to start with a fresh boot |
|
@jonathancolledge check the last point of this also https://github.com/cagnulein/qdomyos-zwift/wiki/FAQ |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
@jonathancolledge what about this issue? can we close this? |
|
Yes indeed! |
|
argh unbelievable! so sorry to hear this :(
Il giorno mer 13 apr 2022 alle ore 19:47 jonathancolledge <
***@***.***> ha scritto:
… The plot thickens - my micro sd card is bent and the whole thing won't
boot now. I don't know if that happened before or after, anyway I will
reinstall. If I can replicate the bug then we can continue, if not, it may
have been some corruption on my sd card.
—
Reply to this email directly, view it on GitHub
<#769 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWHK2M5DSKZVB2GPGITVE4CDTANCNFSM5TJO6VUQ>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
I thought all I changed was pause on start, but my finger must have changed another setting too.
Anyway, QZ won't load - help please! I have attached a log. I removed it all and rebuilt, but still no luck.
debug-Tue_Apr_12_06_03_14_2022.log
The text was updated successfully, but these errors were encountered: