High resource usage for Konq, nspluginviewer and Xorg...

[Linuxguy123]

On Fri, 2010-02-26 at 14:08 +0100, Kevin Kofler wrote:
> Linuxguy123 wrote:
> > Could you please smear the closed source driver a bit more ?  Just
> > because its closed source doesn't mean its bad.
> 
> Sure it does.
> 
> And now FUCKING STOP TO FUCKING FLOOD OUR MAILING LIST with your off-topic 
> whines about us not supporting proprietary crap!
> 
> Go use Ubuntu or Window$ and leave us in peace! We're fed up of your endless 
> repetitive complaining about the same issues we can't fix. We're also fed up 
> of you systematically blaming KDE for problems with proprietary software.   

I think this email is a display of terrible behavior.  

I normally wouldn't indulge this behavior, except that I want people to understand a bit of the background to this situation.

a) As far as I know huge changes were made to the KDE multimedia
subsystem, aka Phonon.  CPU usage was not high before the KDE 4.4
update.  It is after.  There were no changes to nspluginviewer or the
nvidia driver during this period.

b) I have reported a number of bug that were shut down due to "the use
of the proprietary nvidia driver" where it was ultimately found that the
driver had nothing to do with it.  

Specifically, at least these two.

https://bugzilla.redhat.com/show_bug.cgi?id=525767

https://bugzilla.redhat.com/show_bug.cgi?id=504173

c) We don't expect anyone to be able to troubleshoot issues within
proprietary software.  But we also don't think that issues should just
be written off carte blanc when a proprietary driver is involved.   

Given the number of changes made in the Phonon effort and the fact that
neither nspluginview and kmod-nvidia changed, what do you think the
chance of the issue lying in Phonon is ?

d) Open source software is about personal FREEDOM.  The freedom to use
whatever we want, according to our criteria.  I feel it is unfair to
outright criticize people for using proprietary components where they
feel they must.

Thanks for listening.