Preparing the forthcoming Lubuntu 15.04 Vivid Vervet release, the Box theme has been updated and re-merged with Ubuntu's Light Theme to the use last GTK features, like the new HeaderBars used in Gnome native apps. Changes include a lot of bug fixes, adjustments in colour definitions, modified headerbars and toolbars, improved paddings and distances, improved 3rd party apps support (like Nautilus, Maps or Music), etc.

If you want to use Box theme in your distro just download it from the Artwork page.

Since the release of LXQt 0.9 several days ago, many people are curious about its memory usage since in the release announcement we mentioned the use of two libraries from KDE framework 5. Don’t worry! They are just “pure Qt libraries” without other KDE dependencies (Thank you KDE guys!). Good engineers always base their design desicions on careful analysis, experiments, and measurements, not politics. If a library works pretty well, it does not really matter where it comes from or it belongs to which camp. If it’s free software and it’s suitable for our need, I’d say “use it”. Here are some numbers of memory usage after cold boot.
Testing environment:

  • Debian testing (32 bit)
  • LXQt 0.9, Qt 5.3, and KF5 packages are taken from Siduction
  • Running in Virtualbox 4.3.20
  • RAM: 512 MB
  • CPU core: 1
  • Screen resolution: 1024×768
  • Measurement: Open xterm, and type `free -mh` (cache and buffer are excluded)

Memory usage after cold boot:

  • LXQt 0.9: 118 MiB
  • LXDE: 98 MiB
  • XFCE: 107 MiB
  • plain Openbox (without running any apps): 70 MiB

Well, for those who still remembered my previous report, the memory usage increased. But wait! All of the DEs, including Openbox, have the same degree of growth in memory usage. So it’s more possibly caused by the upgrade of the system itself. If you see the difference between plain openbox and LXQt, we only added 38 MiB (LXQt 0.8 added 37 MiB). Given that we migrated to Qt5 and added new features, both of which should normally increase memory usage, the current results are reasonable. Seriously, there are still room for more optimizations but we need some time to finish them.

LXQt aims to be a “modern” desktop with some “classic” designs which does not get in your way. We’re not going to clone KDE. Besides, don’t worry about resource usage. That’s the challange for developers and we’ll fight for it.


A eulogy to CrunchBang, the Linux distro that time passed by
... Debian, CrunchBang made more sense when it was harder to install lightweight desktop environments like LXDE on Debian, and when distros like the official Lubuntu derivative of Ubuntu—which also uses the lightweight LXDE desktop—weren't available.

und weitere »

The death of CrunchBang Linux
If I'm remembering correctly, at the time, there was no LXDE tasksel in Debian and certainly no Lubuntu around. CrunchBang filled a gap and that was nifty. So, what's changed? For anyone who has been involved with Linux for the past ten years or so, I ...



BQ Aquaris E4.5 Ubuntu Edition phone finally here, swaps apps for 'scopes'
I've been using Linux (Ubuntu, Lubuntu & Xubuntu) for many years now -- it makes a great platform, and it gets you out of Microsoft's "Patch of the Week Club". And (at least for now) it doesn't seem to be as big a target for malware as Windows is ...

und weitere »

