A post was split to a new topic: After the update I have an additional Manjaro entry in GRUB menu
I lost keyboard configuration upon updating. Toolbar Icon was unresponsive, keyboard set to qwerty type keyboard - I use an azerty. makes writing this a game of guess-the-right-key, a bit - a lot - more time consuming than I would like.
I had this notification upon restart after updating
Fcitx should be launched by KWin under KDE Wayland in order to use Wayland input method frontend. This can improve the experience when using Fcitx on Wayland. To configure this, you need to go to âSystem Settingsâ â âVirtual keyboardâ and select âFcitx 5â from it. You may also need to disable tools that launches input method, such as imsettings on Fedora, or im-config on Debian/Ubuntu. For more details see Using Fcitx 5 on Wayland - Fcitx
went to select the required option, selected Fcitx 5 wayland launcher experimental, restarted and now the input method icon is responsive. I went to the configure option and was greeted by a Kdialog stating the folowing
Youâre currently running KDE, but KCModule for fcitx couldnât be found. The package name of this KCModule is usually kcm-fcitx5, kde-config-fcitx5, or fcitx5-configtool. Now it will open the configuration directory.
Not sure on how to best proceed
1 Like
I have one XFCE install. No issues.
Then on my KDE Plasma one: failed retrieving file 'qt6-base-6.8.2-2-x86_64.pkg.tar.zst' tried a few different mirrors, but maybe itâs just a question of waiting for them to get updated.
(I have checked, for example, mirror.futureweb.be/manjaro, which is fully synced, but also doesnât seem to have it)
Iâm having a problem with my keyboard, Iâm using KDE
After every reboot, in System Setting, the installed keyboard layout has reset to English (US)
This seems to cause any entry of my password to fail EXCEPT when I log in
When i removed the us layout and added only UK layout, sudo etc worked, but as stated after boot the us layout was the only one present and sudo, pamac etc refuse the password
note the password does have some non standard characters like â!â and â#â and even entering the correct characters (shift-3 for â#â in us layout) the passworrd fails
1 Like
same here w/ XFCE - pamac-manager can not be started anymore
edit
strange, today pamac-manager is back without any update 
I will wait w/ my KDE updates due to issues reported on kwallet âŚ
The bug with the keyboards on kde was mentioned at least 9 days ago in the unstable and testing announcements. Just a food for thought how useful (or not) branches really are here.
The solution mentioned is to remove fctix, which is not essential anyway (i donât have it too).
1 Like
I went the opposite way - removing the legacy keyboard and using fctix virtual keyboards/input methods. This enables switching keyboard layouts per window instead of globally. But this may not be the solution for everyone because there may be applications that donât work with it.
4 posts were split to a new topic: Lost Bootentry in BIOS
6 posts were split to a new topic: Should I worry about this?
(pamac-manager:8394): Adwaita-WARNING **: 13:14:54.147: Using GtkSettings:gtk-application-prefer-dark-theme with Libadwa
ita is unsupported. Please use AdwStyleManager:color-scheme instead.
zsh: segmentation fault (core dumped) pamac-manager
Mod note: Iâve changed this to text for you. Please copy and paste text, rather than using images, which canât be easily referenced on the Forum.
I had to install same libraries to be able to get keyboard back to Finnish
1 Like
There are few things more annoying than a screenshot of text.
2 Likes
Another very seamless successful update on my 2 laptops and 1 desktop. Thank you Manjaro team! You are very appreciated!
1 Like
No issues. Everything went smooth. Manjaro always goes smooth. 
1 Like
Ok, so I tried Fcitx5 again and this time I ran fcitx-diagnose to see why Qt applications don´t seem to work:
## Xim:
1. `${XMODIFIERS}`:
**XMODIFIERS is not set**
**Please set environment variable XMODIFIERS to "@im=fcitx" using the tool your distribution provides or add `export XMODIFIERS=@im=fcitx` to your `~/.xprofile`.
2. XIM_SERVERS on root window:
Xim server name is the same with that set in the environment variable.
## Qt:
1. qt4 - `${QT4_IM_MODULE}`:
**Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add `export QT_IM_MODULE=fcitx` to your `~/.xprofile`.
2. qt5 - `${QT_IM_MODULE}`:
**Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add `export QT_IM_MODULE=fcitx` to your `~/.xprofile`.
3. qt6 - `${QT_IM_MODULE}`:
**Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add `export QT_IM_MODULE=fcitx` to your `~/.xprofile`.
Is there a tool that should be setting these variables or am I to set them manually in .xprofile?
EDIT: I solved it!! OMFG! If anyone needs to add any key overrides to their ~/.XCompose, make sure to start that file with include "%L" so it first loads the current keyboard layout and then adds your changes on top of that, otherwise it will start a new keyboard layout from scratch and ignore the system set keyboard layout.
This is how my ~./XCompose file looks now:
include "%L"
<dead_acute> <C> : "Ă" Ccedilla # LATIN CAPITAL LETTER C WITH CEDILLA
<dead_acute> <c> : "ç" ccedilla # LATIN SMALL LETTER C WITH CEDILLA
2 Likes
We need more info about the Pamac crashes. Which desktop environment is affected by it? Which exact version of Pamac is used.
2 Likes
There is no rule. I have two machines - Hyprland, almost identical configuration, both are full AMD devices, on PC pamac-manager starts without problems on laptop do not start (starts only if pamac-manager --updates). On both I have installed latest updates and:
libpamac 11.7.2-2.1
pamac-cli 11.7.3-1
pamac-gtk3 10.7.0-1
CLI works fine on both.
1 Like
Peculiar. I was hit by the very unwelcome US keyboard layout, but only the day after I did the upgrade and rebooted.
I seem to have managed to reconfigure it back to the proper layout, but time will tell.
Same for me. Keyboard is messed up / english now.
Is there a guide how to fix it_