collin80
Crash when try to save logfile
When clicking the Save logfile menu on Xubuntu the application crashes.
Tried a number of pixbuf problem solutions found on Google, but none helped.
Hmmm, hadn't run into that before. The crash dump makes it appear as if it is a problem getting the GTK resources it is looking for. I know QT tries to do some magic to make file system dialogs like load/save look proper across the various operating systems. I think I may be able to change the behavior a bit to make it draw it's own file dialog instead of trying to make it look native. I'll see if there's any setting I can provide that would help with this.
Collin,
So you know...
Savvy CAN 208 Nov 30 2022 runs fine on the same Xubuntu version.
Ben
Collin Kidder schreef op 2023-09-08 03:43:
Hmmm, hadn't run into that before. The crash dump makes it appear as if it is a problem getting the GTK resources it is looking for. I know QT tries to do some magic to make file system dialogs like load/save look proper across the various operating systems. I think I may be able to change the behavior a bit to make it draw it's own file dialog instead of trying to make it look native. I'll see if there's any setting I can provide that would help with this.
-- Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. You are receiving this because you authored the thread.Message ID: @.***>
Links:
[1] https://github.com/collin80/SavvyCAN/issues/661#issuecomment-1710962415 [2] https://github.com/notifications/unsubscribe-auth/AAMUMMFFG43JLMWY4Z6RD73XZJZ5FANCNFSM6AAAAAA4ITW3P4
I assume you are using the precompiled versions of each? My best guess is that something changed with the QT version as otherwise not a lot changed that would/should cause this sort of problem. But, the QT version used to compile SavvyCAN is likely to have changed between versions. It tends to keep up fairly closely with the latest released QT5 version. I did find the way to make QT use it's own widgets instead of trying to make native looking file dialogs. I'll see about making this an option and we can see if that solves it or not.