Well:
- the fact that it happens in oxygen-gtk does not mean it is an oxygen-gtk bug:
just means the code path followed by oxygen-gtk triggers a bug that can be
anywhere in the chain
- nowhere in the core dump, as far as I can tell, is oxygen-gtk mentionned.
(sorry in advance if I missed it).
(n
I am closing this bug report
Last few posted crashes are unrelated to oxygen-gtk: they are libgobject.
I guess it is just someone pushing the "submit report" button.
So that it brings no new information
(besides java coredumps also have very little information to start with)
finally,
- none of the
