QSO Detail: freezing and crash under Windows 11 #591
Comments
iu0dhv
changed the title
|
Does it crash only for specific QSO or is it for random QSOs from your log? |
foldynl
changed the title
|
Hello the log stalls very very frequently and each time I try to edit a
QSO. So not on specific ones but not even randomly. It does so in all
occurrences I have tried.
Moreover, yesterday I was trying the very convenient command to massive
updates for past QSOs. However, even that function did not work as
expected. Selecting bundles of QSOs, only on very few occasions the updates
went through flawlessly. Most of the times, however, the bar showing the
percentage of completion stopped at a percentage that, depending on the
size of the QSO selection, corresponded always to 1 QSO. So I had to stop,
because I could not go on with the massive updates.
I have also tried to close the only other application that was open, i.e.
JTDX, but nothing changed.
To give you some more context, I have a fairly new and performing laptop
and no issues with any other and much heavier logs (e.g. Log4om).
I hope the issue can be solved as I like the log very much :-)
73
Peter, IU0DHV
PS I also have troubles in connecting the radio (FT DX10) via Cat, but for
the time being this is a less important issue.
Il giorno ven 7 feb 2025 alle ore 11:51 Ladislav ***@***.***>
ha scritto:
… Does it crash only for specific QSO or is it for random QSOs from your log?
—
Reply to this email directly, view it on GitHub
<#591 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPHTUEZVT7P5ELVOZBWUQI32OSF25AVCNFSM6AAAAABWUQJVJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBSGU3TONJSGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
can you send me a debug log? Following instructions below:
|
|
Hello again,
please find attached the debug log zipped, obtained following your
instructions.
Please let me know if the issue can be resolved.
Best
Peter, IU0DHV
Il giorno ven 7 feb 2025 alle ore 13:44 Ladislav ***@***.***>
ha scritto:
… can you send me a debug log? Following instructions below:
1. cmd
2. cd to the directory where QLOG is installed
3. set QT_LOGGING_RULES=qlog.*=true
4. qlog.exe -d
5. double click on some QSO
6. send me a log file
C:/Users/<USER>/AppData/Local/hamradio/QLog/qlog_debug_yyyyMMddhhmmss.log
(it will probably be quite big so zip it).
—
Reply to this email directly, view it on GitHub
<#591 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPHTUE7K7TK5PCIAGWKD5QL2OSTC7AVCNFSM6AAAAABWUQJVJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBSHAYTQMBZGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
@iu0dhv it doesn't look like the attachment made it. You may need to go the github website and attach it there. If you reply to an email it doesn't bring the attachments in. Michael, AA5SH |
|
Maybe it's too big. send me a link to my email where I can download it; google drive or another online service |
|
It is just 180kb Zip file....
Il giorno ven 7 feb 2025 alle ore 22:16 Ladislav ***@***.***>
ha scritto:
… Maybe it's too big. send me a link to my email where I can download it;
google drive or another online service
—
Reply to this email directly, view it on GitHub
<#591 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPHTUE4X5FQA5CKQVQWUNPT2OUPERAVCNFSM6AAAAABWUQJVJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBUGE2DGOJQGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I have now shared the link to the file
Il giorno ven 7 feb 2025 alle ore 22:39 Pierluigi Bologna ***@***.***>
ha scritto:
… It is just 180kb Zip file....
Il giorno ven 7 feb 2025 alle ore 22:16 Ladislav ***@***.***>
ha scritto:
> Maybe it's too big. send me a link to my email where I can download it;
> google drive or another online service
>
> —
> Reply to this email directly, view it on GitHub
> <#591 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BPHTUE4X5FQA5CKQVQWUNPT2OUPERAVCNFSM6AAAAABWUQJVJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBUGE2DGOJQGE>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
|
I have now shared the zip file direcly here on github |
|
That's strange. Unfortunately, I don't see any reason why the dialog would be blocked. The strange thing is that I can see the last event updating the time in the clock widget, which is not related to QSODetail. The application is somehow still alive because I can see CW thread activity, but the main thread is not working. Unfortunately, I am not able to identify the cause, even with such a detailed list. I have a few questions:
|
|
Hello I am sorry that there is not obvious solution to the problem. I am attaching here a short video that shows the kind of problem that I am having. The situation shown in the video occurs any time I try to make any change to a QSO. |
|
Thanks for the video. Unfortunately, I do know how to help you. If you're reporting issues in different places, it could be due to a corrupted database. However, this only happens in exceptional cases - OS Crash, Power failure, Memory issue, Disk issue etc. The only thing you could try is running QLog with the After that, try to insert a QSO and performing the operation that caused QLog to freeze. |
|
Thank you for the feedback. I have tried a test version, created a new
profile and set the information to update data from QRZ. I inserted 3 fake
qsos to test whether the prg freezed when trying to amend and update and
seems not to.
Then, I uninstalled Qlog, and reinstalled, and defined a new profile.
However it recongnised my login information for QRZ and LOTW even if I I
renamed the previous local folder as _old. I don't know why it did so. In
any case the problem is still there.
Don't know what else to do given that I am not an IT expert. It is
obviously something conflicting with the log, but I don't understand why it
does so and why it does not freeze in the test version.
The only difference between the test and the real version is that the real
has information for connecting to LOTW (which however is activated only on
request) and the ongoing connection to the cluster, but even if I stop it
the freeze occurs.
Any ideas? If not I might need to abandon the endeavour with QLOG....
Il giorno sab 8 feb 2025 alle ore 16:38 Ladislav ***@***.***>
ha scritto:
… Thanks for the video. Unfortunately, I do know how to help you. If you're
reporting issues in different places, it could be due to a corrupted
database. However, this only happens in exceptional cases - OS Crash, Power
failure, Memory issue, Disk issue etc.
The only thing you could try is running QLog with the -n test switch.
This is used during development when I need to create another instance of
QLog with a new database. It won't affect your current database but will
create a separate instance of QLog (new database, new configuration). It
means that you'll need to go through profile setup again.
After that, try to insert a QSO and performing the operation that caused
QLog to freeze.
—
Reply to this email directly, view it on GitHub
<#591 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPHTUE6DKW7HWYW2BMSMVG32OYQFTAVCNFSM6AAAAABWUQJVJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBVG44TAOBWGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Could it be that something on my log file (ADI) causes the freeze given that with thre fake QSo everything seems to be ok? |
|
If you uninstall and reinstall QLog, your data will not be deleted. Only the application and libraries are removed, but the QSO database, passwords, and settings remain. If your test instance worked, the issue might be a corrupted database file. Ideally, export all QSOs if possible. If it is not possible, check After that, you will also need to delete the entire registry entry at: Once done, start QLog again, and it will guide you through the initial setup. Finally, import the ADX backup and check if everything works correctly.
I don't know if I don't have this file. |
|
I have tried deleteing evrything. I have imported again a brand new adif with basic fields (not too many). The import went fine. I was going to set the connection to QRZ, then I changed my mind and went back to try to edit a new qso before connecting anything, and gues what? freeze! :-( |
|
|
|
I don't think it's a problem in ADI but we can try. Please send it to my private email - my callsign @ gmail.com |
|
I don't think either is a ADI problem. What I don't understand is why the
problem occurs only with Qlog and not with other logs.
Il dom 9 feb 2025, 08:46 Ladislav ***@***.***> ha scritto:
… I don't think it's a problem in ADI but we can try. Please send it to my
private email - my callsign @ gmail.com
—
Reply to this email directly, view it on GitHub
<#591 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPHTUE55AE5HGIGTALUMM432O4BV5AVCNFSM6AAAAABWUQJVJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBWGEYTCMRWHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
There's nothing unusual about it since QLog is a different application. To be honest, I'm sorry but I'm not able to help you. I don't know where the issue is. It could also be an issue of QT library. The next release will come out with an updated QT library, maybe that will help you. I don't know. |
|
Thank you for the support. I will try with a future version of QLog,
hopefully it will work for me.
73 IU0DHV
Il dom 9 feb 2025, 11:06 Ladislav ***@***.***> ha scritto:
… There's nothing unusual about it since QLog is a different application.
To be honest, I'm sorry but I'm not able to help you. I don't know where
the issue is. It could also be an issue of QT library. The next release
will come out with an updated QT library, maybe that will help you. I don't
know.
—
Reply to this email directly, view it on GitHub
<#591 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPHTUE4VQGIFZTADEQDNXIL2O4SBJAVCNFSM6AAAAABWUQJVJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBWGE2TQMBQHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Version 0.41.1 and earlier, with Windows 11
I have experienced several stalls of the log (with ver. 0.41.1. and also with the previous one) with subsequent crash or need to restart.
I have now identified a specific case when this problem arises. If I double click on a qso in the log, the window with all the details opens, and then the software remains unresponsive, with the need to restart.
It is practically impossible to open a specific QSO in the log to edit something, as the program becomes unusable.
Can someone help to fix this problem?
74, Peter
The text was updated successfully, but these errors were encountered: