kwrite-4.7.0 crashes in "Configure editor" with qt 4.8
Steps to Reproduce:
Open Settings->Configure editor
kate-4.7.0 also crashes with similar backtrace in Editor ooptions
not entirely sure if this is qt48 specific or not yet, adding kde-4.7 tracker too.
#7 0x078556a8 in QFontEngineFT::loadFlags(QFontEngineFT::QGlyphSet*,
QFontEngine::GlyphFormat, int, bool&, int&) const () from
#8 0x07855a4c in QFontEngineFT::getPointInOutline(unsigned int, int, unsigned
int, int*, int*, unsigned int*) () from /usr/lib/libQtGui.so.4
#9 0x07771bd6 in ?? () from /usr/lib/libQtGui.so.4
#10 0x00e04de5 in ?? () from /usr/lib/libQtCore.so.4
may be related to recent qt/fontconfig patches. odd to see the ??'s in there.
fwiw, I cannot reproduce this using kde-4.7.1 + qt-4.8.0 myself.
This not happens now for me too on F16 Beta RC1 LiveCD with KDE 4.7.0 and qt 4.8.
Not reproducible anymore.
*** Bug 739855 has been marked as a duplicate of this bug. ***
KDE upstream says this is QTBUG-17238.
For some reason, it doesn't seem to be 100% reproducible, but it's not entirely random either.
I am have the same crashes in kate and kwrite always. And I can provide additional info.
Created attachment 524035 [details]
Created attachment 524036 [details]
Taking this off the kde4.7 tracker (keeping it only on qt4.8) because this is clearly a Qt bug.
Discussed at 2011-09-30 blocker review (we forgot to update the bug last week). Accepted as a blocker per criterion "All applications listed under the Applications menu or category must withstand a basic functionality test and not crash after a few minutes of normal use. They must also have working Help and Help -> About menu items".
I'm putting this accepted blocker onto F16Blocker-kde, now that qt-4.8 no longer blocks F16Blocker-kde.
Does this still happen with qt-4.8.0-0.12.20111002.fc16? Unfortunately, I see no movement upstream on QTBUG-17238. There's a hint at a possible change which might fix it, I can try to produce a patch.
Looks like problem solved in new QT qt-4.8.0-0.15.rc1.fc16.
Careful there, this is not 100% reproducible. So can anybody else reproduce this with Qt 4.8.0 RC1? If not, we can close it.
Upstream claims this is fixed (QTBUG-17238 is closed, it was actually closed on July 19, just without a comment, so I didn't notice it), and we can no longer reproduce it, so I think we can close this.
Removing external tracker bug with the id '17238' as it is not valid for this tracker