Glad you got it working!
Using grub-customizer is a bit tricky though - many a system has been bricked by that tool.
Please read this:
2 Likes
I’m on a non-english setup and I’d like to verify:
Where in system settings can I find this button?
Never mind - I now know what you mean. I can conform this on Plasma 6, QT6.7, core & extra testing + unstable.
The button is anywhere you can download a customization. Try System Settings → Appearance & Styles → Colors & Themes, click on any of those pages and look in the upper right corner of the page. You should see “Install from File…” and “Get New…”.
Thanks! Found them. I can confirm this on Plasma 6, QT6.7, core & extra testing + unstable.
Ouch! Thankfully, I know what doing. The systems aren’t really “bricked.” The GRUB entry just gets removed or corrupted, similar to what happened when I installed the second EOS version. The partition and files are still intact. Advanced users know to grab a EOS live USB, then use it to chroot into the affected system, then reinstall/fix GRUB. I wouldn’t recommend that any inexperience user try to triple boot or modify GRUB in any way.
I’m wondering if this is an EndeavourOS/Arch related problem or a Plasma 6 RC1 related problem. Can you also confirm if the desktop cube is working on your system also? You have to turn it on in System Settings → Apps & Windows → Window Management → Desktop Effects, then search for “Cube,” then check the box next to Cube, then hit “Apply.” Afterwards, Meta+C should open the cube.
Confirmed: Not working.
Have now 4 virtual desktops.
Activated the cube effect.
Meta-C does nothing.
Edit: tested on Wayland and X11: both not showing the cube effect.
Desktop Cube Not Working For RC1:
https://bugs.kde.org/show_bug.cgi?id=479814
I’m also having an issue with the volume OSD not appearing in Wayland. A bug report for this was submitted back in November for EndeavourOS. I confirmed it on my end. Is anyone else having this issue?
Tested on Wayland and X11: volume OSD is working on both on my setup.
Darn! Why is mine not working? Wonder what I’m missing??
I noticed that a bug report was not submitted for the “Get New…” bug. I submitted one:
I am no expert, but I gather that things might be depending on graphics card; not sure if that can be the problem in this case, but I’m on Intel.
I’m on Intel also. There has to be a package missing. How did you install Plasma 6 RC1 on your system?
Added my system information to the report.
Thanks for submitting!
If you want to know the gory details you should read this thread from the top 
.
In short, in november 2023:
- installed Endeavour OS on a spare partition
- added: kde-unstable, later added core-testing and extra-testing
- ran “yay”
and away I went.
LOL, I actually skimmed over the close to 500 entries for this subject and missed that. I pretty much did the same, except I ran “yay -S plasma kf6.” I wonder what’s borked on my system? Maybe there’s something left over from your previous Plasma 6 install since you hopped on prior to RC1 and I hopped on after RC1 was released?
I’m not at all knowledgeable enough to even start guessing, I’m afraid. There are others involved in this thread who can much better advice you, I expect.
No worries. I was just thinking out loud. I kinda expect stuff like this to happen with testing software. Anyway, I’m still enjoying Plasma 6 RC1, even with the bugs. I just miss being able to use Bismuth for windows tiling, like I have on my main/5.27 build.