Lxde Github

GitHub - lxqt/lxqt: Checkout all LXQt components at once by using git submodule. LXDE.desktop GitHub Instantly share code, notes, and snippets.


Multiload-ng is a modern graphical system monitor.It's a near-complete rewrite of the good old GNOME multiload applet, that aims to support every existing panel.

It supports the following panels:

  • XFCE (xfce4-panel)
  • LXDE (lxpanel)
  • MATE (mate-panel)
  • Ubuntu Unity (through libappindicator)
  • Every panel with support for Application Indicators
  • System tray (virtually any panel with a systray, in particular those without external plugins support, like tint2)
  • Standalone (has its own window, not embedded in any panel)
  • Avant Window Navigator (EXPERIMENTAL)

Multiload-ng can be built with GTK2 and GTK3, so can be embedded within GTK2/GTK3 builds of all the panels above.



  • Draw graphs of system resources (learn more)
  • Customizable under every aspect
  • Builtin color schemes (learn more)
  • Independent configuration for each graph
  • Automatically adapts to container changes (panel or window)
  • Written in pure C with few dependencies = little CPU/memory footprint
  • Customizable tooltips with lots of information
  • Customizable mouse actions, with user-defined command lines
  • Customizable graph scale
  • Customizable data sources (filters)


Small panel, all graphs are visible

Larger panel, all graphs visible. Thicker (2px) borders, graphs have different widths

Each graph has different border width. Color scheme: Uranus

Graphs have no borders. Extra spacing and padding. Color scheme: Solarized Light

Graph background matches panel background. Very stylish

Graphs have vertical orientation on horizontal panel. The opposite is also possible

Graphs are contiguous, with no border and no spacing, behaving like a single graph. Color scheme: Jupiter

Just CPU graph. Color scheme: Ubuntu Ambiance

Multiload-ng in action

Multiload-ng running on Ubuntu

Multiload-ng running on LxPanel. Graphs have different widths

Multiload-ng running on MATE panel. Changed some background colors

Multiload-ng running on XFCE panel. Color scheme: Windows Metro

Standalone window, horizontal layout. Color scheme: Fruity

Standalone window, vertical layout. Color scheme: Numix Light

The Graphs


Lxde Github Io

Draws CPU usage, differentiating between cycles used by programs with normal andlow priority, by the kernel and waiting for I/O to complete.

Tooltip shows CPU information (model, cores, frequency/governor).


Draws RAM usage, differentiating between memory used by the applications (directlyand through shared modules) and memory used as cache/buffers.

Tooltip prints these values as percentage and absolute value.


Draws network I/O of every supported network interface, differentiating betweeninput, output and local (loopback, ADB, etc) traffic.

User can choose which interfaces will be used for graph calculations.


Draws swap usage, when swap is present.


Draws load average, as returned by uptime.

Tooltip shows load average of 1,5,15 minutes, number of active processes/threadsand informations about currently running kernel.


Draws Disk I/O, differentiating between read and write speeds.

User can choose which partitions will be used for graph calculations.


Draws temperature of the system.

User can choose which sensor/driver to read for drawing the graph, or let Multiload-ng automatically select the hottest temperature measured among all detected sensors.


Draws charge and status of system battery, using different colors for charging,discharging and critical level.

Tooltip shows additional battery info.


Draws numeric output of user defined command line. Up to 4 values will be shown together.
Can be also used to monitor changes to a file using cat <filename> as command line.
Can be also used to execute arbitrary shell commands using sh -c '<commands>' as command line.

Tooltip shows contents of command's stderr.

Stay tuned

Other graphs are coming!

Color Schemes

Multiload-ng has color scheme support, that is, every color of the graphs can be changed.This include borders and background (two-color gradient).

Colors (except for border and background) have alpha values, so you can play withtransparency too!

