From the crashing Krita department

Michael Thaler michael.thaler at
Wed Mar 22 22:26:05 CET 2006

On Wednesday 22 March 2006 21:54, Boudewijn Rempt wrote:

> svn up -r 521221 should do the trick.

The crash still happens with that version.

Here is the backtrace:

Using host libthread_db library "/lib/tls/i686/cmov/".
[Thread debugging using libthread_db enabled]
[New Thread -1235654432 (LWP 20732)]
[KCrash handler]
#6  0xb610ee65 in KisView::addAdjustmentLayer (this=0x868edd8)
#7  0xb611e910 in KisView::qt_invoke (this=0x868edd8, _id=106, _o=0xbf88aafc)
    at kis_view.moc:641
#8  0xb6da87ff in QObject::activate_signal () from /usr/lib/
#9  0xb6da9290 in QObject::activate_signal () from /usr/lib/
#10 0xb7718dd9 in KAction::activated () from /usr/lib/
#11 0xb7752f91 in KAction::slotActivated () from /usr/lib/
#12 0xb777205e in KAction::slotPopupActivated () from /usr/lib/
#13 0xb7772331 in KAction::qt_invoke () from /usr/lib/
#14 0xb6da87ff in QObject::activate_signal () from /usr/lib/
#15 0xb7136421 in QSignal::signal () from /usr/lib/
#16 0xb6dc5eec in QSignal::activate () from /usr/lib/
#17 0xb6ecc4b5 in QPopupMenu::mouseReleaseEvent () from /usr/lib/
#18 0xb7726171 in KPopupMenu::mouseReleaseEvent () from /usr/lib/
#19 0xb6de2f00 in QWidget::event () from /usr/lib/
#20 0xb6d3f122 in QApplication::internalNotify () from /usr/lib/
#21 0xb6d3f69d in QApplication::notify () from /usr/lib/
#22 0xb74cefde in KApplication::notify () from /usr/lib/
#23 0xb6cd08cf in QApplication::sendSpontaneousEvent ()
   from /usr/lib/
#24 0xb6ccbd51 in QETWidget::translateMouseEvent ()
   from /usr/lib/
#25 0xb6cca4f4 in QApplication::x11ProcessEvent () from /usr/lib/
#26 0xb6ce3ade in QEventLoop::processEvents () from /usr/lib/
#27 0xb6d57b01 in QEventLoop::enterLoop () from /usr/lib/
#28 0xb6d57a26 in QEventLoop::exec () from /usr/lib/
#29 0xb6d3dc35 in QApplication::exec () from /usr/lib/
#30 0xb7f74362 in kdemain (argc=1, argv=0xbf88b8f4) at
#31 0x08048722 in main (argc=1, argv=0xbf88b8f4) at

Do I get the current version of Krita back with svn up? How can you find out 
that svn up -r 521221 is the version from yesterday?

> Well, we worked quite hard on making Krita a lot more stable. Any crashes,
> please a backtrace! Pity you couldn't have managed to do these reports a
> week earlier. We're in release candidate mode now :-(

What does this actually mean? I changed the dropshadow dialog a bit today, is 
that ok? (No new strings, just made the dialog nicer and changed opacity from 
U_INT8 to use percent).

I also thought about adding things like ESC to abort the multiline and polygon 
tool. Is that o.k.?

(I was quite busy at university, I had to write applications and I had a job 
interview in Madrid for which I had to prepare. So there really was not much 
time for Krita. But I did not give up:-))


More information about the kimageshop mailing list