> I agree with Jithin Emmanuel and am very angry against Kubuntu team. OK, I was quite angry too, but let's try not to lose temper but see how we can get out of this situation (that we should have never gotten into).
(I personally am in the lucky position that I can continue working unaffected from this bug, but only because I have a second machine - so I can temporarily avoid using the affected machine.) I'm missing two things here: (1) help on helping: i.e.: what can all the affected users do to help isolate the root cause of this bug (2) transparency Re (2): I think people would be much more comfortable if someone from Canonical acknowledged that this is a very severe bug with no universal workaround available (I'd really suggest to rank it as a stop-ship bug, please!). Hints at even more severe bugs (X not starting) don't help people in this bug. Secondly, this kind of bug damages the trust in Ubuntu releases: can we safely assume that upgrading to a new Kubuntu release(!) will NOT make that machine unusable for serious work? Thirdly, is there a discussion, whether including Qt 4.5 was an avoidable risk (with better advice available from the KDE developers)? If so, where is that discussion? What are we learning from it? How can a bug with 10 duplicates stay in "undecided" so long? -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
