On Fri, Jul 2, 2010 at 5:45 PM, Honza Barto? <thingwath at gmail.com> wrote: > Hi, > I have some problems running palapeli from kde-unstable repository. > When I try to open any puzzle (either by creating a new one, or > selecting some existing one), it simply segfaults. I'm not sure where > I should report bugs in kde-unstable. It does that in a very ugly way > -- producing stack trace with about 68 thousand frames. I don't have > full -debuginfo for every package, so the stack trace isn't complete, > there are some ??'s. The last frame is > > #0 ?0xb718b710 in QCommonStyle::sizeFromContents(QStyle::ContentsType, > QStyleOption const*, QSize const&, QWidget const*) const () from > /usr/lib/libQtGui.so.4 > > and the only palapeli part in those 68000 lines (except the very > beginning) is something like this: (it's moc-generated code, > unfortunately) > > ?#8 ?0x08084f10 in Palapeli::View::qt_metacall (this=0x84178a0, > _c=QMetaObject::InvokeMetaMethod, _id=35, _a=0xbf800678) > ? ?at /usr/src/debug/kdegames-4.4.85/i686-redhat-linux-gnu/palapeli/src/view.moc:87 > 87 ? ? ? ? ?_id = QGraphicsView::qt_metacall(_c, _id, _a); > > I hope that this is reproducible under any conditions with any similar > system, so I post only this tiny fraction to make sure that you've > reproduced exactly this bug. I can, of course, make full stack trace > with all required -debuginfo packages, if that was not the case. > > It's Fedora 13, qt-4.7.0-0.24.beta1.fc13.i686 (and everything else > from kde-unstable, right now). > > I'm not sure if this is the right place and if this report is of any > use. I'm sorry if it is not. Sounds to me like a qt-4.7.0.beta1 problem. Upstream should be interested in that. Doesn't DrKonqi catch the segfault? Well, to prove if it's a qt-4.7 problem, you could downgrade your qt to the 4.6.3 version. The upcoming KDE SC 4.5 doesn't need Qt-4.7 to work proper. I will try later, with a bit more time, to reproduce it. -- LG Thomas Dubium sapientiae initium
