Linuxguy123 wrote:
> So I entered a bugzilla report on this issue and did a bit of background
> research.   https://bugzilla.redhat.com/show_bug.cgi?id=473446  The
> developer's response ?  They tagged the bug as UNFIXABLE.

Because that's what it is, the bug is in a proprietary driver we do not have
the source for, there's no way we can fix anything in it.

Next time buy hardware with Free (as in speech) drivers.

> Do they create a mini application to help the end user tune their video
> card to work properly ?  Nope.

How can we do this when the hardware is undocumented and the driver is
proprietary?

> Do they state that they have contacted NVidia and the issue is being
> sorted out ?  Nope.

Why should we? It's up to you to contact NVidia (which is what we told you
to do).

> Do they provide tips or a different version of folderview for people who
> have video cards that don't support acceleration ?  Nope.

We provide a version of folderview which works with any graphics card with
working drivers. If the driver is buggy, the driver needs to be fixed, not
the folder view.

And it doesn't really use that much in terms of acceleration, as far as I
know it's just basic XRender, not even OpenGL.

And there haven't actually been _any_ changes to the folderview applet
between KDE 4.1.2 and 4.1.3, your regression must come from somewhere else
(different version of the NVidia driver maybe?).

> The user is left to figure things out for themselves.  Go manually play
> around with your xorg.conf file.  Which has been the norm for nvidia
> users since RH8 days, except that livna, now RPMFusion finally came to
> the rescue recently.

That's because proprietary drivers are not, have never been and will never
be supported in Fedora.

        Kevin Kofler

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Reply via email to