qt6ct is for qt6 software theme, until now breeze didn’t have the qt6 theme and I used qt6ct to use a compatible kvantum theme. But I saw that in the arch repos there is breeze5 and breeze, so I solved my question
1 Like
Somehow I don’t get the newest updates. My system say’s there is nothing to do…
This is how my pacman.conf looks:
#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives
#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
#CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
#HookDir = /etc/pacman.d/hooks/
HoldPkg = pacman glibc
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta = 0.7
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
IgnorePkg =
#IgnorePkg = 4kstogram , 4ktokkit
#, linux-zen , linux-zen-headers
#, linux-tkg-pds , linux-tkg-pds-headers
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options
#UseSyslog
Color
ILoveCandy
#NoProgressBar
#CheckSpace
VerbosePkgLists
DisableDownloadTimeout
ParallelDownloads = 5
# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required
# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.
#
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#
# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
[endeavouros]
SigLevel = PackageRequired
Include = /etc/pacman.d/endeavouros-mirrorlist
[testing]
Include = /etc/pacman.d/mirrorlist
[core]
Include = /etc/pacman.d/mirrorlist
[extra]
Include = /etc/pacman.d/mirrorlist
# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.
[multilib-testing]
Include = /etc/pacman.d/mirrorlist
[multilib]
Include = /etc/pacman.d/mirrorlist
# [endeavouros]
# SigLevel = PackageRequired
# Include = /etc/pacman.d/endeavouros-mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
[chaotic-aur]
Include = /etc/pacman.d/chaotic-mirrorlist
Anyone can see what is wrong?
I also did do: yay -Syu.
1 Like
This has been replaced by [extra-testing] and [core-testing]
1 Like
How many bugs have to be squashed before it’s considered stable to try out? Is there still an option to use Xorg with KDE Plasma 6. I don’t use KDE Plams, but I just switched back from a Wayland session to Xorg session because just had one program I need not startup anymore and when playing games the screen would glitch out sometimes, which would make my eyes hurt. Probably an Nvidia thing but will try again in a few months.
Plasma 6 has been tested in this thread[1] from alpha to beta to rc1 and 2. Perhaps of interest.
As plasma 6 has now been released by KDE they consider it as stable.
1 Like
Yes
3 Likes
If you aren’t currently using plasma, I would wait until the first point release which should reduce the bugs you see.
4 Likes
I’d want to try it out in a vm, not as my primary DE. Was just asking since I’ve read a lot about first new KDE Plasma containing a lot of bugs.
I had incompatibility issues with some programs on Wayland. LanguageTool for Libreoffice didn’t work, Telegram lacked the support of system window frame as well. It was 3-4 months ago. Do you happen to know if the situation has changed?
I don’t use Telegram nor do i have the language tool since i use US english so i don’t know about that. For what i am using Wayland hasn’t caused me any grief. I’m also using on my Intel with Nvidia.
1 Like
I use GB English 
Fortunately, they aren’t going to drop X11 support for this release. I don’t doubt that KDE team will be able to provide a smooth Wayland experience, but some pieces of software I need haven’t had the native Wayland support so far.
1 Like
Unfortunately only in German:
2 Likes
I have a Pro account with LanguageTool and I use it with LibreOffice, and I have Telegram on my desktop. They have worked perfectly with KDE and Wayland for at least 8 or 9 months for me.
2 Likes
Nice. I should try it out again.
1 Like
11 Likes
I was just playing with it in a VM. Definitely has some minor bugs still.
1 Like
I’m sure major ones are well hidden…as always, with such a huge codebase 
I don’t no is it just me but plasma has been always troublesome with VM:s and live environments 
1 Like
Been running wayland for over a month now with zero issues.
2 Likes
Switched to Wayland a couple of months ago too after reading that it’s going to be the default. Been a smooth experience.
1 Like