Created attachment 1271 [details]
GTK-QT with QTCurve using Ozone pre-defined style on Ubuntu 13.04 with May 11, 2013 R14 nightlies

GTK-QT with QTCurve using Ozone pre-defined style on Ubuntu 13.04 with May 11, 2013 R14 nightlies

LibreOffice can't start when GTK-QT theme engine is used with QTCurve. Also, other GTK apps are shown without theme (example: the background is black everywhere with text in white)

This is on GTK-QT with QTCurve using Ozone pre-defined style on Ubuntu 13.04 with May 11, 2013 R14 nightlies

With the classic theme (Plastik), it works, but not in all GTK apps. 2 non-working apps are: the default Ubuntu PDF reader (evince?) and when I right click on the Ubuntu network manager on the taskbar.
These programs also doesn't work with QTCurve.

-Alexandre

On PCLinuxOS 2012 with TDE 3.5.13.1 and LibreOffice 3.6 as well as on PCLinuxOS 2013 with TDE 3.5.13.2 and LibreOffice 4, just having  gtk-qt installed is enough to destroy part of the formatting of documents in LibreOffice. It doesn't even have to be activated to affect the layout of documents.

To try to reproduce the bug:
Make a new document with cropped and resized pictures. You can also put some line or shapes with the drawing toolbar of LibreOffice. Then, save, close LO and try to open back your document. The formatting will be different and cropped images will not be cropped at the right place. Shapes are also in a different place.

Thanks!
-Alexandre

Is there a way to reliably recreate this crash, e.g. with Chromium?  I am seeing these crashes pop up sporadically from Firefox on the crash report server, but the gtk-qt-engine is never involved in the backtrace, making debugging pretty much impossible.

Also, if you are on Debian or Ubuntu, please install the gtk-qt-engine-trinity-dbg package and submit crash reports so that we can get some useful information.

Thanks!

I don't think we'll ever be able to fix this with only the data from Firefox crashes:
https://developer.mozilla.org/en-US/docs/Mozilla/Testing/Valgrind

Basically their implementation does a bunch of rather nasty things that could (and apparently do!) interfere with gdb after Firefox crashes for any reason.

Please stop submitting reports from crashed Firefox instances; however if anything *else* crashes please send a report!

As an aside, this bug will likely close with time on its own when Firefox finally migrates to GTK3--the TDE integration engine for GTK3 is a complete rewrite that does not need many of the hacks from the old GTK2 engine due to GTK3's greater flexibility.

When I tested this with Chromium, the crashes were happening very often. That's why I could easily get a backtrace. If you manage to use Chromium with Trinity for about 20-30 minutes visiting different websites without getting any crash, I would say this problem is fixed.

I believe I've isolated the crash on Firefox to a non-TDE root cause:
https://support.mozilla.org/en-US/questions/1003111

Note that the user in that report describes the exact same behaviour as I was seeing with Firefox and TDE (though he is on Windows!), and the fix mentioned in that report works for me as well.  I suspect TDE makes this bug trigger more easily somehow (changed memory layout?) but that the root cause is Firefox and its apparently buggy Baseline JIT implementation.

I have not had Chromium crash since the patches went in against gtk-qt-engine, so I suspect this bug is as resolved as it's going to be.  I'll leave it open for a while just in case I am wrong. :-)

(In reply to Alex Couture from comment #3)
> On PCLinuxOS 2012 with TDE 3.5.13.1 and LibreOffice 3.6 as well as on
> PCLinuxOS 2013 with TDE 3.5.13.2 and LibreOffice 4, just having  gtk-qt
> installed is enough to destroy part of the formatting of documents in
> LibreOffice. It doesn't even have to be activated to affect the layout of
> documents.
> 
> To try to reproduce the bug:
> Make a new document with cropped and resized pictures. You can also put some
> line or shapes with the drawing toolbar of LibreOffice. Then, save, close LO
> and try to open back your document. The formatting will be different and
> cropped images will not be cropped at the right place. Shapes are also in a
> different place.
> 
> Thanks!
> -Alexandre

Can you check to see if the fix for Libreoffice in Bug 1489 resolved this issue?

Thanks!

After much debugging work I finally traced the Firefox (and most likely Chromium) crashes to their root cause.

In a nutshell Firefox's Baseline JIT *purposefully* generates SIGSEGVs as part of its normal operation:
http://www.jandemooij.nl/blog/2014/02/18/using-segfaults-to-interrupt-jit-code/

TDE's DrKonqui signal handler was simply getting in the way of Firefox's built-in SIGSEGV traps; when DrKonqui saw the (normal) SIGSEGV it forced Firefox to improperly abort.

Fixed in GIT hash 82ccf29 (gtk-qt-engine).

Thanks for reporting!

Updating to iceweasel 31.2.0esr-3~deb7u1 in Debian Wheezy, I find that Iceweasel always crash in few seconds with the following error in terminal:
:~$ iceweasel
[kcrash] KCrash: Application 'gtk-qt-application' crashing...
Segment violation

If I remove the package
gtk-qt-engine-trinity
Iceweasel works ok.

(In reply to Alexis PM from comment #10)
> Updating to iceweasel 31.2.0esr-3~deb7u1 in Debian Wheezy, I find that
> Iceweasel always crash in few seconds with the following error in terminal:
> :~$ iceweasel
> [kcrash] KCrash: Application 'gtk-qt-application' crashing...
> Segment violation
> 
> If I remove the package
> gtk-qt-engine-trinity
> Iceweasel works ok.

Are you using the TDE R14 release candidate builds?