Install a nerd-ttf-fonts of your choice, set it in your profile of Konsole.
For more information about install-grub
see:
Install-grub: a new way to keep your EFI/MBR in-sync with grub package
and
[root tip] [How To] Primer on handling a grub package update
See:
Wiki post:
@notageek Veracrypt version 1.26.7 removed the option to run truecrypt mode.
Please see official changelog: https://launchpadlibrarian.net/689937121/README.TXT
- Remove TrueCrypt Mode support. Version 1.25.9 can be used to mount or convert TrueCrypt volumes.
@philm i still do not get one thing about the mkinit hook
- We add the hook to mkinitcpio.conf
- do we actively delete/comment out the line
ALL_microcode=(/boot/*-ucode.img)
in the presets? - do we do smth else? Like in grub?
Thanks I’ve reverted back to stable and deed the operation, now I will go back to testing…
Problems with auto-mount/VeraCrypt NTFS volumes using Kernel 6.8:
The kernel changed default ntfs
driver from FUSE one to ntfs3
.
These two are not fully compatible, mainly as far as mount options go. If you have custom mount options in the fstab
(or any other application, such as VeraCrypt) they need to be changed.
Symptoms:
Mount fails with: Device or resource busy
DMesg reports: Can't open blockdev
Solution:
Migrate your mount options. For me the changes were:
allow_other
→umask=000
default_permissions
→ [drop]user_id=1000
→uid=1000
group_id=1000
→gid=1000
https://bbs.archlinux.org/viewtopic.php?pid=2154769#p2154769
The advice appears to be: add to /etc/default/grub
GRUB_EARLY_INITRD_LINUX_STOCK=""
ktorrent has problems since KDE Gear 24.02.1. It will not run. A re-install did not change that.
qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "stateChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMState
qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "connectivityChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMConnectivityState
qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "deviceTypeChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMDeviceType
qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "meteredChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMMetered
kf.coreaddons: "Could not load plugin from /usr/lib/qt6/plugins/ktorrent_plugins/StatsPlugin.so: Cannot load library /usr/lib/qt6/plugins/ktorrent_plugins/StatsPlugin.so: (libKF6Plotting.so.6: cannot open shared object file: No such file or directory)"
QLayout: Attempting to add QLayout "" to kt::FileView "", which already has a layout
kf.coreaddons: "Could not load plugin from /usr/lib/qt6/plugins/ktorrent_plugins/StatsPlugin.so: Cannot load library /usr/lib/qt6/plugins/ktorrent_plugins/StatsPlugin.so: (libKF6Plotting.so.6: cannot open shared object file: No such file or directory)"
zsh: segmentation fault (core dumped) ktorrent
edit: installed the missing kplotting package. ktorrent still did not run. removed .config/ktorrentrc and now it does start. But only once!
Am I the only one having an error message when SDDM is being initialized?
The error message is: “Configuration file ‘’/var/lib/sddm/.config/sddm-greeter-qt6rc’’ not writable. Please contact your system administrator.”
Not a very warm welcome. I didn’t have this message at first when KDE6 was released a few days ago. Pretty curious that it comes up suddenly.
EDIT: Found this old thread. It doesn’t explain the difference between now vs last update, but at least it will most likely fix the issue, as indeed, somehow .config directory is owned by root and not sddm for some reasons. Configuration file "/var/lib/sddm/.config/sddm-greeterrc" not writable - #4 by cscs
EDIT 2: OK so I dunno what the f- I did, but I had a custom theme for SDDM installed somehow, a Windows 9x style theme called Reactionary. I have no clue where it comes from, I guess I was drunk when I did it or whatever. I uninstalled it and I click on “Apply Plasma settings on SDDM” too and it fixed it. Hum whatever.
@notageek No need to go back to stable next time. Do use downgrade
or manjaro-downgrade
.
pamac install manjaro-downgrade
manjaro-downgrade veracrypt
or
pamac install downgrade
sudo downgrade veracrypt
On stable it’s normally restricted as it’s only a temporary solution and needs DOWNGRADE_FROM_ALA=1
Please see wiki: Downgrading packages - Manjaro
I explain that in this video/post: [Testing Update] 2024-03-16 - Kernel, Calamares, Mesa, Plasma 6, KF 6, KDE Gear 24.04, LibreOffice - #87 by zar0nick
That is only the first step as we now know there are 3 steps (hooks, presets, grub)
hey thanks for the answer! Can you please elaborate further? I cannot follow you.
and
literally 5 posts above
This update borked my system. Im downloading plasma edition to reinstall it. Good thing I have a w10 partition too.
I had little space in /, not sure if that was related. But while updating the screen went black and that was it, then it didnt start
If you run out of space during upgrade then it will be interrupted.
If upgrade is interrupted for any reason then any number of problems could occur.
Lack of space in critical partitions can also cause problems, including causing software to fail.
CheckSpace
in pacman.conf
should mitigate the specific occurrence of ‘running out of space during upgrade’, though it cannot perform its check from within a chroot
environment.
Well, for pacman
anyways.
I do not know (or believe) pamac
is affected by that option or has its equivalent.
pamac-gtk
has this option in the GUI.
Pamac has this option too. And i think it is turned on by default.
And although this is a personal problem and does not belong here, here are the relevant links
There was a guide for moving /usr but i cannot find it.