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 Benchmarking Platform
Phoromatic Test Orchestration

Whoops, There's A Big Problem For Wayland GTK+

Wayland

Published on 18 March 2012 10:01 PM EDT
Written by Michael Larabel in Wayland
53 Comments

It turns out there's a rather serious issue for some systems when having Wayland support within GTK+ exposed, which may hinder the Wayland GTK+ availability in the near-term.

As I wrote about a few days ago, Wayland support isn't for end-users in Ubuntu 12.04 and the GTK+ version they are shipping is 3.4. GTK+ 3.4 has the Wayland GDK back-end that works as an alternative to the X11 back-end and can be dynamically utilized. With the supported GTK+ code, it's as easy as building it with the --enable-wayland-backend option, but that's not happening for Ubuntu 12.04 LTS or by any other major distribution right now as far as I'm aware. It turns out that for some users this is good to not have the Wayland support exposed.

Building the GTK+ Wayland support currently depends upon having cairo-gl, the OpenGL version of the Cairo drawing library. However, cairo-gl with the NVIDIA binary driver can be a memory-hungry mess. Using cairo-gl at this point with the NVIDIA binary driver appears to be a big mess. This isn't just about using additional memory when running GTK+ applications on Wayland (where the NVIDIA binary driver isn't even compatible at this point), but the GL version of Cairo on X11 would be shafted.

This memory usage problem only seems to be present for the NVIDIA binary driver, but the open-source NVIDIA (Nouveau) driver isn't affected, the AMD Catalyst driver, nor any of the other open-source drivers have a hard time dealing with cairo-gl.

The solution to this is either have NVIDIA address their driver issue(s) causing excessive memory usage with cairo-gl, ship multiple versions of Cairo on the system (but there's some packaging problems currently), or change how Cairo loads libGL such that it only happens when a client requests an OpenGL context. The alternative is just to let NVIDIA binary users burn through the additional system memory.

This issue is talked at length in this Wayland mailing list message.

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 News
  1. Trying To Run The Intel Core i7 5775C On Linux
  2. VirtualBox 5.0 RC3 Brings VMM Fixes, Takes Care Of Some KDE DnD Problems
  3. Ubuntu Is Finally Fixing Its Annoying GRUB Setting
  4. Firefox 39.0 Brings New Features, HTML5 Changes
  5. OPNsense 15.7 Released As Fork Of Pfsense
  6. The Less-Powerful Intel Compute Stick With Ubuntu Will Soon Ship
  7. Kodi 15.0 Release Candidate 1 Arrives
  8. Fedora 23: Python 3 Default Approved; Netizen Spin Rejected
  9. GNOME Shell & Mutter Just Landed More Wayland Improvements
  10. Ubuntu MATE Announces A Partnership With A PC Hardware Vendor
Latest Articles & Reviews
  1. 6-Way File-System Comparison On The Linux 4.1 Kernel
  2. How KDE VDG Is Trying To Make Open-Source Software Beautiful
  3. Attempting To Try Out BCache On The Linux 4.1 Kernel
  4. CompuLab's Fitlet Is A Very Tiny, Fanless, Linux PC With AMD A10 Micro
Most Viewed News This Week
  1. Kubuntu 15.10 Could Be The End Of The Road
  2. KDBUS Won't Be Pushed Until The Linux 4.3 Kernel
  3. Pinos Is For Linux Video What PulseAudio Is For Audio
  4. The State & Complications Of Porting The Unity Editor To Linux
  5. The Staging Pull For Linux 4.2: "Big, Really Big"
  6. Latest Rumor Pegs Microsoft Wanting To Buy AMD
  7. "PulseVideo" Coming To Complement PulseAudio?
  8. Exciting Features Merged So Far For The Linux 4.2 Kernel