sudo pacman -Syyu
[sudo] password for anthony:
:: Synchronizing package databases...
error: failed to update core (unable to lock database)
error: failed to update extra (unable to lock database)
error: failed to update community (unable to lock database)
error: failed to update multilib (unable to lock database)
error: failed to synchronize all databases
That means either something else is already using the Pacman database (like Pamac checking for updates) or you had a failed upgrade and the db.lck was not removed automatically.
Only run this command after trying to update again with the same result.
It worked well for me. I use gnome-keyring for unlocking Skype on startup, and the gnome-keyring issue someone mentioned in the previous thread didn’t happen to me. All was smooth, and I’m only posting this to prevent anyone from being deterred by a potential gnome-keyring issue. There was 1 pacnew file for makepkg and I merged its changes in with meld, keeping my personal change to make it use 3 threads maximum so I can use my computer while building.
Oh, that makes more sense. I thought you were trying to say, “Nah, if you merged makepkg.conf.pacnew, which has this line that I’m showing you, it’ll use more than 3 threads, so good luck thinking that’ll work!”. Now I get you. Thanks for explaining.
GDM no longer starts on it’s own. I need to press ctrl+alt+F2 to get to the terminal and then I can immediately switch back (w/o logging on the text login) and GDM will start normally. I was able to log in. This problem happens now on every boot of this install.
This is the first time in years I installed GNOME; used Manjaro from the iso. Today’s update was my first (large) update with it. Did not have this issue before. Basically I am saying this a fresh new GNOME 40 install + I am not familiar with new GNOME.
Has anybody experienced issues with cheese after the update? Video flickers just like if the app was working on a persistent burst mode or something …
Unfortunately, I’m not able to reproduce the issue anymore since I decided to roll back to my previous snapshot. There should be many journal entries related to cheese with a gstreamer error, if somebody is willing to reproduce it.
EDIT:
Just decided to step up and try the update again.
This is what I get so far whenever I run cheese:
(cheese:1901): cheese-WARNING **: 13:16:10.322: Internal GStreamer error: code not implemented. Please file a bug at https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/new.: ../gst-plugins-base/gst-libs/gst/video/gstvideofilter.c(296): gst_video_filter_transform (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/GstVideoConvert:vfbin-csp:
invalid video buffer received
Same thing happens if I switch to kernel 5.10.32.
If I test with another webcam enabled app such as Skype, the video output works fine.
Any ideas on how to proceed with this?
I know this issue is not a big deal but IMO, you don’t expect minor things like that to happen in a Stable Release.
EDIT 2:
Issue Resolved.
Downgraded pipewire and pipewire-media-session to version 0.3.25-1