I guess some extra modules are not build for RC kernels in general.
See:
1 Like
Kernel 6.8 hasn’t even been released yet so yes, I’d say it’s quite normal to not find something that can’t exist yet.
it is not uncommon for release candidate kernels to be missing kernel modules
To check for when kernel modules are available - packages.manjaro.org/?query=linux68
1 Like
That’s weird because I already installed an RC kernel and I was able to boot my system. Without NVIDIA drivers it’s impossible.
Wish You well
Ran a sync yesterday - and noted that pacman was updated - a bunch of Archlinux patches applied
source=(https://sources.archlinux.org/other/pacman/$pkgname-$pkgver.tar.xz{,.sig}
pacman-always-create-directories-from-debugedit.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/efd0c24c07b86be014a4edb5a8ece021b87e3900.patch
pacman-always-create-directories-from-debugedit-fixup.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/86981383a2f4380bda26311831be94cdc743649b.patch
pacman-fix-unique-source-paths.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/478af273dfe24ded197ec54ae977ddc3719d74a0.patch
pacman-strip-include-o-files-similar-to-kernel-modules.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/de11824527ec4e2561e161ac40a5714ec943543c.patch
pacman-fix-compatibility-with-bash-5.2-patsub_replacement.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/0e938f188692c710be36f9dd9ea7b94381aed1b4.patch
pacman-fix-order-of-fakechroot-fakeroot-nesting.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/05f283b5ad8f5b8f995076e93a27c8772076f872.patch
pacman-change-default-checksum-from-md5-to-sha256.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/aa3a1bc3b50d797fb75278f79a83cd7dde50c66e.patch
pacman-sort-debuginfod-repro.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/843bf21e794c79c5b3bcf8a57e45ef9c62312fee.patch
pacman-split-off-strip-debug.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/7a4fff3310ba2eadd3d5428cbb92e58eb2ee853b.patch
pacman-ignore-a-files.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/00d2b1f90261bf77eaaf262d2504af016562f2ac.patch
pacman-early-err-git.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/3aa096a74f717d31650e0eb3cf34e9a5ebadc313.patch
pacman-fix-gnupg-binary-data.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/86ec26b2d33372a4b3bda48f22c4a9f226c3ccce.patch
pacman-fix-gnupg-newsig-check.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/16a064701a30d7e1175e1185cc6da44238302fab.patch
pacman-check-pipes-gnupg.patch::https://gitlab.archlinux.org/pacman/pacman/-/commit/f8c2e59ec57c86827b1f1b1c2f6760dc3e59fe40.patch
pacman.conf
makepkg.conf
pacman-sync-first-option.patch)
This sync removed my pacman keyring.
I noticed only this morning as I was installing python-opengl and my sublimetext repo threw key errors.
It turned out the entire pacman keyring was missing - the error message is keyring not writeable doh - it was gone.
pacman-key init
followed by
pacman-key --populate ...
What went wrong ?
@cscs that was really nuclear - but necessary - what did she say? nuke it from orbit is the only way to be sure …
I think this patch is part of the reason
Maybe it was the same thing that bit me shortly before?
I haven’t figured it out yet.
That patch only changed the default checksum from md5 to sha256 in the proto files:
I forgot about the keyring for sublimetext repo. So I downloaded the keyring and when executing pacman-key to add it
$ sudo pacman-key --add sublimehq-pub.gpg
==> ERROR: You do not have sufficient permissions to read the pacman keyring.
==> Use 'pacman-key --init' to correct the keyring permissions.
As of just now - running
sudo pacman -Syu
[...]
(23/23) checking keys in keyring [------------------------------------] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
Then
08:26:29 ○ [fh@tiger] ~
$ sudo pacman-key --init
[sudo] password for fh:
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
==> Generating pacman master key. This may take some time.
gpg: Generating pacman keyring master key...
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/2EDA04FF2292B86C1A9677A7CAD923AD7ADDB8CE.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
08:30:39 ○ [fh@tiger] ~
$ sudo pacman-key --add sublimehq-pub.gpg
==> Updating trust database...
gpg: no need for a trustdb check
08:31:12 ○ [fh@tiger] ~
$ sudo pacman-key --populate archlinux manjaro
==> Appending keys from archlinux.gpg...
==> Appending keys from manjaro.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signed 23 keys.
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
==> Disabling revoked keys in keyring...
-> Disabled 52 keys.
==> Updating trust database...
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 20 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 20 signed: 98 trust: 0-, 0q, 0n, 20m, 0f, 0u
gpg: Note: third-party key signatures using the SHA1 algorithm are rejected
gpg: (use option "--allow-weak-key-signatures" to override)
gpg: depth: 2 valid: 74 signed: 22 trust: 74-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2024-04-10
After this the sync worked as expected
signing the sublime text gpg key locally
08:33:27 ○ [fh@tiger] ~
$ sudo pacman-key --lsign-key 8a8f901a
-> Locally signed 1 keys.
==> Updating trust database...
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 21 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 21 signed: 98 trust: 1-, 0q, 0n, 20m, 0f, 0u
gpg: Note: third-party key signatures using the SHA1 algorithm are rejected
gpg: (use option "--allow-weak-key-signatures" to override)
gpg: depth: 2 valid: 74 signed: 22 trust: 74-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2024-04-10
Checking sublime text repo for update
$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
sublime-text 1841,0 B 5,04 KiB/s 00:00 [------------------------------------] 100%
:: Starting full system upgrade...
there is nothing to do
The file tree /etc/pacman.d
/etc/pacman.d
├── gnupg
│ ├── gpg-agent.conf
│ ├── gpg.conf
│ ├── openpgp-revocs.d
│ │ └── 2EDA04FF2292B86C1A9677A7CAD923AD7ADDB8CE.rev
│ ├── private-keys-v1.d
│ │ └── 4A30CAB81F184FDA1E2D21E6B38A137EBF2CEA7D.key
│ ├── pubring.gpg
│ ├── pubring.kbx
│ ├── pubring.kbx~
│ ├── S.dirmngr
│ ├── secring.gpg
│ ├── S.gpg-agent
│ ├── S.gpg-agent.browser
│ ├── S.gpg-agent.extra
│ ├── S.gpg-agent.ssh
│ ├── S.keyboxd
│ ├── tofu.db
│ └── trustdb.gpg
├── mesa-nonfree.pre.repo.conf
└── mirrorlist
4 directories, 18 files
A reboot invalidates the keyring
09:03:12 ○ [fh@tiger] ~
$ uptime
09:03:39 up 14 min, 1 user, load average: 0,48, 0,38, 0,20
09:03:39 ○ [fh@tiger] ~
$ sudo pacman -Syu
warning: Public keyring not found; have you run 'pacman-key --init'?
error: sublime-text: key "F57D4F59BD3DF454" is unknown
error: keyring is not writable
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
sublime-text 1841,0 B 5,18 KiB/s 00:00 [------------------------------------] 100%
error: sublime-text: key "F57D4F59BD3DF454" is unknown
error: keyring is not writable
error: failed to synchronize all databases (invalid or corrupted database (PGP signature))
The file tree /etc/pacman.d is now
09:04:55 ○ [fh@tiger] ~
$ tree /etc/pacman.d
/etc/pacman.d
├── gnupg
│ ├── pubring.kbx
│ ├── S.dirmngr
│ ├── S.gpg-agent
│ ├── S.gpg-agent.browser
│ ├── S.gpg-agent.extra
│ ├── S.gpg-agent.ssh
│ ├── S.keyboxd
│ └── trustdb.gpg
├── mesa-nonfree.pre.repo.conf
└── mirrorlist
2 directories, 10 files
That folder is not something I check on a regular base - but there is a lot of sockets now - I am not sure I have seen them before
Can confirm upon reboots I needs to do
sudo pacman-key --init
sudo pacman-key --populate archlinux manjaro
(more for the second one depending on your third party repos - should be anything you have installed as *-keyring at least)
And just that - then new installs work as expected (ex: sudo pacman -Syu cowsay).
I havent had the time to look at diffs or whatever to figure out why this is needed now though.
If you have keyring issues please use below thread to collect experience so we can - hopefully - find the cause as it seems upstream Arch Linux has implemented some changes we don’t fully understand the implications of
I apologize if this may seem like ETA begging or might be inappropriate, but are there any specific plans as to when KDE Plasma 6 is coming to Manjaro and/or unstable branch?
It’ll be ready when it’s ready. Not 1 second sooner, nor 1 second later. If you can’t wait, KaOS is already rolling with it:
Also, if you like living on the edge, see here:
1 Like
Thank you very much for that.
I’ve added the kde-unstable repo earlier, when Plasma 6 was in Beta, but came to find, that the packages from it are even behind the unstable branch of Manjaro and I didn’t get why that is.
I added it right now and the updateable packages are still behind their respective unstable branch apps on Manjaro. I don’t think I understand how this works haha. But it’s not so super important to me. I’ll just wait it out then 
The best strategy, in my opinion.
2 Likes
Ah, I see Phase 1 has arrived. 
Roadmap for the adoption of new software in Manjaro
Phase 1: Incessant and compelling user demand
Phase 2: User feedback
5 Likes
Good one 
Actually I got confused with the dates and thought the Plasma 6 final release was today I’d have probably received the same reply, but I’m a proud beggar, nothing can put me down! 
(Except maybe software poverty)
1 Like
It might very well be — I haven’t checked — but there is a distinct difference between the official release by KDE upstream and its adoption into Arch Unstable, and then it still has to percolate down through Arch Testing before it reaches Arch Stable, and thus by implication, Manjaro Unstable.
Yeah makes perfect sense. As I didn’t know how the chain of software for Manjaro works (Quite new to all of this or let’s say not very savvy) I thought a question might not harm But thanks for the clarification. As I said earlier I’ll just wait until it’s there 
Plasma 6 will be released in the end of February
3 Likes