Revision as of 06:52, 14 August 2008 by Blauzahl (Talk | contribs)

Jump to: navigation, search

Ha ha, I have a user page now. And it's a mess.


Pages I use all the time

Bugsquad top level pages


List of people in bugsquad, nonofficial & incomplete.

BTW KDE session will not exit fully if there are drkonqi windows open.

sample bug bt and problems with it

Pages to move out of userspace

How to triage bugs.

cf User:Grundleborg's version

Annoying bugs so I can find them again

  • kio_http ipv6 dns bug: [154774]
    • these 2 bugs together are evil^10!! they gave me testing pleasure for about 10 hours :( katastrophe 22:48, 17 June 2008 (CEST)
      • poor katastrophe! Note to onlookers: these tend to be reported to the konq component
  • konqueror crashes on close: [156172]
  • makes Der Spiegel unreadable :P (gwenview bug) [161443]
  • flash on kde4 messed up because of qt3's gtk engine [162824]
    • Quote Pinotree: The reason is simple: do *NOT* use gtk-qt-engine for gtk. Otherwise, your konqueror4 will load the flash plugin, that in turns uses gtk, that in turns loads Qt3 (because of gtk-qt), and the imcompatibility between Qt3 and Qt4 will do the rest. (He closed it as invalid. [Is] a dup.)
  • nVidia


  • IMAP

lost mail

  • Plasma

download widgets crash

Pino's very short triage intro: "pre-filter" or "how to do incoming triage"

  • Look at the new bugs, and sort them out (invalid, or reassign them, or marking as dupe if it is, etc)
  • Use the "New reports since 3 days" link on your bugs.k.o homepage. That's the start point, or read kde-bugs-dist via which is:

Pages to look at



Khtml stuff

Bugs I should file/testcase

Making things work

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal