[Unstable Update] February 2024 Edition

[philm]

@Delor3an91

Is it normal that I can’t find linux68-nvidia in the unstable repo?

please check the logs and provide patches: Releases · manjaro-kernels/linux68 · GitHub

[linux-aarhus]

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

[cscs]

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.

[linux-aarhus]

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

• [UNSTABLE] pacman keyring issues - keyring reset after reboot

[Slyfer1]

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?

[Mirdarthos]

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:

KaOS – A Lean KDE Distribution

Also, if you like living on the edge, see here:

[Plasma 6] RC2 testing

Plasma 6 Alpha Manjaro has - for a long time had a repo kde-unstable - this repo has lived in the shadows - used by developers. The repo is CI managed building daily [image] If you have the guts to participate in testing here is the recipe for switching your system to plasma 6. This is alpha - bumpy road ahead - steep cliffs to fall from … beware - there be If you are keen to test - please observe the following - it is alpha testing - the r…

[Slyfer1]

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

[Mirdarthos]

@Slyfer1

I’ll just wait it out then

The best strategy, in my opinion.

[Aragorn]

@Slyfer1

are there any specific plans as to when KDE Plasma 6 is coming to Manjaro

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

[Slyfer1]

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)

[Aragorn]

@Slyfer1

Actually I got confused with the dates and thought the Plasma 6 final release was today

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.

[Slyfer1]

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

[notageek]

Plasma 6 will be released in the end of February

https://community.kde.org/Schedules/Plasma_6

[Aragorn]

Valgrind missing strlen in ld-linuxx86_64.so.2

On Manjaro Unstable - valgrind does not work because strlen is missing in ld-linuxx86_64.so.2. Any advice would be helpful. TIA

[stasadev]

Edit: fixed in 1.46.0-2.

Do not upgrade NetworkManager:

extra/networkmanager  1.44.2-3 -> 1.46.0-1

No IPv4 via DHCP after updating to 1.46.0-1 (#2) · Issues · Arch Linux /...

If you’ve already upgraded and are stuck without internet, use the pacman cache to revert to the previous version or get a working version from ALA.

[robin0800]

Just checked and I have 1.46 and IPV4 is working

[koshikas]

i did try after restarting NetworkManager, router WIFI card, seems like the issue is limited to wired connections. i’m on IPv4 with v6 disabled, and had no issues connecting after router came online again.

log

Feb 24 19:37:33 koshika-inspiron-5520 NetworkManager[23649]: [1708783653.2596] device (wlp8s0): state change: config → ip-config (reason ‘none’, sys-iface-state: ‘managed’)
Feb 24 19:37:33 koshika-inspiron-5520 NetworkManager[23649]: [1708783653.2600] dhcp4 (wlp8s0): activation: beginning transaction (timeout in 45 seconds)
Feb 24 19:37:33 koshika-inspiron-5520 NetworkManager[23649]: [1708783653.2646] dhcp4 (wlp8s0): state changed no lease
Feb 24 19:37:33 koshika-inspiron-5520 wpa_supplicant[1038]: wlp8s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-53 noise=9999 txrate=6000
Feb 24 19:37:35 koshika-inspiron-5520 NetworkManager[23649]: [1708783655.2850] dhcp4 (wlp8s0): state changed new lease, address=192.168.1.4, acd pending
Feb 24 19:37:35 koshika-inspiron-5520 NetworkManager[23649]: [1708783655.4615] dhcp4 (wlp8s0): state changed new lease, address=192.168.1.4
Feb 24 19:37:35 koshika-inspiron-5520 NetworkManager[23649]: [1708783655.4623] policy: set ‘IKS_WIFI’ (wlp8s0) as default for IPv4 routing and DNS
Feb 24 19:37:35 koshika-inspiron-5520 avahi-daemon[855]: Joining mDNS multicast group on interface wlp8s0.IPv4 with address 192.168.1.4.
Feb 24 19:37:35 koshika-inspiron-5520 avahi-daemon[855]: New relevant interface wlp8s0.IPv4 for mDNS.
Feb 24 19:37:35 koshika-inspiron-5520 avahi-daemon[855]: Registering new address record for 192.168.1.4 on wlp8s0.IPv4.
Feb 24 19:37:35 koshika-inspiron-5520 NetworkManager[23649]: [1708783655.4779] device (wlp8s0): state change: ip-config → ip-check (reason ‘none’, sys-iface-state: ‘managed’)
Feb 24 19:37:35 koshika-inspiron-5520 systemd[1]: Starting Network Manager Script Dispatcher Service…
Feb 24 19:37:35 koshika-inspiron-5520 systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 24 19:37:35 koshika-inspiron-5520 NetworkManager[23649]: [1708783655.5051] device (wlp8s0): state change: ip-check → secondaries (reason ‘none’, sys-iface-state: ‘managed’)
Feb 24 19:37:35 koshika-inspiron-5520 NetworkManager[23649]: [1708783655.5054] device (wlp8s0): state change: secondaries → activated (reason ‘none’, sys-iface-state: ‘managed’)
Feb 24 19:37:35 koshika-inspiron-5520 NetworkManager[23649]: [1708783655.5059] manager: NetworkManager state is now CONNECTED_SITE
Feb 24 19:37:35 koshika-inspiron-5520 NetworkManager[23649]: [1708783655.5066] device (wlp8s0): Activation: successful, device activated.
Feb 24 19:37:35 koshika-inspiron-5520 NetworkManager[23649]: [1708783655.5072] manager: NetworkManager state is now CONNECTED_GLOBAL

connection

                Type: wlan
                Path: pci-0000:08:00.0
              Driver: iwlwifi
              Vendor: Intel Corporation
               Model: Centrino Wireless-N 2230 (BGN)
    Hardware Address: 
                 MTU: 1500 (min: 256, max: 2304)
               QDisc: mq
  Wi-Fi access point: IKS

Number of Queues (Tx/Rx): 4/1
Address: 192.168.1.4
Gateway: 192.168.1.1

[zbe]

@koshikas

the issue is limited to wired connections

Works fine here.

[Zesko]

@stasadev

Do not upgrade NetworkManager:

extra/networkmanager  1.44.2-3 -> 1.46.0-1

I have the same problem with networkmanager 1.46.0 because some network-packages are conflicting.

My networkmanager’s log tell me “dhcp4 ... acd pending”

I fixed it.

1. Edit /etc/NetworkManager/NetworkManager.conf to add:

[connection-dad-default]
ipv4.dad-timeout=0

That disables Duplicate Address Detection (DAD)

2. Restart: $ sudo systemctl restart networkmanager

3. Done

[Yochanan]

It should be fixed with networkmanager 1.46.0-2 coming along shortly.