Comment 14 for bug 1838919

What can I do to help you diagnose the problem further, Daniel?

I think something changed recently, and that must have been an update. I do not believe I have installed any new packages that might have called for GTK2, so my guess is that it has been there since the clean 18.10 install and not been in conflict with GTK3 until recently.

Searching on the conflict has not revealed anything helpful to me because this kind of error has popped up lots of times as far back as ubuntu 12.04. The packages recommended to be installed to "fix" these old problems all seem to be present on my system already.

Is there an easy way to discover what is calling for GTK2, or is that being done by canberra on behalf of some applications, but not others?

Is there any point in me booting recovery mode to see whether the errors (keyboard mapping too, don't forget) are logged from the simple tty console login?