Comment 14 for bug 1962807

> So I should download the corresponding files from launchpad to a new directory and then issue the sudo dpkg -i *.deb command from there to replace the updated files on my system, correct?

Yes

> Should there be anything else I ought to do before issuing the sudo dpkg command? Should I take any action to ensure I don't accidentally "update" these files and get back into the same situation?

there are way to 'pin' updates with apt or synaptic but at this point we are trying to confirm if that update is the issue, if it is and that you want to pin back to the old version we can help you with that

> How helpful to you would it be for me to install the .ddeb file and which of the traces would you want me to run again? Would I do the install via sudo dpkg -i or use synaptic or apt in some manner?

it would provide more details on the segfault and make it easier to understand, but let's start by going back to the previous gtk3 version and see if that helps.

There has been no other report of such issue and trying in a fresh VM from focal gtk3 softwares work fine with the updated gtk, including gimp, pidgin and others. Unsure if Mint is adding some sort of custom hacks on top of what is in Ubuntu which would have an impact or if that could be something local.

One other thing you could try is to create a new local user, log with it and see if the issue is still there, it would tell us if it's due to some user profile configuration or something wrong in the system