kontact, kdepim-3.5.2, dies when I try to create a calendar appointment. The back trace seems to show it crashing in pthread_mutexattr_init which is called from QBoxLayout::sizeHint(). The backtrace shows libthread.so.2 and libqt-mt.so.3. How-To-Repeat: Run kontact. Select the calendar application. Double-click a time from the day-view. Crash.
Responsible Changed From-To: freebsd-ports-bugs->kde Over to maintainer
Please report application bugs at http://bugs.kde.org and report the number your bug gets assigned here so we can track it. In order to get a more revealing backtrace to include with your bug report there, you also might want to recompile kdelibs and kdepim with WANT_KDE_DEBUG=YES in /etc/make.conf.
Probably the same as: https://bugs.kde.org/show_bug.cgi?id=124024
On Wednesday 26 April 2006 16:52, Michael Nottebrock wrote: > Please report application bugs at http://bugs.kde.org and report the > number your bug gets assigned here so we can track it. There are already some similar bugs at http://bugs.kde.org/. In particular: http://bugs.kde.org/show_bug.cgi?id=124504 http://bugs.kde.org/show_bug.cgi?id=124024 I reported the bug to the freebsd lists due to the phtread_mutexattr_init call. I thought it might be a FreeBSD/libpthreads specific bug. But all the other postings on http://bugs.kde.org/ make it appear to be a KDE bug and not specific to any particular OS. mike
Yes, it's easy to get confused by this - pretty much every stack trace of a crashed KDE program ends in libpthread. This is because every KDE program is in turn a Qt program and since Qt became threads-enabled in 2.2, that makes pretty much every program run in a thread by default. In practice, when debugging a KDE application crash, symbols from the system threads libraries in stack traces can be ignored, as can most symbols from Qt itself. If a trace doesn't turn up symbols from the actual KDE program or at least from a KDE-related library, that usually means that something needs to be recompiled with debug symbols enabled.
Till Adam has created a patch, which I've posted to http://bugs.kde.org/show_bug.cgi?id=124024 and attached to this message. It appears to fix the problem for me, though I haven't done extensive testing. Given the impact of this bug (not being able to create events in the calendar), it might be a good idea to add this patch to the kdepim FreeBSD port until the next official KDE release appears. mike --- trunk/KDE/kdepim/kdgantt/KDGanttView.cpp #536242:536243 @@ -638,7 +638,12 @@ bool block = myTimeTable->blockUpdating(); myTimeTable->setBlockUpdating( false ); myTimeTable->updateMyContent(); - qApp->processEvents(); + /* The below causes recursive calls to various size updating methods, which + * cause QCanvas to hide and show items like mad, which is very slow. If + * there is a legitimate gui updating issue here somewhere, it will need + * to be solved differently. + */ + //qApp->processEvents(); int hintHeight = myTimeHeader->height(); int legendHeight = 0; if ( showLegendButton() )
State Changed From-To: open->closed Fixed in kdepim-3.5.2_1. Thanks for reporting!