SoylentNews is people
SoylentNews
Despite the previous announcement at the Ubuntu Wiki, that said
Martin Pitt announces the date to switch Ubuntu Vivid to boot with systemd instead of upstart as Monday, March 9th. He says that the switch will affect the desktop, server, cloud, all flavors but not Ubuntu Touch, and that if there are too many regressions there is a simple upload to revert to upstart.
regarding Lubuntu, the Ubuntu Wiki now reports
LXQt is still in development, so Vivid Vervet [(*buntu 15.04, slated for release in April)] is another bug fix release. A late regression in the desktop installer for 32 bit means there is no Desktop installer for this milestone but it does not affect the alternate installer. Systemd is not the default init system.
LXQt is a light-ish desktop environment built with the Qt toolkit usually associated with KDE-compatible apps.
This announcement indicates that, for the time being, Lubuntu will be sticking with LXDE (Lightweight X11 Desktop Environment) built with the GTK+ toolkit usually associated with GNOME-compatible apps.
Upstart will remain the init system for Lubuntu for now.
(Score: 2, Interesting) by Anonymous Coward on Monday April 06 2015, @11:42PM
The choice to stay with LXDE makes sense to me, it has for quiet a while been my go to DE. PCmanfm is a good file manager and the whole of LXDE runs nicely on aging hardware. (set up a perfectly smooth system with debian 7 and LXDE on an Athlon64 3000+ with 512MiB DDR2) .
I have been playing with LXQt on my Arch box and it is just not quite there, I am liking how it's looking though but there is a shortage of Qt apps that don't pull in the whole of KDE, and some nice features are missing (auto hide panel).
That said it has lots of promise and i prefer Qt to gtkmm. I will argue the C is a bad language for GUI stuff as objects just make sense for a GUI. I can't wait for LXQt to really get to the the point where it's feature equivalent to LXDE, when that happens it will be my goto DE.
(Score: 2) by NCommander on Tuesday April 07 2015, @06:40AM
I won't be surprised if a lot of the decision to go to systemd deals with the fact that Unity still uses a large number of GNOME components, which in turn depend on systemd. Using upstart was reasonable as long as the vast majority of the stack didn't break w/o systemd, but without Debian making sure the core components are systemd-free, the delta between Debian and Ubuntu would drastically increase. LXDE, which, to my knowledge, does not ship with GNOME based components would not have this underlying issue.
Still always moving
(Score: 0) by Anonymous Coward on Tuesday April 07 2015, @10:45AM
Weird thing is that supposedly Canonical was poised to take over development of Consolekit, that used to do what Logind (the main link between Gnome and Systemd at this point) does now, but for some reason it never happened.
But then there is all kind of weird passive-aggressive stuff regarding the move from Consolekit to Logind. Not helping that Poettering was the de-facto maintainer of Consolekit towards the end.
What is really striking tough is that apparently the major reason for discontinuing Consolekit was that they could not get multi-seat to work to their satisfaction. And multi-seat basically means having multiple displays and input devices hooked up to a single computer, that is then logically bundled into a "seat". In essence it recreates terminals via different means. And they are trying to get it working "securely" while still allowing for hot-plugging of devices.
Their idea with Logind seems to be to use cgroups, via Systemd, to limit what device files a seat can see, never mind interact with.
All in all the whole thing is starting to look like netsec erotica...