Ubuntu 14.04 LTS AIO, o todos 'los Ubuntu' en uno
genial no sabes cuanto llevaba esperando algo asi… es decir bien se puede usar una version de ubuntu server y escribir sudo (escritorio de tu preferencia lubuntu, xubuntu), pero en pos de facilitar la tarea a nuevos usuarios y por demas hacerlo con la ...

Google News

Lubuntu 14.10仍将LXDE作为默认桌面环境
摘要: LXQt 又一款轻量级的桌面已经发布有一段时间了,这是LXDE 的一个新项目,LXDE 是基于GTK+2 的桌面环境,而LXQt 不是基于GTK+3 的桌面环境,而是基于QT5。因为还有一些工作需要优化,Lubuntu 14.10 仍然将LXDE .

und weitere »


Abschied von Windows Und dann tanzen die Pinguine
Scheffler hat mir Lubuntu auf einen USB-Stick gezogen, ein Ubuntu-Derivat, das auch auf schwächerer Hardware gut läuft. Damit kann er mir in einer Live-Demonstration an meinem eigenen Computer zeigen, wie ich mit dem Betriebssystem arbeiten könnte.

Google News


Microsoft Working on a New Windows 365 - Windows 9 Spotted with Mobile and ...
Of the desktop environments to choose from, there is GNOME 3.x (Ubuntu GNOME), KDE (Kubuntu), Unity (Ubuntu), Xfce (Xubuntu), and Lxde (Lubuntu). I quite like the first three as they are modern desktop interfaces. KDE specializes in giving you complete ...

und weitere »Google News

Listen up, XP users: Stuff's about to get real
If your computer meets the minimum requirements, update your Flash player and Adobe acrobat. Most computer that came with XP won't have the necessary chip speed to accomplish the last two things mentioned . You could also install Unbuntu or Lubuntu ...

und weitere »

After the initial release of LXQt, I found that there is a FAQ. How’s the memory usage? Will it become a bloated memory hog because of Qt? Here are some numbers for you.
My test environment is the latest Debian stable installed in VirtualBox with 512 MB of RAM and 1 CPU core assigned. After cold boot, the memory usage is as follows.

  • Plain Openbox only: 58 MB
  • XFCE: 89 MB (with default configuration of Debian. This value will increase after xfce is ported to gtk+ 3)
  • LXDE (gtk+ 2 version): 78 MB (add 20 MB to openbox)
  • LXQt: 95 MB (add 37 MB to openbox, still has some room for optimization)

The screen resolution is 1280 x 1024. So a wallpaper roughly used 1280x1024x4 bytes = 5MB of RAM. If you don’t set a wallpaper, this number can be lower. Besides, this is a virtual machine so some special modules for vbox are loaded. I turned off printer service and network-manager applet since they’re not used.

Yes, the memory usage slightly increased, but the difference is really negligible. Moreover, LXQt has more features, such as a better program launcher and new power management stuff.

Apparently the gtk+ 2 version uses less memory, but we cannot use gtk+ 2 forever. It’s not a secret that gtk+ 3 is not a memory saver. So, I’d say Qt is really not that bad.

Why yet another DE? Why can’t you do something more innovative? I think the answer for this FAQ is simple.

  • Nowadays everything goes mobile and touch, but we still saw unmet need for a classic desktop environment. Otherwise, Windows xp should have been killed years ago and Windows 8 should have high market share now.
  • In the history of free software, we see forking everyday, but (successful) merging rarely happened. We want to prove that it actually works. People can focus on what they can share with each other, not how they are different.

The following is my personal opinion (not on behalf of other LXQt developers)
Seriously, if a 17 MB memory usage increment can buy us faster development, more active developers [Figure 1], more contributors, and a healthier upstream community, that’s definitely worth it. When I say healthier, I mean those who do not hold a “Follow our way, or go away!” attitude. This is just as important as other technical considerations when you choose a toolkit.
Many people like to argue that Qt is not C++ since it requires a pre-processor. Did anyone tell you that Gtk+ actually uses a preprocessor, too? Check the manpage of “glib-genmarshal” please. Without this pre-processor to generate some code for you, it will be awfully difficult to add signals to your GObjects. That’s not C language, right?
It does not really matter for users what toolkit you’re using given the final result works. Let’s save some time not arguing which is better and focus on what we can do with them.

Figure 1. A screenshot from Google Trend


Recently, PC-BSD developers just reminded us that there is an unmet need for a Qt desktop for BSDs. So, here you go.

As stated earlier, we’re not really Linux-centric. We support Linux better simply because we’re Linux users. Now with some help from several FreeBSD users, things can be different. I installed FreeBSD 10 in Virtualbox last week. After reading some docs and fighting with it we fixed some broken makefiles. Now the major components should work as expected.
Of course, there are still some Linux things which do not work (yet).

  • lxqt-powermanagement: this requires upower
  • lxqt-policykit: I haven’t test if policykit works for FreeBSD
  • volume control applet: currently it only supports ALSA and PulseAudio. I’m going to implement OSS support for it.
  • removable device applet: this requires udisks
  • Reboot/Shutdown from the menu: We use logind/consolekit now. Any good alternative for BSD?

Other parts should just work. We hope that we can improve FreeBSD support more. Of course, help from the BSD community is needed.




The first release of LXQt is now available!

Downloads and links are hosted on lxqt.org. Mirrors of all the releases are also available on Github.  Issues and pull requests should be filed on the Github issue tracker.

The full release announcement is available on the mailing list.