Archive for the ‘Bugzilla’ Category

BKO: How to look for duplicate bugs (without wasting too much time)

One of the best Bugzilla feature is its search interface. You can look for almost anything, a comment, an author, a modification date, a bug flag and so on…

Those who sometimes make some noise and suggest to throw away bugs.kde.org and replace it with <insert a random tracker name> are usually not the ones who triage bugs.

The downside: Bugzilla advanced search interface is quite complex…

So, what about saving some time ?

 

Using and abusing bookmarks and shortcuts to find duplicate bugs

Let’s try with Konqueror…

  • Open the Web Shortcuts kcm Settings > Configure Konqueror > Web Shortcuts

  • Let’s create a new shortcut

Shortcuts: Choose something you won’t forget easily 😉

Shortcut URL: https://bugs.kde.org/buglist.cgi?product=kmail&longdesc=\{@}&longdesc_type=allwordssubstr&bug_severity=crash

To search in more than a product, add several product parameters, eg: product=kmail&product=kontact

The longdesc will be replaced by our search string.

Note: on older Bugzilla versions, this parameter is called long_desc. so, use longdesc or long_desc but don’t mix them

bug_severity=crash : We’ll only look for crashes

 

Our shortcut is ready, what about testing now ?

Let’s try with a recurrent crash from 2009: enter  kmailc:KIO::Slave::Deref in Konqueror

 

and the result:

 

Using another browser ? No problemo !

  • Opera

Open Tools > Preferences > Search and press Add

 

  • Firefox

Open Bookmarks > Show All Bookmarks > Select (or create) a new folder > Organize > New Bookmark

 

etc…  Note that %s is used in these browsers.

To reduce the amount of result, you can also look for several lines of the backtrace: eg  kmailc KIO::Slave::deref KIO::Slave::gotInput

 

HOWTO…

Look for normal bugs or wish reports ? / List the critical bugs ?

the bug_severity parameter accepts the following values: critical, grave, major, crash, normal, minor, wishlist

eg: &bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor will look for all but crash and wishlist reports.

Look only for bugs marked as FIXED ?

Add  &bug_status=FIXED to the search URL

the bug_status parameter accepts the following values: UNCONFIRMED, NEW, ASSIGNED, REOPENED, RESOLVED, NEEDSINFO, VERIFIED, CLOSED

Find normal duplicate bugs ?

This is a bit harder, look for words, synonyms…

eg: kmailw toolbar returns https://bugs.kde.org/buglist.cgi?product=kmail&longdesc=toolbar&long_desc_type=allwordssubstr&bug_severity=wishlist here

 

 

 

Written by krop

18 May 2012 at 12:00

Posted in Bugzilla, KDE

Is Kmail still being developed?

This question was posted on the KDE forum a few days ago and deserves an answer.

Yes, KMail is maintained, It even has a new maintainer since a few months. Laurent Montel now takes care of KMail2 and already made an awesome work.

So, what’s the state of KMail in KDE 4.7 ?

Since the 4.7.0 tag, 556 commits were made in kdepim/kmail.
But KMail is no longer a monolithic block, so let’s add:

  • 207 commits in kdepim/mailcommon,
  • 51 commits in kdepim/mailfilteragent.
  • 98 commits in kdepim/messagecomposer,
  • 43 commits in kdepim/messagecore,
  • 54 commits in kdepim/messagelist,
  • 153 commits in kdepim/messageviewer,

Still not convinced ? Let’s head to the KDE Bugs Tracker

Since the creation of the KMail2 product, 690 bugs were marked as RESOLVED.

Amongst those:

  • 11 bugs were marked as UPSTREAM (bug in one of the KDEPIM/KDE dependencies)
  • 4 bugs were marked as DOWNSTREAM (distribution/packaging bug)
  • 6 bugs were marked as WONTFIX
  • 67 bugs were marked as INVALID
  • 77 bugs were marked as WORKSFORME (the reporter cannot reproduce the issue)
  • 178 bugs were marked as DUPLICATE (!!)
  • 324 bugs were marked as FIXED

Still according to our bugs tracker,

  • 14 bugs were explicitly marked as fixed in 4.7.2
  • 24 bugs were explicitly marked as fixed in 4.7.3
  • 24 bugs were explicitly marked as fixed in 4.7.4
  • 15 bugs were explicitly marked as fixed in 4.8

KMail bugs closed since KDE 4.7.3 (only the reports explicitly marked as fixed-in 4.7.4 are listed):

  • 143059 printing of mails ignores if part of the mail is blinded out
  • 258117 Cannot create Mailing List filter via context menu
  • 259422 Kmail ignores trash folder setting. It moves deleted emails to the local trash folder.
  • 263587 BCC addresses shows bcc’s to “To:” recipient
  • 278060 Mailing list detection does not work
  • 280649 Kontact crash when closing
  • 282652 Setting up filters for Distribution lists does not work
  • 284789 Does not remember mail transport
  • 285134 Closing the drop action popup by clicking somewhere else will execute a “move” operation instead of “cancel”
  • 285508 subject line is always spell checked with default dictionary
  • 285623 emails are not sent until restart of mail dispatcher agent
  • 285653 Thousands of errors “Select Failed, server replied A000… NO Mailbox …
  • 285814 Shortcut for moving mail to folder does not move to folder highlighted in dialog
  • 285878 search mail – unusable sort by date
  • 286505 kmail no more send mails
  • 286615 Encrypted email not decrypted in-time for printing
  • 286663 Kontact crashed when canceling creation of sieve script
  • 286827 Unable to reply to an encapsulated message
  • 286875 Redirected email is stored in wrong sent-folder
  • 286889 Move Thread to Trash Context Menu
  • 286922 edited mail from outbox deleted after closing
  • 287367 Kmail is truncating recipients in “reply to all”
  • 287696 redirected mail isn’t marked as redirected (or forwarded)
  • 287779 Copy Email then Paste As Attachment does not work as expected

Written by krop

7 December 2011 at 22:30

Posted in Bugzilla, KDE, kdepim

Time to close some KMail bugs…

With kdepim and kdepim-runtime 4.6 release getting close, I think it’s finally time to squash the KMail 1 bug reports.

What will happen ?

In a couple of hours, I’ll close the KMail product, which means reporting new bugs will not be possible anymore. The bugs audit will then begin.

Several phases are planned :

  • Revisit the KMail crash reports and close the ones that are no longer reproducible with KMail2
  • If a given crash is reproducible, open a new KMail2 report with a fresh and useful backtrace and a link to the old report.
  • Test the ‘Normal’ bugs, close the ones that cannot be reproduced, reassign the reproducible ones to the proper product (kmail2, kdepim, kdepimlibs…)

What to do with the wish reports has yet to be defined. I think evaluating the ones which received the most votes and discard the others is probably the best choice.

How can YOU help ?

You have KDEPIM 4.6 beta 5 installed ?  What about starting with triaging your own bugs ?

Once logged on https://bugs.kde.org, click on “My bugs” voilĂ , you’re ready to triage.

Want more ? visit https://bugs.kde.org/component-report.cgi?product=kmail, pick a category and check whether you’re able to reproduce the original report. Drop a comment to the report if you cannot close it.

Written by krop

22 April 2011 at 14:54

Posted in Bugzilla, KDE, kdepim