Actually that issue was patched as soon as the patches were available:
2 Likes
Yes but now it is mainstream.
It had been a thing in Manjaro before it was mainlined, so if you’re worrying about BTRFS performance, now you shouldn’t.
Now last thing is Nvidia do fix D3 PCIE support for laptops so I can move to 5.10.x
I updated networmanager from the link first, rebooted and wifi is working correctly 
. So there is no need to check the second package. Unless you want to check it against networkmanager from Manjaro testing repo?
1 Like
Check if the 1.28.1-dev package creates an regression. See also the changes made to that package: 1.28.1dev+7+g3f5df3cdc6-1: FS#68891 Restore resolvconf · archlinux/svntogit-packages@71d5a9d · GitHub
Info
NM 1.28 changed the way detection of the default resolv.conf handler works; it now prefers using resolvconf if available. However, this does not work properly if systemd-resolvconf is installed, as NM
already configures systemd-resolved over D-Bus.So we get the choice between enabling resolvconf support (supporting openresolv but crashing and burning if systemd-resolvconf is installed) and disabling resolvconf support, which then allows other
network managers to use systemd-resolvconf to merge configuration for their interfaces with NetworkManager’s.Choose the latter and disable resolvconf support.
Should then I uninstall libnm-1.28.1dev+7+g3f5df3cdc6-1? I didn`t understando what to disable, I have systemd-resolvconf installed.
Yes, dev version breaks the Internet for me. As far I understand, the easy solution here would be to install openresolv (i’m not sure if it’s enough to install it and uninstall systemd-resolvconf, or maybe it needs some additional configuration). However, if that is intended, then openresolve should be a hard dependency, which is not, so in theory it should also work with systemd-resolvconf, but it doesn’t. This is clearly an unintended regression that will break a lot of user’s Internet and that is a very bad situation. This is clearly the case of breaking the user space, the biggest programmer’s sin (if this was intended) or a serious bug, no matter if the fix is easy,
From my, average user standpoint, what is the difference of using openresolv over systemd-resolvconf? Is there any advantage? If not, why should I switch? Or maybe use combo with different network manager? Again, pros and cons would be important here. If there are no clear perks, why change something that works?
I assume, this regression will be fixed and till then, we should stay on networkmanager 1.28.0-2? Am I right?
It turns out that pamac-gtk has issues updating some packages from AUR. It shows failed dependencies, although those are met, while it doesn’t show dependency that isn’t installed. When I used yay in terminal, all went fine, only pamac isn’t capable of doing it correctly.
I installed the Manjaro Ornara 21.0 GNOME preview.
The pamac-manager (10.0.4-2) is complaining and stuttering quite a lot:
>
> ** (pamac-manager:89599): WARNING **: 00:11:18.719: snap_plugin.vala:288: cannot search: got unexpected HTTP status code 403 via GET to "https://api.snapcraft.io/v2/snaps/find?architecture=amd64&confinement=strict%2Cclassic&fields=base%2Cconfinement%2Ccontact%2Cdescription%2Cdownload%2Clicense%2Cprices%2Cprivate%2Cpublisher%2Crevision%2Csummary%2Ctitle%2Ctype%2Cversion%2Cwebsite%2Cstore-url%2Cmedia%2Ccommon-ids%2Cchannel&q=bb"
>
> ** (pamac-manager:89599): WARNING **: 00:11:19.758: snap_plugin.vala:288: cannot search: got unexpected HTTP status code 403 via GET to "https://api.snapcraft.io/v2/snaps/find?architecture=amd64&confinement=strict%2Cclassic&fields=base%2Cconfinement%2Ccontact%2Cdescription%2Cdownload%2Clicense%2Cprices%2Cprivate%2Cpublisher%2Crevision%2Csummary%2Ctitle%2Ctype%2Cversion%2Cwebsite%2Cstore-url%2Cmedia%2Ccommon-ids%2Cchannel&q=bbs"
>
> ** (pamac-manager:89599): WARNING **: 00:11:20.447: snap_plugin.vala:288: cannot search: got unexpected HTTP status code 403 via GET to "https://api.snapcraft.io/v2/snaps/find?architecture=amd64&confinement=strict%2Cclassic&fields=base%2Cconfinement%2Ccontact%2Cdescription%2Cdownload%2Clicense%2Cprices%2Cprivate%2Cpublisher%2Crevision%2Csummary%2Ctitle%2Ctype%2Cversion%2Cwebsite%2Cstore-url%2Cmedia%2Ccommon-ids%2Cchannel&q=bbsw"
>
> ** (pamac-manager:89599): WARNING **: 00:11:22.333: snap_plugin.vala:288: cannot search: got unexpected HTTP status code 403 via GET to "https://api.snapcraft.io/v2/snaps/find?architecture=amd64&confinement=strict%2Cclassic&fields=base%2Cconfinement%2Ccontact%2Cdescription%2Cdownload%2Clicense%2Cprices%2Cprivate%2Cpublisher%2Crevision%2Csummary%2Ctitle%2Ctype%2Cversion%2Cwebsite%2Cstore-url%2Cmedia%2Ccommon-ids%2Cchannel&q=bbswi"
>
> ** (pamac-manager:89599): WARNING **: 00:11:22.886: snap_plugin.vala:288: cannot search: got unexpected HTTP status code 403 via GET to "https://api.snapcraft.io/v2/snaps/find?architecture=amd64&confinement=strict%2Cclassic&fields=base%2Cconfinement%2Ccontact%2Cdescription%2Cdownload%2Clicense%2Cprices%2Cprivate%2Cpublisher%2Crevision%2Csummary%2Ctitle%2Ctype%2Cversion%2Cwebsite%2Cstore-url%2Cmedia%2Ccommon-ids%2Cchannel&q=bbswit"
>
> ** (pamac-manager:89599): WARNING **: 00:13:24.158: snap_plugin.vala:288: cannot search: got unexpected HTTP status code 403 via GET to "https://api.snapcraft.io/v2/snaps/find?architecture=amd64&confinement=strict%2Cclassic&fields=base%2Cconfinement%2Ccontact%2Cdescription%2Cdownload%2Clicense%2Cprices%2Cprivate%2Cpublisher%2Crevision%2Csummary%2Ctitle%2Ctype%2Cversion%2Cwebsite%2Cstore-url%2Cmedia%2Ccommon-ids%2Cchannel&q=bbswitch+d"
>
> ** (pamac-manager:89599): WARNING **: 00:13:25.070: snap_plugin.vala:288: cannot search: got unexpected HTTP status code 403 via GET to "https://api.snapcraft.io/v2/snaps/find?architecture=amd64&confinement=strict%2Cclassic&fields=base%2Cconfinement%2Ccontact%2Cdescription%2Cdownload%2Clicense%2Cprices%2Cprivate%2Cpublisher%2Crevision%2Csummary%2Ctitle%2Ctype%2Cversion%2Cwebsite%2Cstore-url%2Cmedia%2Ccommon-ids%2Cchannel&q=bbswitch+dkm"
>
> ** (pamac-manager:89599): WARNING **: 00:13:25.648: snap_plugin.vala:288: cannot search: got unexpected HTTP status code 403 via GET to "https://api.snapcraft.io/v2/snaps/find?architecture=amd64&confinement=strict%2Cclassic&fields=base%2Cconfinement%2Ccontact%2Cdescription%2Cdownload%2Clicense%2Cprices%2Cprivate%2Cpublisher%2Crevision%2Csummary%2Ctitle%2Ctype%2Cversion%2Cwebsite%2Cstore-url%2Cmedia%2Ccommon-ids%2Cchannel&q=bbswitch+dkms"
>
> ** (pamac-manager:89599): CRITICAL **: 00:15:42.422: pamac_database_custom_db_search: assertion 'needles != NULL' failed
>
> ** (pamac-manager:89599): CRITICAL **: 00:15:42.422: pamac_database_custom_db_search: assertion 'needles != NULL' failed
>
> ** (pamac-manager:89599): CRITICAL **: 00:15:42.422: pamac_database_custom_db_search: assertion 'needles != NULL' failed
>
> ** (pamac-manager:89599): CRITICAL **: 00:15:42.422: pamac_database_custom_db_search: assertion 'needles != NULL' failed
>
> ** (pamac-manager:89599): CRITICAL **: 00:15:42.422: pamac_database_custom_db_search: assertion 'needles != NULL' failed
>
> ** (pamac-manager:89599): WARNING **: 00:15:42.585: snap_plugin.vala:288: cannot search: got unexpected HTTP status code 403 via GET to "https://api.snapcraft.io/v2/snaps/find?architecture=amd64&confinement=strict%2Cclassic&fields=base%2Cconfinement%2Ccontact%2Cdescription%2Cdownload%2Clicense%2Cprices%2Cprivate%2Cpublisher%2Crevision%2Csummary%2Ctitle%2Ctype%2Cversion%2Cwebsite%2Cstore-url%2Cmedia%2Ccommon-ids%2Cchannel"@michaldybczak I’ve never had “systemd-resolvconf” installed on any of my systems (tho I use XFCE). Make sure no other package depends on it. If that’s the case, just uninstalling it should resolve the issue with no further intervention. I dont have openresolv either.
1 Like