There are also some builtin color schemes, which you can set with a single click.Some examples are present in screenshots above. Here is a partial list:

  • Default color scheme with its distinctive colors
  • Tango from Tango Desktop Project
  • Solarized by Ethan Schoonover in both Light and Dark variants
  • Color schemes inspired by famous Linux distribution: Ubuntu (both Ambiance and Radiance), Linux Mint
  • Color schemes inspired by famous GTK themes: Numix (both Light and Dark), Arc
  • Color schemes inspired by outer space: Moon, Venus, Earth, Mars, Jupiter, Uranus, Neptune
  • Color schemes inspired by The Simpsons (from the work of designer Hyo Taek Kim, watch it here)
  • Color schemes inspired by old cartoons and video games: Dragon Ball Z, Super Mario Bros (with colors from original 1985 game)
  • More!


Multiload-ng started as a simple port of multiload-nandhp to lxpanel>0.7.As I become familiar with code, I started making other little changes, and cleaning the code.I then contacted original author, but received no reply - meanwhile the plugin continued improving.

This came to the point where the changes became many and deep, and I realized that this wasn't the same project anymore.I knew that a fresh start would give a boost to development, and at the same time itwould allow to choose future directions with more ease.

For the above reasons, I made Multiload-ng a separate project.The name changes too (so the filenames), in order to allow them to be installed together.

Multiload-ng gained popularity starting from version 1.1.0, that introduced GTK3 support. Some Linux bloggersstarted writing about the plugin, and some contributors started to send translation in their languages.

All this keeps the author motivated, and the project alive and kicking!

System Requirements

Common requirements

These are the packages required to build any version of the plugin.Some panels may require additional packages (see below).

PackageMin version (GTK+2)Min version (GTK+3)
gtk+>= 2.20.0>= 3.0.0
cairo>= 1.0>= 1.0

Multiload-ng requires a reasonably recent Linux kernel (>2.6.36) built withspecific configuration options. These are not build-time requirement, ratherrun-time ones. Here are required options:

  • CONFIG_SYSFS(sysfs filesystem support)
  • CONFIG_PROC_FS(/proc filesystem support)

In addition, enabling the following options allows Multiload-ng to gather all possibleinformations from the system. These are not strictly required, but some graphs mightnot work properly, or not work at all, without these other options:

  • CONFIG_CPU_FREQ(CPU Frequency scaling)
  • CONFIG_POWER_SUPPLY(Power supply class support)
  • CONFIG_HWMON(Hardware Monitoring support)
  • CONFIG_THERMAL(Generic Thermal sysfs driver)
  • CONFIG_SENSORS_* - enable sensors you need

Any modern kernel (since 2010) sets all these options automatically, so generallyspeaking you don't have to worry about user kernels.

It is recommended building with gcc. Multiload-ng code is pretty standardscompliant, so it should work flawlessly with any C compiler, but usingcompilers other than gcc is untested and it's not guaranteed to succeed.

Requirements for Application Indicator (Ubuntu Unity and others)

In addition to common requirements (see above)these packages are required to build Application Indicator:

PackageMin version
libappindicator>= 0.4.92

Check which GTK+ version is supported by your target panel.Ubuntu Unity needs AppIndicators to be built against GTK+3.You may have to set correct GTK+ version (see here for instructions).

Requirements for LXDE panel

In addition to common requirements (see above)these packages are required to build LXDE panel plugin:

PackageMin versionNotes
lxpanel>= 0.5.8
libmenu-cacheOnly for lxpanel <= 0.7.0
libfm1.2.0Only for lxpanel >= 0.7.0

Note that due to a mistake in lxpanel source, if you are using lxpanel 0.7.0you will need both libfm and libmenu-cache. This was fixed in version 0.7.1.Read about this here.

You might have to force GTK+2 build (see here for instructions).

Note that LXDE 0.5.8 or greater is required.

Requirements for MATE panel

In addition to common requirements (see above)these packages are required to build MATE panel plugin:

PackageMin version
libmatepanelapplet-4>= 1.7.0

