You are not logged in.
Totally agree Oconcal, in regards to 32 bit systems. XWayland for me really hasnt helped much in general.
Last edited by crosscourt (Yesterday 20:32)
Q4OS KDE 5.xx Lenovo M73 Thinkcentre Tiny/Dell Inspiron 3670
Offline
It would be interesting to know what kernel that is running. Cauldron seems to be the equivalent of Debian Sid...
Kernel 6.12.33
Calm down, it's only ones and zeroes
Offline
I just installed Debian Trixie rc1. Same old Acer laptop.
Plasma 6.3.4. Kernel 6.12.30
Everything is running fine. I am experiencing none of the previous glitches I had with Q4OS Plasma Alpha.
Calm down, it's only ones and zeroes
Offline
So Q4OS have to miss something as it's is just Debian with extras. Would you be willing do some testing @Germ ?
Offline
Yes, I can do some testing.
Calm down, it's only ones and zeroes
Offline
So, please
- install Q4OS-6 Plasma with the full desktop, use the most recent iso q4os-6.0-x64-plasma.r6-testing-alpha.iso
- login to Plasma session
- untick checkbox on Welcome screen not to show on startup
- run terminal and get system up to date:
$ sudo apt update
$ sudo apt full-upgrade
- reboot
- perform some activity, same as for Debian, but avoid to run any of Q4OS utilities
Report back.
Offline
OK. Will do.
Calm down, it's only ones and zeroes
Offline
Going back to KDE neonuser, I have had various issues with it, being a mix of Ubuntu and Debian. When they migrated to 6, no-one could login. They fixed the issue with an update. Then came a major update to the OS - this ended up with a totally baulked system, moving from jammy repos to the 24.04 repos of Ubuntu. So downloaded the iteration after that. Then the next major update resulted in KDE disappearing up it's own repository only to be left with a full blown 24.04 Gnome desktop! Apparently this has been fixed with the next iteration but I prefer to stick with Q4OS, PCLOS Debian KDE Plasma and MX-Linux.
ASUS X470-PRO, AMD Ryzen 7 1700X 8 Core, 16 Gb RAM, Asus GT1030 2 Gb DDR-5 Q4OS 5.8 (Aquarius)
Offline
Im not a fanboy for Neon but Ive been using it since day one and havent had any of the issues you describe in your post @swarfendorfer437.
Neon has always had some issues, because its always using the latest iteration of KDE. My install was a fresh install of Neon with Plasma 6, and I also didnt have any login issues. Im still presently using it with no major issues. Typically I upgrade to the newer version but Ive been using KDE a really long time and Ive found that doing a fresh install has lead to way fewer problems.
Many people who had major issues were using the testing edition versus the Users Edition but as many people had issues, there were many who didnt, like myself. People got spoiled as KDE 5 had some issues early on but its been around a decade now, so its very stable. KDE 6 hasnt been around that long and its still going to take time to work things out.
Debian intentionally doesnt move that fast and many packages are somewhat outdated but overall its a lot more stable. Many want newer packages and that presents the chance for more issues depending on the situation.
I wouldnt use KDE Neon as a daily driver because its a bit cutting edge. I use the Users Edition just to test and see what Plasma 6 looks like, before it comes out in some other distros.
My favorite Debian distros are, Q4OS, MX Linux/antiX, and Netrunner 25. I no longer use PCLOS Debian KDE, too many issues for me. PCLOS Debian KDE doesnt auto detect printer at boot, has many issues with custom apps, unusual lack of some apps you see in other distros, other little niggles that just werent necessary. PCLOS Debian will also have significant issues using Sysvinit with Debian 13/Wayland in the next version of their distro.
Last edited by crosscourt (Today 00:31)
Q4OS KDE 5.xx Lenovo M73 Thinkcentre Tiny/Dell Inspiron 3670
Offline
- install Q4OS-6 Plasma with the full desktop, use the most recent iso q4os-6.0-x64-plasma.r6-testing-alpha.iso
- login to Plasma session
- untick checkbox on Welcome screen not to show on startup
Done
$ sudo apt update
Done. apt reports "All packages are up to date". And, I was not asked for my password.
- reboot
- perform some activity, same as for Debian, but avoid to run any of Q4OS utilities
Report back.
Will let you know how it goes.
Calm down, it's only ones and zeroes
Offline
I just installed Debian Trixie rc1. Same old Acer laptop.
Plasma 6.3.4. Kernel 6.12.30
Everything is running fine. I am experiencing none of the previous glitches I had with Q4OS Plasma Alpha.
In Kernel 6.12.25 they fixed all the drivers they broke and patched the buggy drivers they got from Intel.
Offline
In fact the 6.12.25 kernel caused issues with Nvidia drivers, AMD GPU configurations and many reported that the i915 Intel driver wasnt loading or in fact wasnt present(including other issues with Intel IGPs). The 6.12.30 kernel did fix some of the issues of previous 6.12.x kernels which was very welcome by many users(Germ was using the 6.12.30 kernel with Trixie with success). Users reported less Nvidia driver issues, i915 driver issues and better experience with AMD GPUS.
The 6.12.33 kernel(Germ in post #52 reported he is presently using the 6.12.33 kernel with Cauldron as they updated to both the .30 and .33 versions rather quickly,due to reported issues with 6.12.25) was released 6/10/2025(6.12 series will be supported thru 12/2026) and includes some additional minor fixes.
Linux kernel archives has details on the kernel as well as other kernels released in this series and in other series.
The issue with Q4OS alpha is the fact that its an alpha and will get a lot better by the time it releases.
Last edited by crosscourt (Today 05:03)
Q4OS KDE 5.xx Lenovo M73 Thinkcentre Tiny/Dell Inspiron 3670
Offline
I
The issue with Q4OS alpha is the fact that its an alpha and will get a lot better by the time it releases.
It just reminds me of the early 2000s when people were trying to write a better gnome. But the underlying os is total diy garbage that a high school level enthusiast threw it all together. If you really want my professional opinion.
Offline
Thanks @Germ
Terminal asks for sudo password for the first run definitely on the installed system. Afterwards it doesn't ask, however it has some expiration period to ask again. If you are performing within the live media, sudo users are not asked for password at all. We will check the alpha.
Offline