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. 13-Way Low-End GPU Comparison With AMD's AM1 Athlon
  2. ASUS AM1I-A: A Mini-ITX Board For Socketed Kabini APUs
  3. Mini-Box M350: A Simple, Affordable Mini-ITX Case
  4. Overclocking The AMD AM1 Athlon & Sempron APUs
Latest Linux Articles
  1. How Much Video RAM Is Needed For Catalyst R3 Graphics?
  2. Ubuntu 12.04 LTS vs. 14.04 LTS Cloud Benchmarks
  3. Ubuntu 12.04.4 vs. 13.10 vs. 14.04 LTS Desktop Benchmarks
  4. AMD OpenCL Performance With AM1 Kabini APUs
Latest Linux News
  1. Linux 3.15 Lands Some DRM Graphics Driver Fixes
  2. AMD Is Disabling DPM Support For RV770 GPUs
  3. ReactOS Working On A Community Windows OS
  4. Borderlands Is Being Considered For Linux
  5. Mesa 10.0 & 10.1 Stable Get Updated
  6. Getting Hit By The Variable Performance Of The Public Cloud
  7. Git 2.0 Test Releases Begin With Many Changes
  8. Wine 1.7.17 Works On Its Task Scheduler, C Run-Time
  9. The Improv ARM Board Still Isn't Shipping; Riding A Dead Horse?
  10. Debian To Maintain 6.0 Squeeze As An LTS Release
  11. Wasteland 2 Is Finally Released For Linux Gamers
  12. FreeBSD Advances For ARM, Bhyve, Clang
Latest Forum Discussions
  1. The GNOME Foundation Is Running Short On Money
  2. Updated and Optimized Ubuntu Free Graphics Drivers
  3. Catalyst 14.3 Beta
  4. Suggestions about how to make a Radeon HD 7790 work decently?
  5. Radeon 8000M problematic on Linux?
  6. Linux Kernel Developers Fed Up With Ridiculous Bugs In Systemd
  7. After Jack Keane, RuseSoft will briing Ankh 3 to Linux through Desura
  8. Suspected PHP Proxy Issue