Overstappen op Ubuntu
Computer Totaal
De alternatieve desktops zijn ook achteraf te installeren via de pakketten ubuntugnome-desktop, kubuntu-desktop, xubuntu-desktop en lubuntu-desktop. Andere smaken zijn Edubuntu (met een collectie educatieve software), Ubuntu Studio (om multimedia te ...

Google News

As we’re going to have a new release for LXQt 0.9, I’d like to provide some performance tips for users and packagers.

  1. Consider compiling lxqt-panel and lxqt-runner with menu-cache  support whenever possible:
    Menu-cache is a mechanism to cache the generated freedesktop.org application menu so we don’t need to parse hundreds of files everytime. Though you can compile lxqt-panel and lxqt-runner without it and things still work, these two components will generally load faster if you use menu-cache.
  2. Compile libfm with libexif:
    Libfm if the core library of PCManFM file manager. When compiled with libexif support, it can extract the thumbnails created by the cameras which are often embedded in jpeg files. So we can avoid loading the photo and generate the thumbnail ourselves. With libexif, loading folders with many photos will be faster.
  3. Try to “prelink” your system:
    When you launch a program, your system will load it alone with the libraries it requires. Then, dynamic linking will be performed to make these libraries work together. The process could take seconds in some cases and affect the speed of program startup. By using “prelink”, part of the linking/relocation process can be done once and cached; then in the future the dynamic linking becomes faster. It’s tool worth trying if your desktop takes quite a long time to login.
  4. Avoid GTK+ theme:
    Qt developers did a great job and provided a “GTK+” style for theming the Qt programs so they can look like GTK+/Gnome programs when running in Gnome. The magic behind this is simple. Your Qt style engine loads GTK+  2 and creates fake Gtk UI elements. Then, copy the images painted by GTK+ to your Qt widgets. By using this, you have both Qt and GTK+ 2 theme engines loaded for every Qt program. Not really a big deal since the operations are still fast enough, but if you don’t need a GTK+ theme, don’t use it. Try “fusion” for Qt5 or “Cleanlook” for Qt 4.
  5. Some notes about gvfs:
    Removing gvfs won’t make your file manager faster. PCManFM-Qt does not use it for most of the local file operations. So it’s safe to keep it around since it does not slow down things.  We used “gvfs” from Gnome internally for trash can, volume management, and mounting various network filesystems. Yes, the UI is in Qt and its core uses few Gnome stuff. Don’t hate gvfs just because there’s a “g” in its name. It’s a quite good VFS implementation which does not have Gnome dependencies. So don’t remove it just because its name contains a “g”. It provides you some good features, including mounting sftp filesystems or accessing Android mtp devices if you have proper plugins installed.
    Generally speaking, it might be a good idea for packagers to add “gvfs” to the dependencies or package suggestion list of pcmanfm-qt.
  6. Avoid Qt 5.4.0 if possible:
    We encountered several weird regression bugs of Qt 5.4 while debugging LXQt. It breaks drag and drop crossing different programs. With Qt 5.4, you cannot drag a file from my file manager to other programs, but it’s not my fault.  
    (The bug will be fixed in Qt 5.4.1, which is not yet released.)

We’re going to release LXQt 0.9 very soon!
Hope these tips help. Cheers!

Here we go again! It's that time of the year when Lubuntu asks the community to contribute an artistic touch to the distribution.

Please feel free to join us at Flickr and upload your favourite creation, that's one submission per user so make it count :).

Submissions are accepted until 1st March 23:59:59 UTC+01:00, and the polls will open shortly after that. The polls will be open until 9th March, and the top five wallpapers will be included by default in Lubuntu 15.04.

Please make sure to follow the rules, as failing to do so will get you disqualified.

Good luck to all contestants and please help us spread the word :).


Ubuntu 15.04: "Vivid Vervet" macht Fortschritte
Die Entwicklung für die nächste Generation der Linux-Distribution Ubuntu nimmt Fahrt auf. Seit wenigen Tagen gibt es nun eine zweite Alpha-Version von "Vivid Vervet", die wie gewohnt aber nur für die diversen Ubuntu-Derivate veröffentlicht wurde ...

Google News

Hello. This blog, as many others, is continuously receiving disgusting spam messages and troll comments. Of course all of them go directly to the trash can and marked as non-welcomed, so they no longer can annoy us. It's ok, I can deal with it with the help of Google.

But what I'm not going to tolerate is, under the appearance of nice readers and users, allow offensive comments or trolling about non-related things or articles on this blog. So please, you non-bots, humans that intentionally work for those companies colelcting data from blogs, public profiles and other stuff to feed the beast, you know you work sucks and I doubt about your human quality and integrity. You're banned.

Thanks everyone for your patience.