Check which GTK+ version is supported by your panel: mate-panel used to be GTK+2only, while newer versions of mate-panel are GTK+3. You may have to set correctGTK+ version (see here for instructions).

Note that MATE 1.7 or greater is required.

Requirements for XFCE panel

In addition to common requirements (see above)these packages are required to build XFCE panel plugin:

PackageMin version (GTK+2)Min version (GTK+3)
libxfce4panel>= 4.6.0>= 4.12.0
libxfce4util>= 4.6.0>= 4.12.0

Check which GTK+ version is supported by your panel: xfce4-panel used to be GTK+2only, while newer versions of xfce4-panel supports GTK+3 too. You may have to setcorrect GTK+ version (see here for instructions).

Note that XFCE 4.6 or greater is required for GTK+2 plugin.Note that XFCE 4.12 or greater is required for GTK+3 plugin.

Install instructions

Package generators

Take a look at extras directory.There are scripts for most Linux distributions, that generate packages which canbe then installed through package managers.

External support

  • For Ubuntu/Mint and derivatives, WebUpd8 PPA hosts stable packages for all supported panels.Read how to install here (instructions are valid for all versions).
  • Arch users can get Multiload-ng from AUR. There is a separate package for each variant of the plugin.Just search for multiload-ng in AUR!

If your distro isn't covered above, or you just want to have some control over build (e.g. enable/disable some plugins, try experimental features), you can build it yourself.

Build Instructions

Get the source

Execute the following command line (you must have git installed):
git clone https://github.com/udda/multiload-ng

If you don't have git, download the lastest source ZIP here.

Or, if you don't want any surprise, download a stable release here.


Move to the directory that contains source code just cloned and run:

Now run configure script:
./configure --prefix=/usr
Change prefix as needed. /usr is the prefix of most distros.If you do not specify a prefix, configure script tries to infer it from installed programs. If this fails, prefix defaults to /usr/local.

LxPanel in systems with Multiarch support

Some Linux distributions (like Debian and its derivatives) have Multiarch support, means thatthey can install 32 bit and 64 bit libraries alongside each other.

This affects libraries location for LxPanel plugin, and it must be set manually.

Users of Multiarch-enabled systems running LxPanel (e.g. Lubuntu) have to set libdir directly, by adding to ./configure theoption --libdir=/usr/lib/x86_64-linux-gnu in 64 bit systems, and --libdir=/usr/lib/i386-linux-gnu in 32 bit systems.

If plugin does not show up in the list of LxPanel plugins, you could try to repeat build process with this configure setting.

GTK version

Build system automatically selects highest GTK+ version available. If you need to build against a lower version, you have toset it manually (see next section, Advanced configure)

For example, LxPanel and older versions of MATE and XFCE panels need GTK2 version of the plugin.They need to add option --with-gtk=2.0 to ./configure.

Advanced configure

If you are ok with default settings, you can skip this paragraph and head to Build section. Otherwise, continue reading.

Configure script automatically detects installed panels (and related development packages) and enables panel plugins accordingly. You can force enable/disable them using --with-PLUGIN, --without-PLUGIN or --with-PLUGIN=yes no (replace PLUGIN accordingly)

Multiload-ng's ./configure has some extra options:

--with-gtk=2.0 3.0 autoGTK+ version to compile againstRemember to set same GTK+ version of the target panel! Otherwise you could get linking or runtime errors.
--disable-deprecationsDisable GDK/GTK deprecation warningsUseful when build system enforces -Werror. Some deprecated symbols does not have adequate replacement yet.
--enable-experimentalCompile in experimental codeMay be unstable/malfunctioning. Only for testing/developing purposes.
--enable-debugAllows debugging with GDBThis enables required CFLAGS.
--enable-profilingAllows profiling with gprofThis enables required CFLAGS
--disable-autostartDo not install autostart entriesAutostart entries are normally put into /etc/xdg/autostart for some plugins (indicator, systray...)

To get a list of all available options, type:
./configure --help

