KOffice Bug Day and Krush!

To help the upcoming final release of KOffice, Bug Squad will be having our first KOffice Day this Sunday. We will triage the old bugs, and look for new ones (krush). We will be starting at around 07:00 UTC (be aware that summer time ends in various European countries on the 26th). As always we will be gathering in #kde-bugs on freenode IRC. You do not need any programming knowledge. All you need is a copy of the new KOffice Beta from your distribution with the debug packages installed. This is an easy way to give back to the KDE community, and also an excellent way to get involved.

Triaging just means going through the old bug reports and checking to see if they are still valid, and if they can be given new information. Often older bugs are fixed without the developers realising there is a bug report on it. Or a bug report may be poorly written, and so it gets overlooked. Triage helps to clear out and improve the bugs in the Bugzilla database. It seems simple, and it is! But it saves developers' time for coding, and is more important than you might at first think.

Krushing is a confusing term that just means looking for new bugs, and then filing bug reports. Developers will be standing by!

In particular, we will work on KWord, Krita, KChart, Karbon, KPresenter, KSpread, and more. Is one of these your favourite application? Or something you use a lot? Come join us and help make it better!


> Krushing is a confusing term that just means looking for new bugs, and then filing bug reports

By hlpr at Thu, 2008/10/23 - 5:00am

Also: "Bug Squad" is the confusing name for the team that designs new icon themes for the KDE desktop.
(Their latest work is the slick j/k theme.)

By Martin at Thu, 2008/10/23 - 5:00am

I'm happy. There is a bug (wishlist ) for 4 years (2004-12-21), which is now being solved


By ac_z01 at Fri, 2008/10/24 - 5:00am

> All you need is a copy of the new KOffice Beta from your distribution
> with the debug packages installed

just tried to install Koffice 2 beta2 in opensuse11, but the only packages I found on download.opensuse.org (http://download.opensuse.org/repositories/home:/CyrilleB/openSUSE_11.0) are still version 1.9.96 (Beta2 should be 1.9.98)

Would be nice to have up-to-date packages for opensuse so that users of this distro can participate in the bug day!

By Oliver at Sat, 2008/10/25 - 5:00am

mactalla, thanks for the link.

Now I successfully installed Beta 2. Wanted to take part in the bug day testing Krita, but it crashes as soon I want to do something on an image. I'm tired of filing crash reports, and please, can someone tell me if there is one single action in krita (except loading an image) that does not crash it? Thats really a pity, I was hoping that there would be a useful image editor for KDE soon...

By Oliver at Sun, 2008/10/26 - 5:00am

It's the same for me.
There is so much crashes in Krita that I don't know where to begin...
Is really Krita working fine on other computers??

I had the same problem with the Krita 1.6 serie.

By Ro at Mon, 2008/10/27 - 5:00am

Krita 1.6 is pretty stable, actually. There are some things that make it crash, like bad icc profiles. Now if your camera embeds a profile lcms thinks bad, and you try to use krita for your camera pictures, you will have a lot of crashes, but they should be pretty similar. I have been using Krita 1.6 myself to work on pictures taken with my camera and to draw and sketch without encountering any crashes.

As for Krita 2.0, it depends very much on what you are doing with it. Plain painting is pretty stable, as is running filters. Other things haven't been debugged well enough. Then there are distribution problems: Kubuntu notoriously has had problems with the way they compiled the jpeg import filter and OpenSUSE uses weird names for the tablet devices, which means Qt cannot pick them up unless you edit your xorg.conf by hand.

There simply are many problems we as developers never notice because our circumstances are different from yours, which is why it's important that people tell us about crashes (and other bugs) because no matter how obvious it might seem to you, we may never have seen that crash ourselves. If you're unsure whether it's something we'd like a bug report for, you can always contact us at the kimageshop@kde.org mailing list or on irc: #krita or #koffice, and we can investigate together with you.

This Sunday's bug day was wildly succesful for Krita: we got a much better handle on existing problems. Reporting bugs helps!

By Boudewijn Rempt at Mon, 2008/10/27 - 5:00am


I'll try the beta 2 asap and and give a feed back on the mailing list.

In general, Krita was really slow on the beta 1. Is it because of some debug mode?

By Ro at Wed, 2008/10/29 - 5:00am

Partly... There were a few unfortunate performance-guzzling bugs in the freehand painting code. Those are gone now, but they are still in beta2, as far as I know. And there is still a lot to improve performance-wise. The good news is, we're right on to it, the bad news is, krita will always be slower than an application that's hard-coded for 4 8-bit channels.

By Boudewijn Rempt at Wed, 2008/10/29 - 5:00am

And automatic crash reporting, does it work well enough? Do you see a need to provide "talkback" versions that submit more detailed crash reports?

By Andre at Thu, 2008/10/30 - 5:00am