F12: 30 second freeze when accessing certain panel items ?

[Linuxguy123]

On Wed, 2009-12-16 at 08:00 +0200, Eli Wapniarski wrote:

> Just my 2cents.
> 
> If from the command prompt you run setup then X configuration select
> the Nouveau driver. Go to the panel that should allow you to configure
> dual head go through the trouble of configuring it and click on OK.
> Nothing happens. Not even a crash. Nada, nothing. 

I experienced that when I did my upgrade too.

> And this is a bug I absolutely refuse to report. This is a basic QA
> issue never seeemed to get done cause the problem has been around
> since at least Fedora 11. While the configuration tool that comes with
> the proprietary driver just works.

Agreed.

> Nouveau doesn't support TV out. As a matter of fact I've tried an
> older ati card with tv out and I couldn't get tv out in an a tv only
> setup. Works fine with Nvidia geforce 2. Heck it even works with Vesa
> drivers. Nouveau not there yet. Maybe somebody could relate their
> experience with the intel chip set.

How about this little bug:

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

All the developers do is keep asking for data.  Its been given to them
several times.  Nothing has been resolved.  Thus I cannot use nouveau.

Or this one that they closed outright:

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

> And as frustrating and slow as the support has been from NVidia from time to time. They do indeed support Linux and when it works it works.
> 
> There is a world of difference between reality and ideology; between
> the actual and the potential. When the Nouveau drivers are ready I
> will be using them (I genuinely believe opensource is the superior
> development model.) Until then I need to use my computer for work and
> play. I need to get things done. If its a choice between 3/4 there but
> I can't do what I need to or want it to and 90% there and I can...
> guess what choice I'm going to make.

Well said, Eli.

Kevin, I really wish you would change your attitude towards the
proprietary drivers.

You repeatedly claimed that this bug was due to a problem in the
proprietary nvidia driver:
https://bugzilla.redhat.com/show_bug.cgi?id=525767

However, that problem disappeared in F12 with no change in the driver
version.  Hmmm....