When you are satisfied with your flags, run ./configure with selected options.


This is easy. Move to the directory that contains source code and execute:


To install (must run make before), execute:
sudo make install

To later uninstall you need source directory. If you deleted it, just download again, and run Configure part. Then execute:
sudo make uninstall

How to Contribute

Read here

Help & Troubleshooting

Plugin shows only a vertical blank line

Probably you compiled against the wrong GTK+ version. E.g: LXDE panel and older version of MATE and XFCE panelsare still based on GTK+2, and Multiload-ng build system automatically selects GTK+3 when available.

Try running Configure with the right options (see Configure section above)

High CPU usage

This has basically two causes:

  • low update interval
  • parametric command

Lowering update interval means more redraws per second. CPU usage might become noticeable on older systems.

Command line of parametric graph is called synchronously every time the graph is redrawn.This means that plugins hangs waiting for the command to terminate and return numbers.

You should try to raise update interval, and try to use lightweight programs for parametric command line.

Memory usage is not the same reported by task manager

There is some disagreement on how to count some components of kernel memory. Some resource monitors(like htop and some graphical task managers) count them as used memory, while other programslike top and free report them as cached.

Multiload-ng now allows to choose where to count that memory component, in orderto align memory usage value with what your favorite resource monitor reports. You canfind the switch in Advanced Preferences window of Memory graph.

Tooltips not showing reliably

This happens often on GTK+3 builds. Due to changes in the way tooltips are handled in GTK+3,sometimes they might show with big delay, or not show at all. Sometimes they do show up,but without being updated with every graph redraw, as they should.

Basically, being on GTK+ side, there is not much that can be done from Multiload-ng.Some users 'solved' it by raising update interval of the graphs aboveGTK+ default tooltip delay time (500 ms in many systems).

Starting from GTK+ 3.20.0, tooltips appear to be working normally.

Plugin doesn't show, and terminal is full of lines like this: GLib-GObject-WARNING *: cannot register existing type 'GtkWidget'

You probably selected wrong GTK+ version when building. See GTK Version section


Q: Which are the differences with original Multiload applet?

A: First of all, this project is forked from original Multiload. Nearly 100% of the code has beenrewritten by now, but Multiload-ng is designed to keep ALL the features of the original multiload,and extend them.

There are some notable differences:

  • Original multiload contains old and unmantained code, Multiload-ng is actively mantained
  • Multiload-ng has a Wiki!
  • Multiload-ng runs on a variety of panels, including those of the original multiload
  • Multiload-ng does not depend on glibtop, meaning less bugs and less overhead
  • Multiload-ng detects automatically installed task manager and launches it without configuration
  • Multiload-ng has additional graphs, and more will be added in the future
  • Multiload-ng has way more graphical customizations
  • Multiload-ng has color schemes support
  • Multiload-ng responds to mouse events with per-graph customizable actions
  • Multiload-ng can choose its orientation regardless of panel orientation
  • Multiload-ng can set graphs scale manually
  • Multiload-ng has higher limits for graph size and update interval
  • Multiload-ng can also be run without any panel
  • Multiload-ng can filter which source to show in suitable graphs
  • ...and so on

Lxde Github Download

Not enough? Try it in your system and you won't come back!

Q: Doesn't a system monitor use system resources by itself?

Lxde Github

A: Yes. This is true for every system monitor. That's why resources usage from Multiload-ng is kept to a negligible level.

Q: I found a bug/I have a suggestion! How can I report?

A: It's easy. Read here

Q: Will you continue the development of Multiload-ng?

A: Of course! To get an idea of future directions, take a look at the Wishlist.

Q: Why don't you port to panel [insertyourpanelhere]?

A: Because of a number of reasons:

  1. I don't have the time -> Will be done when I find some time
  2. I don't have required knowledge -> Will be done when I learn it
  3. I didn't know that [insertyourpanelhere] existed/supported plugins -> Now I know, I'll investigate and eventually you will have your plugin
  4. Requires too much work -> If it's worth it, see #1
  5. Requires plugins to be written in languages other than C -> Sorry, this would break ALL existing plugins. Unless special cases (like supersets of C or simple wrappers), it's very likely it can't be done.

