The LXQt team is proud to announce the release of LXQt 0.13.0, the Lightweight Qt Desktop Environment.
The LXQt team is working hard towards LXQt 1.0.0. Want to help us? Found any bugs? Please file bug reports and pull requests on our GitHub tracker!
The release can be downloaded at downloads.lxqt.org or Github.
- All packages are ready for Qt 5.11.
- Out-of-source-builds are now mandatory.
- libfm-qt is made more self-sufficient and less dependent on libfm, resulting in better performance and more flexibility.
- qps and screengrab have been moved to the LXQt umbrella.
- Improved overall translations.
- Made menu-cached optional (default=off) in panel and runner to prevent memory leaks and to avoid problems when restarting or shutting down LXQt.
- Improved LXQtCompilerSettings.
- Our (upstream) configuration defaults were moved to `/usr/share/lxqt`, distribution’s overrides can be placed into `/etc/lxqt`
Notes For Packagers
- Please follow the build order.
- Please note that our repos are moved to GitHub/lxqt. Mentions and links should point at the new location.
- lxqt-build-tools >= 0.5.0 is mandatory and should be packaged directly after libqtxdg.
- All lxqt-* packages depend on liblxqt >= 0.9.0.
- libfm-qt soname bumped from libfm-qt3 to libfm-qt5.
- liblxqt now build-depend on libpolkit-qt5-1 directly.
- lxqt-admin now build-depend on libpolkit-qt5-1 directly.
- lximage-qt, lxqt-qtplugin pcmanfm-qt depend on libfm-qt >= 0.13.0.
- qterminal depends on qtermwidget >= 0.9.0.
Read the full release notes here
After a short discussion we decided to move our repositories from gh/lxde to https://github.com/lxqt before the upcoming release. Local repositories which was checked out before will work for a while, github automagically redirects to the new location – but it will be worth it to change the uris to the new location.
To do so please edit the .git/config like that
url = email@example.com:lxde/$foo
--> url = firstname.lastname@example.org:lxqt/$foo
git remote set-url origin email@example.com:lxqt/$foo
Hi all, there are some ongoing changes.
First of all we now have a blog – after talking with Medicalwei i copied the LXDE-Blog and removed all the things that are not related to LXQt – so we have a blog with a little bit history now.
Second – https://github.com/lxqt will become alive in the next weeks. I don’t know right now which approach is better – transfer our repos from https://github.com/lxde to https://github.com/lxqt now or directly after the upcoming release – we can discuss it in our shiny new forum. To populate the new LXQt home a little bit i transferred qps and screengrab to https://github.com/lxqt/
Third – https://forum.lxqt.org – it seems to be reliable and stable, so we can make it official right now or wait until the discours guys release the final 2.0.0. We can discuss that in the forum too.
That’s all for now.
It has always been rumored that Qt is bloated so programs written in Qt should be bloated. Some even argued that the LXDE developers made a wrong decision on the migration to LXQt.
Why not replace the assumptions with some experiments?
In fact, LXQt 0.11 even uses slightly less memory than XFCE (with gtk+ 2). After cold boot, LXQt uses 112 MB in the testing environment. Continue reading “Benchmark: Memory Usage: LXQt desktop environment vs XFCE”
There has long been needs for a simple Qt frontend for pulseaudio-based audio mixer. So I ported the gtk+ version pavucontrol program to Qt5 for use in LXQt. Continue reading “Qt5 port of Pulse Audio Volume Control (pavucontrol)”
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. Continue reading “Memory Usage of LXQt 0.9”
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. Continue reading “LXQt Performance Tips”
Although people often compare LXDE and the “so-called” Qt port, LXQt with each other, they are actually from different code bases.
The most parts of LXQt are actually built on top of razor-qt, a lightweight Qt-based DE with the same philosophy as LXDE. We reorganized the source code of razor-qt and removed unused pieces. Then we ported several LXDE components to Qt and also developed some new ones. Hence it’s more the merge of developers than the merge of the actual source code. That’s why they have slightly different feature sets. Without the work of razor-qt project, we can’t have LXQt now. Its developers deserved the credit. Since the story is too long for the tiny “About” dialog, I wrote the blog post here to thank their contributions.
Long live free software!
Yes, it’s about the gtk+ version LXDE, not LXQt.
Previously, razor-qt and lxde project merged and formed LXQt project, which just had a 0.8 release. Though the original plan was to migrate to Qt, this does not mean that LXDE is dropped. As many of the users have noted, many LXDE gtk+ components got updates recently. LXDE is still actively developed and maintained by the developers lead by Andrej N. Gritsenko (LStranger) and as long as gtk+ 2 is in use, I believe that they’ll keep working on it. We even got some patches for gtk+ 3 recently. Yes, gtk+ 3. This does not mean that LXDE is going to use gkt+ 3, but it’s a clear indicator that LXDE is not dead. If you’re not a fan of LXQt, don’t worry, you can still use LXDE. Also I want to say “thank you” again to LStranger who work really hard to keep LXDE so others can have some time to focus on LXQt while keeping our promise to the users.
About LXQt, the 0.8 version is quite stable and we have the required features, but of course it’s not good enough and have room for improvement. We’ll keep working on that, too. For the part I’m responsible for, the file manager, I’ll try to add the features that exist in the gtk+ versions but abscent in the Qt port. Also, I’m going to do more bechmarks for LXQt recently. Other developers are working on code cleanup and removing dependency on X11 so we can move to Wayland later.Both LXQt and LXDE are actively developed. Stay tunned! 🙂
The LXQt 0.8.0 release is now available. It brings with it full Qt 5 compatibility, two beautiful new themes and lots of new features, performance improvements and bugfixes.
Please see the full release announcement on our mailing list.
We are always looking for new contributors. If you are interested in joining us, please take a look at our Contributing guidelines.