Core, installed KDE, how to automatically start it?

[Forum Admin anticapitalista]

Helpful

Up

0

::

Thanks for testing @olsztyn

I tried again and got much further with antiX-21-core-runit.
I found it easier to install xorg first and openbox, then install kde plasma within X and then use runit-service-manager (needs to be installed) before rebooting.
All seems to be working as it should with sddm (shudder) as login manager.

BTW – KDE users should be aware of telemetry built into it though I think Debian’s version removes it.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member puter]

Helpful

Up

0

::

Thanks Christophe. The steps you have taken are the same as what I tried except I hadn’t created a swap partition.
I had allocated 2GB RAM which I thought should be enough for a fresh install with KDE.

I tried again, this time with 3GB RAM and 2GB swap partition but I still get the same result.

Checked output of ‘top’ and the SDDM process is listed.

I also tried installing :

xfce4, stops booting at a blank screen with a flashing cursor.
lxde, stops booting at a blank screen with a flashing cursor.

I have a few different distro virtualboxes with the DEs that are provided, no problems there. I created an antix21-base virtualbox, it boots to GUI without issues.

Any suggested trouble shooting steps would be appreciated.

• This reply was modified 1 year, 1 month ago by puter.

[Member puter]

Helpful

Up

0

::

Tried installing xorg and openbox . . . boots to cli login.

[Moderator christophe]

Helpful

Up

0

::

Any suggested trouble shooting steps would be appreciated.

Did you partition the virtual hdd (& perhaps format it) before installation?

I got a repeated error stating “no space left on disk” or similar worded error, as the installation went along. Next attempt, I was careful to run fdisk & the formating utility.

“cfdisk” is the recommended partitioning tool, if you are not familiar with fdisk.

If you find that you need to format your root partition after creation, but before installation, the syntax is: mkfs.ext4 /dev/sda1.

confirmed antiX frugaler, since 2019

[Forum Admin anticapitalista]

Helpful

Up

0

::

Let us know your repos, just in case there is an issue there.

inxi -r

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member olsztyn]

Helpful

Up

0

::

anticapitalista wrote:

I found it easier to install xorg first and openbox, then install kde plasma within X and then use runit-service-manager (needs to be installed) before rebooting.
All seems to be working as it should with sddm (shudder) as login manager.

In my case installation of KDE Plasma was much simpler as I started from antiX Runit Full, not Core. No these additional steps were needed.
Although antiX KDE Plasma appears to work perfectly fine in my case, I fail to notice any particular incremental value in KDE Plasma vs. JWM or IceWM. Just useless (IMHO) fluff and no incremental substance in addition to what is already provided in antiX.
However for those users who for some reason like KDE Plasma DE better than JWM or IceWM or Fluxbox, this conversion of antiX default to KDE Plasma appears to be a quick way to have this KDE and not lose any of those great assets built into antiX, not found any place else… So I am still playing with this KDE antiX to have a complete picture…

• This reply was modified 1 year, 1 month ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Forum Admin anticapitalista]

Helpful

Up

0

::

puter wrote:

Tried installing xorg and openbox . . . boots to cli login.

You might need to install xserver-xorg-legacy and set it up.
You might want to install a login manager as well eg slimski

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member olsztyn]

Helpful

Up

0

::

Not strictly on topic being the issue of not booting directly to KDE, which I do not experience in my testing…
Having converted antiX 21 Runit to KDE Plasma through simple installation via Package installer I have played quite a bit with resulting antiX Runit KDE Plasma with the following results:
– KDE Plasma appears to work as designed on my antiX 21 Runit. No issues experienced in typical use. The typical KDE bunch of apps and functions added in result.
– KDE Plasma has significantly larger memory footprint than JWM, Fluxbox or IceWM. This is expected, being a full DE.
After some use of memory heavy apps memory footprint grows to about 730M on my test Thinkpad 410 and never seems to decrease to the original footprint of 420M. Not sure if due to cache or memory leak…
– Switching desktop from KDE Plasma to JWM through ‘Other Desktops -> JWM’ does not switch immediately but requires a Log-Off from KDE, subsequent to desktop switch, but running tasks appear to be correctly preserved in result of desktop switch. Switching desktop from JWM to KDE Plasma through ‘Other Desktops -> Plasma’ menu works correctly and preserving running tasks. So in general desktop switching does work correctly.
It seems KDE Plasma desktop could be even added to the standard set of antiX list of desktops for those users who like KDE for some reason. This feature appears to be a long hanging fruit to exploit and incorporate in antiX, if antiX strategy of expansion to a full DE is considered at all…
Just a thought…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Moderator Brian Masinick]

