Notice: ConsoleKit2 will be replaced with elogind
by A. Wilcox
Hello all,
ConsoleKit2 is abandoned upstream[1] and has crashing bugs that are
difficult to debug[2]. elogind implements mostly the same features, and
even our most staunch bloat-opposers agree that replacing CK2 with
elogind makes sense, since at their core they are both fd.o projects
that implement similar APIs in similar ways.
This change will take affect with RC2, which will be released some time
within the next week.
FAQ:
"What will I need to do?"
-------------------------
If you use a display manager on boot up, you will need to run the
following commands as root:
# rc-update del consolekit
# rc-update add elogind default
To become root, open a Terminal window (such as Konsole or QTerminal)
and run "su", then enter your root / administrative passphrase.
"Does this mean we're giving in to systemd?"
--------------------------------------------
No. Even FreeBSD is working on an elogind-type system. All "modern"
desktop environments use this API. It is exposed over D-Bus. It does
not mean we are shipping systemd, nor that we plan to ship systemd.
"Will this affect my computer in any way?"
------------------------------------------
Possibly. Some hard-to-pin-down KDE bugs may be caused by our use of
CK2 instead of elogind. Similarly, XFCE's power management applet
crashing on start up may be fixed by this change. There should be no
*removal* of features, but there may be some addition.
"Can I keep using ConsoleKit?"
------------------------------
This is not supported. You may be able to do this by pinning CK2 before
upgrading to RC2 in your world file, as so:
# apk add consolekit2
# apk add '!elogind'
This will prevent you from upgrading KDE Plasma past 5.18.4.1, as our
5.18.5 packages will require elogind. Please remember that if you do
this, your system is not running a supported configuration.
*Do not request support if something breaks after doing this!*
"Where was this decision made? Why wasn't the community involved?"
-------------------------------------------------------------------
The community was involved. This decision was made in our IRC channel,
#Adelie, on irc.interlinked.me. Comments were heard from over a dozen
community members.
Best to you and yours,
--arw
[1]: Last commit was December 2017:
https://github.com/ConsoleKit2/ConsoleKit2/commits/master
[2]: https://github.com/ConsoleKit2/ConsoleKit2/issues/115
--
A. Wilcox (awilfox)
Project Lead, Adélie Linux
https://www.adelielinux.org
9 months, 2 weeks
Adelie Linux 1.0-RC1 32-Bit PPC - Problems with Apple iMac G4 Nividia GeForce 2 / NV11 GPU
by Jürgen Brunk
Hi Folks,
I've tested again Adelie Linux after some months of abstinence...
1. The choosen color set of light pink foreground on white background in
GRUB isn't eye candy at all, it's pure eye cancer as it's almost
unreadable. After Installation i've set this in /etc/default/grub:
GRUB_COLOR_NORMAL="white/black"
GRUB_COLOR_HIGHLIGHT="light-white/black"
May you could change this to a more eye friendly color combinatopn in
the final Installation Media also pls?
2. Missing some urgent Informations in the Wiki about eg. needed
Apple_Bootstrap Disk Labels and so on when installing on a new world
PPC. Lucky this Video helped me out:
https://www.youtube.com/watch?v=LLLfCgBu96M
3. Sadly the GeForce 2 / NV11 GPU in the iMac G4 PPC still won't work
with the current 5.4 Kernel and / or Xorg, using the Nouveau Driver.
Under OpenBSD, which i was giving a try, it was working, more or less,
with the older "nv" driver.
To boot at all from Installation Media, and later from Disk, i've to set
this for Grub as kernel parameters in /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="ro modprobe.blacklist=nvidiafb
modprobe.blacklist=nouveau modprobe.blacklist=rivafb"
Any Hints to get a working GUI with that GeForce 2 ?
Thanks and Best, J.
9 months, 4 weeks
no wireless connection after install
by wastelander1972＠gmail.com
Hi, I have successfully installed Adelie on my Lenovo laptop, but there is no active wireless interface. The rfkill command did list a Lenovo wlan unblocked interface, however dhcpcd wlan0 fail to detect it. Also, I have noticed that the whole /usr/lib/firmware folder was missing, so I tried to download and extract the linux-firmware package to that location. Unfortunately, this didn't fix the problem, it looks like the system is not able to load any firmware. My laptop ships with an Intel Dual Band Wireless-AC 3160 Controller, an Intel i5-4258U processor and a dual gfx card Radeon R5 M230/Intel Iris Graphics 5100. Thanks in advance.
10 months, 1 week
possible workaround for the consolekit session not starting
by wastelander1972＠gmail.com
In a previous thread I mentioned the strange issue on Plasma DE that prevented me to start NetworkManager and use the power options as user. So I tried to see whether my consolekit session was active or not, but % ck-list-sessions gave me no output at all! So I thought that a .xsession file was needed and edited it adding "exec ck-launch-session startplasma-x11". On reboot I was able to connect to my wireless network as user, and all the power options were back and working! Of course it's only a workaround, because I really don't know why sddm could not get consolekit to start normally, but at least my DE is usable now. Hope this helps.
10 months, 1 week
weird characters in terminal
by wastelander1972＠gmail.com
Running KDE DE and after entering the su command, I have an unreadable name as root user:
jordan on Adelie-BC80D0 ~ % su
Password:
%n on %B%F{white}%m%f%b %~ %B%F{green}%#%f%b apk update
I have the default regional settings enabled, and the encoding in konsole is set to UTF-8. Any help? Thanks.
10 months, 1 week
