These fcitx5 wiki pages might be helpful for those who are currently experiencing keyboard layout issues with the change from fcitx to fcitx5:
For Users
Note: “Fcitx 4” is the fcitx package in Manjaro
2 Likes
I went into the keyboard tab of systemsettings, where I found only the US keyboard showing (a bit of US-centricism here, methinks). Added the correct keyboard and made it default, then deleted the US one.
2 Likes
Added the correct keyboard and made it default, then deleted the US one.
I did the same but US keyboard was back after a reboot.
My update went alright, but ibus was introduced for some reason. I’ve been using fcitx5 for a long time so the fcitx change doesn’t affect me. I can remove ibus and libibus afterwards, as no other packages depend on them. It is just weird to see ibus is installed without any other packages relying on it.
OK, my system was OK after a reboot. I think the answer is from earlier posts recommending the installation of fcitx5-qt and fcitx5-configtool, which I’d done (but had forgotten when I replied to you).
Exactly the same happened as last time, with the same solution:
3 Likes
2 posts were merged into an existing topic: When will Plasma 6.3 be delivered?
A post was split to a new topic: After this update, I cannot switch the keyboard layout in Xfce
Install went flawless. Thank you all for the work!
A post was split to a new topic: Booting to a black screen on kernels 6.12.12-2 and 6.13.1-2
3 posts were split to a new topic: Update broke some functionality of moonlight-qt on wayland
Having pamac ui crash here as well.
Running KDE
libpamac 11.7.2-2.1
pamac-cli 11.7.3-1
pamac-gtk 11.7.2-2
As Tomek mentions it starts with pamac-manager --updates but when selecting “Browse” it crashes with a Segmentation fault (core dumped). As well as with pamac-manager --search= when hitting enter on package query.
Here is the log with an annotation
feb 17 21:26:26 Infinity xdg-desktop-portal-kde[1283]: xdp-kde-settings: Namespace "org.gnome.desktop.a11y.interface" is not supported
feb 17 21:26:26 Infinity kwin_wayland[1017]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x6333eb1abf80)
feb 17 21:26:26 Infinity kwin_wayland[1017]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x6333eb1abf80)
*moment when selecting Browse
feb 17 21:26:45 Infinity kernel: pamac-manager[30386]: segfault at 90 ip 0000765d614b0b6c sp 0000765d58b2db38 error 4 in libpamac.so.11.7[67b6c,765d6145f000+76000] likely on CPU 6 (core 6, socket 0)
feb 17 21:26:45 Infinity kernel: Code: 35 49 11 03 00 31 ff 48 89 e5 ff 15 ae a7 04 00 31 c0 5d c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 85 ff 74 1f 48 8b 07 <48> 8b 80 90 00 00 00 48 85 c0 74 08 ff e0 66 0f 1f 44 00 00 31 c0
feb 17 21:26:45 Infinity systemd-coredump[30387]: Process 30302 (pamac-manager) of user 1000 terminated abnormally with signal 11/SEGV, processing...
feb 17 21:26:45 Infinity systemd[1]: Started Process Core Dump (PID 30387/UID 0).
feb 17 21:26:46 Infinity (sd-parse-elf)[30391]: Could not parse number of program headers from core file: invalid `Elf' handle
feb 17 21:26:46 Infinity (sd-parse-elf)[30391]: Could not parse number of program headers from core file: invalid `Elf' handle
feb 17 21:26:46 Infinity systemd-coredump[30388]: [🡕] Process 30302 (pamac-manager) of user 1000 dumped core.
Module [dso] without build-id.
Module [dso]
Module [dso] without build-id.
Module [dso]
Stack trace of thread 30386:
#0 0x0000765d614b0b6c n/a (n/a + 0x0)
#1 0x0000765d6147f432 n/a (n/a + 0x0)
#2 0x0000765d61773be6 n/a (n/a + 0x0)
#3 0x0000765d612ec70a n/a (n/a + 0x0)
#4 0x0000765d61370aac n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64
feb 17 21:26:46 Infinity systemd[1]: systemd-coredump@7-30387-0.service: Deactivated successfully.
feb 17 21:26:46 Infinity systemd[1]: systemd-coredump@7-30387-0.service: Consumed 1.024s CPU time, 420.2M memory peak.
Pamac didn’t open for me as well, I briefly caught the error " Remote Peer Disconnected"
I followed the solution in the thread and replaced pamac-gtk with pamac-gtk3. Now pamac opens normally and also does not crash. Using KDE with latest LTS kernel.
2 Likes
(KDE) Infinite loading on the UEFI/manjaro splash screen after selecting kernel on boot with kernel 6.12 . Issue persisted through reboots.
Reverting to kernel 6.6 resolved the issue.
1 Like
I updated five systems yesterday.
So far only one issue has arisen, and only on one of the systems: the Pamac Manager crashed on launch on one of the five systems, saying “Remote Peer Disconnected”.
All five systems are running KDE with latest LTS kernel.
After running sudo pacman-mirrors --continent, pamac-manager was able to launch, but launching it from the command line still gets this error (but, again, it still launches):
(pamac-manager:12783): Gdk-CRITICAL **: 14:58:48.006: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
1 Like
2 posts were split to a new topic: Launching Spectacle (failed) Remote peer disconnected
Hi everyone!
Today update my work laptop and so far I had some trouble with file indexing in plasma. From dolphin I coudn’t find files by name but finding files by content seemed to work, which was really weird. At the same time kfind it worked fine for both cases.
Meanwhile, balooctl6 hanged or refuse to work. It wouldn’t give me status, and purge run (apparently) but when I wanted to enable it again, it fail.
So then, I went to:
System Settings → Search → File Search and disable indexing from there. When prompted, I choose the delete the current index. To be sure, run this from console:
sudo pkill baloo
rm -rf ~/.local/share/baloo
After that I enabled indexing again from settings and shutdown.
After start again seems to be working, so far.
A post was split to a new topic: Digikam is now throwing a Segfault on startup
Ran into this issue very soon after updating (KDE/Wayland + RX 6800 gpu). It doesn’t seem to cause any serious problem apart from the system log messages (Steam still works and so do my games, at least the few I’ve tried so far)
systemd-coredump[3306]: [🡕] Process 3304 (gldriverquery) of user 1000 dumped core.
According to that github issue this will be fixed in Steam soon™ (or may already be fixed on beta branch) but it does require SDL 3.2.4 which is currently only in Manjaro testing branch. Might be a good idea to push 3.2.4 to stable asap.
Btw it definitely is sdl2-compat causing this because out of interest and to satisfy my own curiosity (definitely not recommending that anyone else does this) I completely removed SDL3 (sdl3, sdl2-compat, lib32-sdl3, lib32-sdl2-compat packages) and installed the old sdl2 and lib32-sdl2 packages from /var/cache/pacman/pkg. Sure enough, no more core dump.
A post was merged into an existing topic: Launching Spectacle (failed) Remote peer disconnected