On Fri, 25 Feb 2022 16:19:44 -0800
William Morder via tde-users <users(a)trinitydesktop.org> wrote:
Sorry, but I have never had a problem quite like this.
I don't even know where
to begin. I've been running TDE since about 2010, off and on, and KDE3 before
that from about 2006. This is a first for me.
As it happens, I have been experimenting with just that approach. Here is what
I get from trying to start Firefox from a konsole window.
$ firefox
(firefox-esr:19742): Gtk-ERROR **: 16:12:42.109: GTK+ 2.x symbols detected.
Using GTK+ 2.x and GTK+ 3 in the same process is not supported
ExceptionHandler::GenerateDump cloned child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
19749
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
Trace/breakpoint trap
Vivaldi gives even less information:
$ vivaldi-snapshot
(vivaldi-snapshot:20029): Gtk-ERROR **: 16:14:29.797: GTK+ 2.x symbols
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
Trace/breakpoint trap
$ midori
(midori:20520): Gtk-ERROR **: 16:17:48.267: GTK+ 2.x symbols detected. Using
GTK+ 2.x and GTK+ 3 in the same process is not supported
Trace/breakpoint trap
I could go on, but it seems to be this problem with gtk2 and gtk3.
Things which may or may not be of use to you in sorting this out:
I remember similar error messages showing up in the past when one of the
impose-TDE-visual-settings-on-GTK optional bits malfunctioned, so uninstall
those if you have them. (I thought that bug had been fixed, though.)
Pale Moon probably works because it's still GTK2-primary, so no GTK3.
links apparently doesn't use a toolkit and calls X stuff directly.
Vivaldi has a direct runtime dependency on the at-spi-bus crud.
E. Liddell