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
Edit: fixed in 1.46.0-2.
Do not upgrade NetworkManager:
extra/networkmanager 1.44.2-3 -> 1.46.0-1
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.
2 Likes
Just checked and I have 1.46 and IPV4 is working
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
Works fine here.
1 Like
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.
- Edit
/etc/NetworkManager/NetworkManager.confto add:
[connection-dad-default]
ipv4.dad-timeout=0
That disables Duplicate Address Detection (DAD)
-
Restart:
$ sudo systemctl restart networkmanager -
Done
3 Likes
It should be fixed with networkmanager 1.46.0-2 coming along shortly.
1 Like
plasma 6 has hit arch-testing
3 Likes
Time to switch my branch to Testing or even Stable 
@openminded Yes, the only thing I miss with systemd-boot is timeshift or snapper if these tools would work with it I would switch to it. But unfortunately that’s not the case.
In what way couldn’t you use either of them with sd-boot?
I think they are not as tightly integrated as they are with grub.
He means that grub uses grub-btrfs to support booting off any snapshot from Grub menu.
AFAIK, there is a trick for systemd-boot that allows booting off snapshot when requiring a large ESP size and writing your own tool, but it is complicated.
I use limine bootloader which does the same.
Hi, I searched the forum but I didn’t find answers to this question: why manjaro we are with mesa 23.3.x while on Arch there is already 24?
Also I wanted to report that with the kernel 6.8 opencl doesn’t work (Intel tigerlake integrated card). clinfo returns 0 platforms/devices. With 6.7 everything works fine.
Typically for mesa the x.0.x releases are development releases, so they are not considered stable.
It’s now March not February