The best way to get a new port is to suggest it (or code it yourself, of course). Feel free to submit an issue about your request, it will be considered carefully.

Lxde Github Download


All product names, logos and brands are property of their respective owners. All company, product and service names used in this software are for identification purposes only. Use of these names, logos, and brands does not imply endorsement, and do not infringe any patent, trademark, copyright, license or any other proprietary right of any third party.


  • FSF and creators of original Multiload applet (see AUTHORS file), for giving a good starting point
  • Translators, for sending me always up-to-date translations. Read their names in About dialog, in git commits comments, or looking at the source, in the PO file headers
  • Beta testers, for reporting bugs that I would have never discovered, because they didn't happen in any of my systems. Now these bugs are all gone, thanks to them. Some translators also helped me with testing.

Lxde Github Web

Canonical was founded with the goal of bringing polish, consistency and usability to the Linux desktop. Derided unfairly by some as not contributing much technically to the open source ecosystem, Ubuntu has been undeniably popular, becoming for the last five years the closest thing we have to a de facto standard distribution. I myself switched to using Linux full time coinciding with this phenomenon, drawn by the mixture of freedom, power and flexibility. For the first time in my experience, Linux mostly “just worked”.

When Unity was announced a couple of years ago, I was more than willing to give Canonical the benefit of the doubt. Being a big believer in the value of good UX in the context of my own work projects, it seemed to me that professionals could surely improve upon the existing paradigm, which was mostly an accumulation of legacy skeuomorphs left over from the initial mouse and window scheme. I had already incorporated search into my normal work flow by using “Gnome Do”, so a desktop designed around search seemed like a logical step.

When the first beta came out, the reaction from geek circles was largely negative. The bulk of users were simply reluctant to embrace change. Some of the feedback was legitimate constructive criticism, though. Making a single UI usable on touch screens and desktops leaves both sub-optimal. Search results were quickly turned into obnoxious and slow pseudo-advertisements. Multi-monitor support has was knocked back five years.

But usability sessions showed that Unity was in fact easier to use for novice users. First time users were able to more quickly figure out basic tasks. Feedback from these users was largely positive. So I told myself to give it a solid six months before coming to a verdict. Inertia turned that timetable into two years, but now finally I have had enough.

Unity is just too slow. Bringing up the Unity dash has noticeable lag. Even switching between windows with ALT-TAB doesn’t feel smooth. I feel like I can see the window elements being drawn. I’m sure it’s something to do with my graphics card, but I don’t care. The lag has persisted over five successive releases, and several totally different pieces of hardware. My guess is that it’s a combination of having three monitors (and thus having many more pixels to push than your average user), refusing to use the proprietary drivers (which have their own usability issues) and my own neurosis. But it’s simply bad design to require good 3D video performance for basic UI interactions on a platform that has always been synonymous with poor graphics drivers.

Windowing in LXDE on the other hand has “just worked”. The very first time I booted into it, it picked up my three monitors correctly, with no configuration. ALT-TAB is blazing fast, if aesthetically work-a-day. “Gnome Do” is all I need to launch apps. The status bar is easily configurable and familiar.

Not everything is rosy. The ssh-agent integration is manual. It was a PITA to get my sound set up with a bluetooth headset. The lock screen is decidedly fugly. It seems that the power users were right, in a way. Those niceties have not made it back into the larger Linux desktop ecosystem. But at least I don’t feel like I’m operating my desktop over a 200ms VNC connection anymore.

Fuck you Canonical. You showed us how awesome a smooth, integrated Linux desktop could be. Then you went ahead and messed it up. Now the power user is back to having to fiddle again just to get a good experience. At least for me, you have managed to burn the goodwill you built in those first five years. I hope this mobile play is worth it.