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:
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 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.
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.
Its not documented anywhere, not in man or the conf file.
Eventually after installing one of the gtk versions I found it does have this option in GUI.
So theres that then.
Thanks for the friendly reply
That information was not present to me at the last update. However, I do not have the microcode line (ALL_microcode=(/boot/*-ucode.img) in /etc/mkinitcpio.d/linux67.preset) and the microcode is loaded just fine (can be observed by this command: journalctl -k --grep=microcode).
To get a common ground for everyone here from the discussion you shown before regarding this Forum entry: [Unstable Update] March 2024 Edition - #33 by koshikas
→ Before, it was discussed in the Arch-Forum:
It rather seemed to be a misplacement of the GRUB_EARLY_INITRD_LINUX_STOCK="" -line. As you see in the posts before, it was at an earlier state called. I would assume(!) that the early position overwrote a latter one, which lead to issues.
Also, it seems not to be necessary, as shown by this discussion of this merge request, which was discussed in the unstable forum: