1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Calling For A Fork Of GNOME 3's Fallback/Panel Mode

GNOME

Published on 21 November 2012 12:58 PM EST
Written by Michael Larabel in GNOME
8 Comments

GNOME's Vincent Untz has written about the recent decision to remove the GNOME3 fall-back mode with the forthcoming GNOME 3.8 release. He thinks the situation will improve but he basically calls for the community to fork and maintain the GNOME fall-back (gnome-panel, Metacity, etc) components assuming there is enough interest.

GNOME developers decided to drop the fallback mode rather than maintain it since it was already a burden to take care of and not always well tested. For those without the GPU/driver support to handle GNOME Shell with Mutter, LLVMpipe will now be used instead for running the heavy GNOME desktop. However, LLVMpipe doesn't work for everyone.

Untz recognizes that this may cause some fallout in GNOME 3.8 so he recommends those potentially negatively affected to stick with GNOME 3.6 for the time being. "There might be cases where these improvements will not be good enough in 3.8 (or with the Mesa and llvmpipe versions available at that time), resulting in a GNOME version that people might not consider acceptable in terms of performance or hardware support. Things will improve with time, obviously, and 3.10 will solve more and more issues; hence I would recommend to people hitting such issues to stay with 3.6 for a few more months."

In his blog post he then goes on to basically call for the community to fork the old GNOME 3.x fall-back mode.
Of course, this raises the question of what happens to the components of the fallback mode: gnome-applets, gnome-panel, gnome-screensaver, metacity, notification-daemon, polkit-gnome, etc. These components don't necessarily have to go away: they're just not part of what the GNOME project officially releases, and people are welcome to keep working on them. It's really up to each maintainer.

Now, I believe a group of people could well adopt all the fallback components and keep building a great desktop, on top of other GNOME 3 bricks. They wouldn't even have to restrict themselves to what the GNOME 3 vision is (which is something that blocked some people from seriously contributing to gnome-panel). I don't think it'd be actually too much work: the code is already there! Of course, there would be some compatibility bits removed from other GNOME modules that would need to be moved elsewhere, but in most cases, it's really just about "moving" the code, not "re-implementing" things.

To be honest, I would really have loved if the MATE people had taken such an approach (maybe it's not too late?). I think it's a more reasonable effort than effectively forking all of GNOME 2, including obsolete technologies, as the amount of work is much more reasonable.

I'm eager to see if a group will step up to keep alive this old code, which represents thousands of hours from many of us! I wouldn't use it, but it would still make me happy :-)
Now be sure to participate in the 2012 GNOME User Survey.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. CompuLab Intense-PC2: An Excellent, Fanless, Mini PC Powered By Intel's i7 Haswell
  2. From The Atom 330 To Haswell ULT: Intel Linux Performance Benchmarks
  3. AMD Radeon R9 285 Tonga Performance On Linux
  4. Apotop Wi-Copy
Latest Linux Articles
  1. AMD Moves Forward With Unified Linux Driver Strategy, New Kernel Driver
  2. MSI: Update Your BIOS From The Linux Desktop
  3. NVIDIA vs. AMD 2D Linux Drivers: Catalyst Is Getting Quite Good At 2D
  4. 15-Way GPU Comparison With Mesa 10.3 + Linux 3.17
Latest Linux News
  1. NVIDIA's NVPTX Support For GCC Is Close To Being Merged
  2. KDE's KWin On Wayland Begins Using Libinput
  3. Khronos Releases OpenVX 1.0 Specification
  4. Linux Kernel Working Towards GNU11/C11 Compatibility
  5. Ubuntu 15.04 Is Codenamed After A Monkey: Vivid Vervet
  6. Following GCC, Clang Looks To Default To C11
  7. Users/Developers Threatening Fork Of Debian GNU/Linux
  8. Linux 3.18-rc1 Released One Week Early With Many Changes
  9. The VC4 Gallium3D Driver Is Still Moving Along For The Raspberry Pi
  10. Direct3D 9 Support Might Land Within Mainline Mesa 3D Drivers
Latest Forum Discussions
  1. Users/Developers Threatening Fork Of Debian GNU/Linux
  2. HOPE: The Ease Of Python With The Speed Of C++
  3. NVIDIA Presents Its Driver Plans To Support Mir/Wayland & KMS On Linux
  4. AMD Is Restructuring Again, Losing 7% Of Employees
  5. Bye bye BSD, Hello Linux: A Sys Admin's Story
  6. Open-Source AMD Fusion E-350 Support Takes A Dive
  7. Upgrade to Kaveri, very slow VDPAU performance
  8. ChromeOS Drops Support For EXT2/EXT3/EXT4 File-Systems