“disable plymouth” 
Make a backup copy of the .conf file before merging changes from the .pacnew file
sudo cp /etc/mkinitcpio.conf /etc/mkinitcpio.conf.old
If manjaro-pacnew-checker is not working well, users should also be suggested to install and use meld (or kcompare for KDE) to merge the .pacnew file
meld "admin:///etc/mkinitcpio.conf.pacnew" "admin:///etc/mkinitcpio.conf"
Recent posts this year show some users did not merge /etc/pacman.conf.pacnew from last year (to remove the community repository)
There will always be new users arriving that do not know about managing .pacnew files
2 Likes
So reboot isn’t enabled right now:
0 – disable sysrq completely
1 – enable all functions of sysrq
>1 – bitmask of allowed sysrq functions (see below for detailed function
description):
2 = 0x2 – enable control of console logging level
4 = 0x4 – enable control of keyboard (SAK, unraw)
8 = 0x8 – enable debugging dumps of processes etc.
16 = 0x10 – enable sync command
32 = 0x20 – enable remount read-only
64 = 0x40 – enable signalling of processes (term, kill, oom-kill)
128 = 0x80 – allow reboot/poweroff
256 = 0x100 – allow nicing of all RT tasks
(from SysRq – The not so known key)
I think manjaro-pacnew-checker should be part of the default Manjaro installation.
Just like on Debian or Gentoo for example where you’re asked by default if you want to view and merge or keep the new one or the existing one.
Update itself went smoothly, but wasn’t able to install kernel 6.9.2 after the update:
(4/4) Updating Grub-Bootmenu
Fehler: Befehl konnte nicht korrekt ausgeführt werden
GRUB-Konfigurationsdatei wird erstellt …
cat: Schreibfehler: Auf dem Gerät ist kein Speicherplatz mehr verfügbar
Translation: write error due to no more empty space on device. On /boot there are ~130 of 512 MB free, however and I had actually recently deleted several old kernels.
The alternative or ‘original’ is pacdiff. Which can be used with any diff program.
DIFFPROG=meld pacdiff -s
Which is still preferred for a number of reasons. Including these from man
1. Temporary copies are made of the files to be edited with the owner set to the invoking user.
2. The editor specified by the policy is run to edit the temporary files. The sudoers policy uses the SUDO_EDITOR, VISUAL and EDITOR environment variables (in that order). If none of SUDO_EDITOR, VISUAL or EDITOR are set, the first program listed in the editor sudoers(5) option is used.
3. If they have been modified, the temporary files are copied back to their original location and the temporary versions are removed.
To help prevent the editing of unauthorized files, the following restrictions are enforced unless explicitly allowed by the security policy:
• Symbolic links may not be edited (version 1.8.15 and higher).
• Symbolic links along the path to be edited are not followed when the parent directory is writable by the invoking user unless that user is root (version 1.8.16 and higher).
• Files located in a directory that is writable by the invoking user may not be edited unless that user is root (version 1.8.16 and higher).
Users are never allowed to edit device special files.
If the specified file does not exist, it will be created. Unlike most commands run by sudo, the editor is run with the invoking user's environment unmodified. If the temporary file becomes empty after editing, the user will be prompted before it is installed. If, for some reason, sudo is unable to update a file with its edited version, the user will receive a warning and the edited copy will remain in a temporary file.
3 Likes
True Story, that’s why i wrote… better late than never. 
Thanks, went ahead and changed it to 1.
Note that it won’t be permanent unless you do
su
kernel.sysrq = 1 > /etc/sysctl.d/sysrq.conf
To enable it at each boot.
Finally switched away from nividia-390. Seeing great snappy swiftness in Wayland on my i3 
I encountered a message in pacman.log that I don’t think I have seen before. In this forum only mentioned in the [ARM not stable thread]:
WARNING: No module containing the symbol 'drm_privacy_screen_register' found in: 'drivers/platform’
EDIT: For some reason, I’m seeing the wrong cursor theme in SDDM although it is still
[Theme]
CursorTheme=breeze_cursors
in sddm.conf
Unfortunately resetting/deleting the files doesn’t fix the issue. I just edited them manually for my needs. Seems to be a real bug in systemsettings, it’s already on the corresponding KDE bug tracker.
The update broke two kde plasma widgets that are of minor importance to me. Both weather widget and KDE Connect widget fail to load with the same error:
FullRepresentation.qml:38:24: Cannot assign object of type "QQC2.Action" to property of type "Action_QMLTYPE_106*" as the former is neither the same as the latter nor a sub-class of it.
Google did not show anything, even not similar.
I suspect they’re not compatible with Plasma 6. It may be that the developers have updated them; try downloading them again to find out. Otherwise you’re stuck until (if) they get updated.
1 Like
Thank you for your hint. But they were working before with Plasma 6. Only the latest update broke them. Additionally these are Plasma standard widgets, that I didn’t download from somewhere.
Are you certain that it was not Plasma 5 the widgets were working on?
I switched to Plasma 6 with Stable Update 2024-05-13. This was when I first started using the weather widget successfully and KDE Connect widget was there without errors (but unused by myself)
Strange… I’m using the KDE Connect widget and it’s still working fine. Maybe remove, add and set up again? (Just a random thought)
Was my thought as well, but these are not normal widgets, they are contained in the plasma system tray widget. This I can remove and re-add, but no change. In system tray settings I can disable these widgets and can re-enable them, also no change.
I restarted plasmashell on console to get more info and got the full error message:
kf.plasma.quick: error when loading applet "org.kde.plasma.weather"
QList("file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/main.qml:452:25: Type FullRepresentation unavailable", "file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/FullRepresentation.qml:38:24: Cannot assign object of type \"QQC2.Action\" to property of type \"Action_QMLTYPE_90*\" as the former is neither the same as the latter nor a sub-class of it.")
"org.kde.plasma.weather" : Migrate settings to plasma XML config
The last line is interesting, is that a log entry that the system does some migration (thatz maybe fails) or is that a request to the user to do something (and if yes, what?)
Ah! I wonder if the weather applet is blocking further movement when it’s throwing that error. Perhaps disabling it might allow further progress so at least you get the KDE Connect widget? Pure speculation on my part though.
Random thought: disable everything, and turn them back on one at a time to see if it’s something specific or not…
Nice thought, but no, KDE Connect applet is broken itself. Similar error, different file.
kf.plasma.quick: error when loading applet "org.kde.kdeconnect" QList("file:///usr/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/main.qml:50:25: Type FullRepresentation unavailable", "file:///usr/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/FullRepresentation.qml:63:32: Cannot assign object of type \"Action\" to property of type \"Action_QMLTYPE_79*\" as the former is neither the same as the latter nor a sub-class of it.")
Thanks, but no, error seems very specific to (at least) these two plasmoids
Another try was to use this plasmoid as normal widget on desktop. Same error.
SOLVED
Solved by rm ~/.config/plasma-org.kde.plasma.desktop-appletsrc and starting all over with about everything… well…