You are not logged in.
Pages: 1
With the announcement about 2.1 came the chance to re-read the Release Notes.
http://files.devuan.org/devuan_ascii/Release_notes.txt
In particular the part about Policykit and session management.
The desktop environments supported at install time are
XFCE, Cinnamon, KDE, LXQT, MATE along with the desktop managers
slim and lightdm, requiring either consolekit or elogind, but not both!
I found this interesting as on my ASCII desktop I use :-
lxdm
lxde
elogind
consolekit
this has been working smoothly for a long time. It does appear that both
consolekit and elogind are actually running. I think that lxdm wants elogind and
that lxde wants consolekit. Maybe this is why neither lxde nor lxdm are
recommended at installation.
The following are installed :-
libpolkit-backend-consolekit-1-0
libpolkit-gobject-consolekit-1-0
but not :-
libpolkit-backend-elogind-1-0
libpolkit-gobject-elogind-1-0
I also have a laptop running Beowulf which has installed :-
lxdm
lxqt
elogind
libpolkit-backend-elogind-1-0
libpolkit-gobject-elogind-1-0
Geoff
Offline
Yes, we removed lxde from the desktop choices in the installer because we couldn't get the 'kits to play nice. Please keep us informed, and maybe we can add lxde back into the installer for beowulf.
Offline
Thank you for that clarification.
I think that I would not be able to explain how I got to my current ASCII set-up! I see that on the desktop /lost+found and /usr date from Sep 2013, so assume that the set up originates from then. I believe that it pre-dates elogind and that I installed that when it first became available. I have at some point installed lxqt on the desktop, but am not currently using it.
I went with lxqt on Beowulf because it appeared that that was the way things were going and that lxde pulled in stuff that didn't sit too comfortably with everything else.
Geoff
Offline
Pages: 1