Revision as of 08:39, 1 June 2009

- 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

flash on kde4 messed up because of qt3's gtk engine bug #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.)

User:Lemma/GPU-Performance (moved to userbase now)

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 www.gmane.org which is: http://news.gmane.org/gmane.comp.kde.devel.bugs

@@ Line 23: / Line 23: @@
 [[/Priority_4.2_bugs|Priority list of 4.2 rendering bugs]]
+=Standard bug text=
+http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
+*Kubuntu
+Unfortunately, we can't help you with debugging distribution problems. However, these places can:
+http://forum.kde.org
+irc.freenode.org  on #kubuntu (you can use mibbit.com to access)
+http://www.kubuntu.org/support
+The release notes might give a clue:
+http://www.kubuntu.org/news/9.04-release
+FAQ: https://wiki.kubuntu.org/FAQ
 =Annoying bugs so I can find them again=