Helpful

Up

0

::

While I doubt that KDE will become an integral part of antiX packaging, it’s obvious from the many comments already expressed that it’s possible to add or create a KDE respin fairly easily.

In one of our past, ancient forums, I am pretty sure that I’ve outlined how I have created KDE builds from scratch *many years ago*. It wasn’t hard then and it isn’t hard now, but it does require an understanding of packages and their dependencies.

I may have written about my experiences in an old blog. Since others have already explained how to do it successfully, no need to repeat the obvious steps; others have done so in concise explanations.

--
Brian Masinick

[Member olsztyn]

Helpful

Up

0

::

Brian Masinick wrote:

While I doubt that KDE will become an integral part of antiX packaging, it’s obvious from the many comments already expressed that it’s possible to add or create a KDE respin fairly easily.

Indeed, it was a piece of cake for me to add Plasma. Any user interested in KDE can do it in a few minutes. In my case it was just an experiment for testing though. After playing a lot with KDE Plasma I have come to a personal conclusion that KDE does not bring any material advantage for me over current JWM. Just a useless bloat and visual fluff. So in my case it is a no-go. However I do respect other opinions to the contrary. What is pure bloat to me might be a treasure to someone else…
Thanks for your comment…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member puter]

Helpful

Up

0

::

Tried antix 19.5 x64 core, I have the same issue there too.

One thing I didn’t mention previously is that I need to run the installer in failsafe mode (on 19 and 20) as it wont run in the regular mode. That wouldn’t affect the installed OS though would it?

anticapitalista wrote:

Let us know your repos, just in case there is an issue there.


Repos:
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://la.mxrepo.com/antix/bullseye bullseye main nosystemd nonfree
Active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list
1: deb http://deb.debian.org/debian bullseye-backports main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.us.debian.org/debian/ bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.de.debian.org/debian/ bullseye main contrib non-free
2: deb http://security.debian.org/ bullseye-security main contrib non-free
No active apt repos in: /etc/apt/sources.list.d/various.list


anticapitalista wrote:

You might need to install xserver-xorg-legacy and set it up.
You might want to install a login manager as well eg slimski

I get an error regarding slimski failing when at cli login screen:


Starting slimski: slimski failed!

startpar: service(s) returned failure: slimski ... failed!


It’s not vital to have KDE as the DE, that is the one I’ve used the most in the past (was an older version) and most comfortable using, so that is the one I tried first. Some other DEs I’m not fond of using. At this point I’d be happy just to get any DE working.

[Member puter]

Helpful

Up

0

::

anticapitalista wrote:

You might need to install xserver-xorg-legacy and set it up.

I’ve installed it. How do I set this up?

• This reply was modified 1 year, 1 month ago by puter.

[Moderator Brian Masinick]

Helpful

Up

0

::

Do you have a “login manager” (sddm, kdm, LightDM, etc)? That gives you a login screen.
KDM would be a sensible choice with KDE, but you may use something else if you have a preference.
So if you have the basic KDE installed, next install KDM and see if it provides you with a login screen when you boot or reboot it (or even immediately, which would be great).

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

If KDE is causing you too many problems, I use Xfce with a lot of distributions, and it has meta packages for various configurations, or individual packages. If you are interested in that as another alternative, I can look up one or two metapackages that would provide you with an immediately usable Xfce setup.

I can also look at some KDE meta packages instead of just kde-standard, maybe it’s not quite enough by itself. Let me know what you’d prefer, and I’ll check out Debian-based packages for KDE and Xfce.

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

I’m wondering if the slimski problem is what is preventing you from reaching the login screen; I looked at kde packages; there isn’t a “kdm” any more, but the suggestions here were set up with sddm, so try this next:

sudo apt install –reinstall sddm

If sddm is already installed, it’ll reinstall it; if it’s not installed, it won’t hurt. I’m hoping that will allow you to select sddm as the login display manager, and if yes, KDE should be a choice for login. Try this and see if it helps.

--
Brian Masinick

[Author]

Posts