tracker bug for failed fallback created

[Colin Walters]

On Thu, Feb 17, 2011 at 9:01 AM, Matthias Clasen <mclasen at redhat.com> wrote:
> On Wed, 2011-02-16 at 11:21 -0800, Adam Williamson wrote:
>> Hey, folks. Just a note that I set up a tracker bug for known cases
>> where trying to start GNOME 3 results in something totally unusable -
>> Shell fails and fallback does not work correctly. So far there's a
>> couple of bugs blocking it. The tracker is
>> https://bugzilla.redhat.com/show_bug.cgi?id=678116 , it has the alias
>> F15GNOMEfail. Please add any appropriate bugs to it, for convenience.
>> thanks!
>
> Thanks, that is useful. Fallback is under active development atm.

I think we need to distinguish between hardware/driver specifc bugs
versus general ones.  Both of the ones on the list look
hardware-specific.  Fixing these kinds of things will involve at a
minimum a lot of back and forth with the reporter, running tools,
looking at output, etc.  We may be able to do some of this for F15,
but barring some major jump in manpower, it's unlikely we can do *all*
of them.

I think we're going to need to have an always-fallback hardware
blacklist somewhere.  Where exactly that lives and how it works is up
for debate.  I'd strawman that we make a new module/RPM
"gnome-shell-blacklist" and insert it in the startup path, but better
ideas are welcome.