This site has been retired. For up to date information, see handbook.gnome.org or gitlab.gnome.org.


[Home] [TitleIndex] [WordIndex

Drop or Fix Fallback Mode

Status: in progress

Description

With the release of GNOME 3.0, GNOME required some very basic hardware rendering support. Still in practice there were various issues. Some hardware vendors did not provide good drivers. Another issue was with running GNOME in a virtual machine, as most virtual machines software did not provide or emulate hardware acceleration.

To allow GNOME 3 to be used in such cases, a fallback mode was implemented. Some distributions labeled this mode as something other than fallback mode. This caused some grievance as it gave an impression that it was intended to provide a GNOME 2 experience. The fallback mode was always meant to be a temporary stopgap. It has become less and less useful as a pure fallback mode with recent releases: it's working (mostly), but it doesn't offer the high quality people are expecting from us.

Those are some of the issues we now have with the fallback mode:

In addition to these issues, some people would like to improve components of the fallback mode to work differently -- but in a way that would make the fallback mode work more like GNOME 2, and diverge from the GNOME 3 vision. Those contributions are usually blocked because the goal of the fallback mode is to work the GNOME 3 way.

Since the release of 3.0, a technology called llvmpipe has allowed for fast software rendering, lowering the need for the fallback mode. However llvmpipe doesn't currently work on some architectures (ppc, s390, arm?--ARM (hf) works-shawnl) and might not work in some non-Linux-based OS (OpenBSD support is not there, for instance).

What is clear is that the current status of fallback mode does not provide an acceptable experience, neither for people expecting a 'GNOME 2' experience, nor for people who cannot make use of 'GNOME 3'.

If we are serious about offering the fallback mode, we should invest more efforts into it. If we can't invest more effort, it might be better to simply say we don't support the fallback mode anymore and keep focusing on making our core UX rock.

Owner

Vincent Untz

Involved Parties

Release Team

Affected modules

Modules that can be dropped altogether when fallback mode goes away:

Modules that can be simplified:

Improvements that are held back by fallback mode:

Modules where functionality is broken/missing in fallback mode:

Current Status

Relevant information that is needed for this discussion:

Fallback mode was discussed in June. It was discussed again at the Boston Summit in October. It was discussed again on the list in October. And then the release team discussed it in its November meeting.

The outcome of the release team discussion was that we don't think we have the resources to provide fallback mode in adequate quality. Therefore, we should drop it from 3.8.

Side effects/things to address

Action Items

How to Help


2024-10-23 11:47