Contribute/Bugsquad/BugDays/KOfficeDay1/Krush

< Contribute‎ | Bugsquad‎ | BugDays
Revision as of 08:22, 31 October 2008 by Lemma (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Introduction

KOffice Bug Day 1 will take place on Sunday, October 26th 2008. We will coordinate the day from #kde-bugs on irc.freenode.net, so if you are not already in that channel, please join it.

The aim of the Krush part of that day is to discover as many bugs as possible in various KOffice applications so they can be fixed before the final release of KOffice 2.

Requirements

You don't need any programming experience to help out with Krush Days, but you will need a recent version of KOffice, either svn trunk or the recent KOffice 2.0 Beta 2. Information on setting up KOffice from trunk can be found here. If you're having trouble installing KOffice, feel free to drop by on #kde-bugs early to get some help.

Applications put to test

As the KOffice suite is pretty big the developers asked us to concentrate on specific parts they think need the most love. Those are

  • KChart - or rather the flake shape formerly known as KChar :)
  • Karbon - the KOffice vector drawing application
  • KPresenter - the presentation application
  • KSpread - the spreadsheet application

Preparations

Select an application you would like to test. Then, go to that application's section below on this page. Add your name and svn revision number to the list of testers for that app.

Workflow

  1. Testdrive the application. The testing procedure is pretty much up to you but following some use pattern might be a good idea for a start (eg. try to create a real presentation) as that would probably exhibit the most annoying bugs (those most people are hit by). After you're done with that, try doing more obscure things and checking out as many of the buttons and options you can. Using features you're not using normally can provide some fun and help you finding bugs as well. (Of course you can also click around and smash your keyboard erratically to see what happens)
  2. Try to be thorough. If there's more than a way to accomplish a task, try all of them. If you've already been using an application in the past and remember a bug you encountered, try if it's still there.
  3. You encounter a bug.
    1. Check if someone has already put that bug in the appropriate section. If so, put that you can reproduce the bug below adding more details if you found any.
    2. Enter new bugs in the appropriate section giving as many details as possible. Remember, the more information there is the easier it will be for the developers to fix the bug.
    3. If the application crashed for you, try to get a good backtrace, paste it on pastebin and put the link below the bug. We'll pick it up later when the bugs are being filed. Due to the nature of KOffice, please try reproducing a crash you encounter in the other KOffice applications by using the crashing program's flake shape (if you're unsure about how to do that, please ask on #kde-bugs).
  4. If you're unsure about a bug, you can ask others on IRC if they can reproduce it as well.
noframe
 
Warning
Do NOT use rafb.net/paste as it expires after 24 hours. Use pastebin.ca instead.


Wrapping it up

After a while we'll start filing the bugs on bugs.kde.org. It's best to file bugs others have already confirmed because like that the developers will only get the good stuff.

Hints

  • You can edit single sections of this page if you you check Enable section editing via edit links in your TechBase Preferences.
  • Sometimes you might encounter edit conflicts if several people are working on the wiki page at once. We can mostly avoid those by keeping notes of the bugs we encounter in a text editor and file several of them later at once (don't forget to save).
Ktip.png
 
Tip
Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup ~~~ to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).


Applications

Some application specific tips are given in the sections below.

General KOffice

Application specific tips

This section is meant for bugs concerning all of KOffice (eg. general problems with flake shapes or the user interface).

Testers

Please put your IRC nickname and KOffice svn revision number (or beta2) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
Lemma svn trunk r878038 starting

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

  • bug #173622 - Shapes can't be removed using the DEL key - eg. in KWord. Behaviour should be the same across all applications. Lemma
  • bug #173737 - Adding dockers can resize the window. If you open too many the window now longer fits on screen. Lemma

Charting Shape (fka. KChart)

Application specific tips

You can add a chart in any of the KOffice applications as it's one of the flake shapes. Just select it from the "Add Shape" toolbox and drag it into the document area.

Testers

Please put your IRC nickname and KOffice svn revision number (or beta2) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
Lemma svn trunk r876132 starting

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

  • bug #173602 - Bar Chart/Percent-3D with sample data is drawn outside the shape's boundaries
  • bug #173605 - Widgets in tool options don't get reset properly when creating a new chart
  • bug #173608 - The Edit Data dialog might do good with some improvements

Karbon

Application specific tips

Application specific tips go here.

Testers

Please put your IRC nickname and KOffice svn revision number (or beta2) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
Blauzahl svn trunk r876167 working some
m4v svn trunk r876041 done

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

  • opening autosave files doesn't work. (when restarting after a crash) Blauzahl
    • seems to work now, r877685. m4v
  • bt for jaham's artistic text bug crash: http://kde.pastebin.com/f73689ba added it to the canvas and karbon crashed if Shape Properties docker was opened while Artistic Shape was selected Blauzahl
  • bug #173650 - karbon crashes if using a tablet. m4v
  • bug #173807 - karbon crashes while using split view. m4v
  • bug #173880 - selected tool switches to default tool by itself m4v FIXED
  • bug #173881 - spliting views duplicates the tool options docker. m4v FIXED
  • bug #173882 - can't set splitter orientation. m4v FIXED

KPresenter

Application specific tips

Application specific tips go here.

Testers

Please put your IRC nickname and KOffice svn revision number (or beta2) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
JustAnExample svn trunk r803492 starting

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

KSpread

Application specific tips

Application specific tips go here.

Warning: When editing cells, you will likely see this bug: https://bugs.kde.org/show_bug.cgi?id=173293

Testers

Please put your IRC nickname and KOffice svn revision number (or beta2) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
Lemma svn trunk r876329 still ongoing

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

KWord

Application specific tips

Kword is not top priority today, but if you find problems during triaging, add them here.

Testers

Please put your IRC nickname and KOffice svn revision number (or beta2) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
jtamate svn trunk r874912 working
jrt svn trunk r875816 working
gkiagia svn trunk r875984 working
Blauzahl svn trunk r876167

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

  • Bug 1. Start a new document using the Colorful Document template, wait until the template seems to finish, type a word, and you get a crash. Look at http://pastebin.com/m4b1cb83c for the backtrace. Jtamate
  • Bug 2. I see a lot of stdout traces with:

Atttempt to use QAction "...." with KXMLGUIFactory!

Shortcut for KAction "...." "...." set with QShortCut::setShortcut()! See KAction documentation. Jtamate

  • Bug 3. Kword does not recognizes the autosaved files made by itself. Jtamate
  • bug #173600 - "Create Template" menu item missing in KWord. Lemma
  • bug #173635 - kword crashes while typing using the colorful document template gkiagia
  • bug #173636 - importing an html document results in internal error gkiagia
  • bug #173630 - "Format -> Page Layout ..." does nothing jrt 00:19, 28 October 2008 (UTC)

Taken together with bug 173600, this makes it basically impossible to do anything. jrt 00:19, 28 October 2008 (UTC)

When I retry from the autosave file, I get: error occurred while parsing at line 1, column 1 QXml(l18N_EXCESS_ARGUMENTS_SUPPLIED) Blauzahl

Krita

Application specific tips

Krita is not top priority today, but if you find problems during triaging, add them here.

Testers

Please put your IRC nickname and KOffice svn revision number (or beta2) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
jtamate svn trunk r874912 working
Lemma svn trunk r875799 working

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

  • Hint. Krita initial page to create a new RGB picture does not fit in an 800x600 screen because the left selection (cmyk, rgb...) and the use this template are just one line bellow where they could be. Jtamate
  • Hint. Krita config screen for color managemt does not fit in an 800x600 screen by one line displacement on the screen top. Jtamate
  • Bug. The help|Change language option is missing. Jtamate
  • bug #173584 - Opening the testcase of bug #137702 crashes krita. Lemma
  • bug #173589 - Create a new image, draw something, delete the layer -> image still visible, even after adding a new layer. Lemma
  • bug #173591 - Crash on creating a new file after previously closing the last open one. Lemma
  • bug #173590 - wish. no visual feedback on progress when opening a ps file in Krita. Lemma

This page was last modified on 31 October 2008, at 08:22. This page has been accessed 3,751 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal