Greetings from KDE Linux

hello all today i switched out from Fedora Kinoite and choosed to test KDE Linux first time and took the leap of fate and went straight to Bare Metal and damn it is good, fast, snappy and even Hybrid optimus setup is working out of the box with Nvidia open drivers including cuda. Didint had to do any special tricks and hacks and it took totally like 30 Minutes to setup desktop and install all apps

had to limit screenshots to only one since new user limits

9 Likes

Sounds nice - slightly confusing.

Fedora Kinoite is the KDE Plasma spin of Silverblue - IMMUTABLE versions of Fedora, with a container-centric approach, so Iā€™d expect that to be slightly slower in the pursuit of stability.

So you didnā€™t switch to KDE or Plasma, but you switched to a distribution of which youā€™re unsureā€¦

Is that Neon perhaps?

OP is referring to KDE Linux - KDE Community Wiki :slight_smile:

3 Likes

Ah, the Arch based immutable KDE projectā€¦ thanks, I got it.

might be my language now days not so easy to read sometimes and even i am confused multiple times what i actually wrote later since English not main language and living Asia for years and originally Scandinavian everything gets mixed.

1 Like

KDE is the software project.
Plasma is the Desktopā€¦
Not at all - you were right to call it ā€˜KDE Plasmaā€™ - I hadnā€™t realised that this was the official Distribution nameā€¦

The combination doesnā€™t make it clear to anyone that itā€™s a separate distribution (because Neon is KDE Plasma)ā€¦

I think a name like ā€˜Plasma Ironcladā€™ or ā€™ KDE SolidStateā€™ or just ā€˜KDE Solidā€™ would have been more informative.

Naming stinks these days, all the good things are taken.
KaOS exists, so anything similar would be more confusing. KOs. OSk?

But KDE Linux or Gnome OS, while seemingly confusing, are pretty descriptive.

Plasma= the desktop
Linux= the OS

I personally think they should have kept the original name, Project Banana :crazy_face:

1 Like

i second this, for scale.

Yes, agree.

  • An issue seems to be that, an acceptable name in one human language is, unacceptable in another human language.
    Proposing a name which is acceptable for all the human beings on this planet is becoming an almost impossible task ā€¦ :imp:
3 Likes

I think everything about that disto is in the right direction in terms of its design goals. And I guess itā€™s probably also needed as well after the remarks on Neon at Akademy: ā€œitā€™s a thing, it does things.ā€ Historic words :]

I hope it wonā€™t be named banana though, or orange for that matter.

Man this so so awesome Community is really nice, I want to be more part of itā€¦

The KDE Linux is so good even ā€œpre alphaā€ that I am not switching anymore it has everything I wanted and it just works and I can make it even better reporting small bugs and issues

Thank you for creating this since arch base it Support all my hardware and has good drivers

XPS 15 with optimus hybrid Intel UHD RTX 3050 TI
i9-11900H 32GB ram Samsung 990 pro NVME 4K touch screen all works so much better and keeps getting better

2 Likes

Of course itā€™s good, fast and snappy, itā€™s based on Arch after all, what else would one expect? :sunglasses: :stuck_out_tongue_winking_eye:

1 Like

Hi After previous attempt to install and run KDE Linux that faild . I have finaly succeeded, the system run well.
But since it is my first immutable distro (apart from Android), I am still learning how to manage those system. On KDE Linux do you use it only with the core system and flatpak/Appimage or do you install other programs. and how. I know that you can use overlay with systemd-sysext and I have use it to compile neovim and install it to ~/kde, but it seems more for kde developpement normally. I would be very interested to know youre experience from an immutable distro user. Those have a lot of advantage and are presented as the future of linux distros but I still have difficulties to see how to manage them.

my approach is flatpak first then snap ( if no flatpak ) then distrobox ( distrobox-export ). Sometimes there is no flatpak app and i see since we have snap support why not use it and distrobox is for me mostly as Development containers where i store all dependencies and workflow stuff i need.

mostly there is no correct way on my opinion since it all depends on your use case and what is best for you

test and see and learn what seems to be best for you
just side note there is sometimes need to tweak permissions on flatpaks to achieve what you want for permission side

i can recommend to start as base setup where you have all apps as flatpaks and see if those are good and then start changing and tweaking if need to use distrobox-export side apps. It takes time to find the best balance on your work so be patient and experiment

Edit my list installed apps
Packages: 1033 (pacman), 47 (flatpak), 9 (snap)
first flatpak if app wont work and is broken etc i go snap and if that wont work i go distrobox

Thanks for the reply. So by using those you donā€™t use small tui tools like ranger, btop, ? or do you use distrobox-export, maybe? Distrobox need a lot of ressource, right?
I know I have to look into flatpak permissions, I didnā€™t need it for the one I was using before that (a few high level app like Gimp, Krita,ā€¦).

I think I havenā€™t need permissions changes to anything else except VScode fkatpak to get Dev containers extension work so I can connect it to distrobox containers straight using flatapak version on host and create wrapper using podman-host like small tweaking and at now I have just changed apps and approach how I use and do and what apps I goā€¦

Keep it simple as default as can use flatapaks and snaps and distrobox. No customizing and tweaking mostly

I have found a way to have my usual tool albeit in an unorthodox way.
I have reinstall and now it is almost running, fast and good. There is though one point I have error message with my locale that seems bad configured, I wonder if you add the same problem ? Since it is immutable the usual way to install locale and configure donā€™t apply. There is no /etc/locale.gen and for exemple

% localectl set-locale LANG=en_US.UTF-8
Failed to issue method call: Locale en_US.UTF-8 not installed, refusing.

and with locale

% locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

It is like locale or not installed

% ls -al /usr/share/X11/locale/
total 144
drwxr-xr-x 1 root root    54 Dec 18 03:58 C
-rw-r--r-- 1 root root 31977 Aug  4 11:43 compose.dir
drwxr-xr-x 1 root root    54 Dec 18 03:58 en_US.UTF-8
drwxr-xr-x 1 root root    54 Dec 18 03:58 iso8859-1
-rw-r--r-- 1 root root 76404 Aug  4 11:43 locale.alias
-rw-r--r-- 1 root root 35812 Aug  4 11:43 locale.dir

I install 2 times the first time I use a combination of en_US.UTF-8 and other in the installer and since I had this error I just reinstall all with en_US.UTF-8 thinking maybe the others where not installed.
what is your /etc/locale.conf and does locale commande produce errors?
If someone using KDE-Linux (or maybe with experience in other immutable distro) can enlight me it would be awesome because it is the only things preventing me from using it: Konsole produce error at startup and foot complain and refuse completely to start.

Use zsh it shows locale errors on bash and now zsh is default on new install on latest images

I already use zsh. The locale got fixed it seems. The system works great . I have found a way to have my cli tool and other programms not in flatpak (or better not in flatpak) by bootstraping pacman and the installed programms in a systemd-sysext extension (like ~/kde).
There is still something: I have tried distrobox (no previous experience with it), creating a simple debian container but I got an error about /etc/localtime did you have something like that?

Arch base? Will this distro take care of all the manual interventions you need to do on an Arch system?