Did a simple: 'sudo pacman -Syu
And now i’ve got kernelpanic after reboot.
Happy days 
I’ve got no clue what you’re exactly doing there with copying a file and editing it but I narrowed the problem down on my side by disabling all GNOME extensions and then enabling them one at a time.
FWIW, it seems that Dash to Dock is causing gnome-logs to coredump reliably.
Can anyone confirm? Are there any obvious errors to look out for in the journal? How would I know if it’s in fact DBus being the problem? The journal lists some dbus errors but I’m not sure they’re related to the problem. I’ve got:
… gnome-shell[1620]: Received error from D-Bus search provider org.gnome.Boxes.desktop: Gio.IOErrorEnum: Cannot invoke method; proxy is for the well-known name org.gnome.Boxes.SearchProvider without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
… gnome-shell[1620]: Received error from D-Bus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
… gnome-shell[1620]: Received error from D-Bus search provider org.gnome.Terminal.desktop: Gio.IOErrorEnum: Cannot invoke method; proxy is for the well-known name org.gnome.Terminal without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
but also a lot of these dash-to-dock errors:
… gnome-shell[1620]: JS ERROR: TypeError: this._source is null
setUpdating@file:///usr/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/appIconIndicators.js:1109:9
destroy@file:///usr/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/appIconIndicators.js:794:14
_decorateIcon/<@file:///usr/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/appIconsDecorator.js:55:23
callback@file:///usr/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/utils.js:199:17
clear@resource:///org/gnome/shell/ui/search.js:198:44
_clearDisplay/<@resource:///org/gnome/shell/ui/search.js:784:30
_clearDisplay@resource:///org/gnome/shell/ui/search.js:783:25
_reset@resource:///org/gnome/shell/ui/search.js:670:14
setTerms@resource:///org/gnome/shell/ui/search.js:735:18
_onTextChanged@resource:///org/gnome/shell/ui/searchController.js:248:29
reset@resource:///org/gnome/shell/ui/searchController.js:182:9
_onKeyPress@resource:///org/gnome/shell/ui/searchController.js:274:22
@resource:///org/gnome/shell/ui/init.js:21:20
Looks like it could not find root partition. Did you skip grub install in the last update notes? The one before this update.
I bet it is something as simple as that.
Well, i installed manjaro from the 25.0.0 iso. So this is the first update for my system since os install.
Luckely btrfs timeshift made a snapshot before the update. 
.
Me too and all went well; logged out, TTY, updated mirrors and then the system!
Updated 2 machines via pacman, no issues that I can see on either so far.
1 Like
After further verification, I found that the problem with playback in mpv is separate from the problem with audio capture in ffmpeg.
The problem with mpv playback was caused by va-api, and by disabling va-api, I was able to playback without any problem.
The segfault in libc.so.6 by ffmpeg is also caused by access to va-api.
In contrast, the audio capture problem does not produce any error messages, so I can’t see the cause at all.
Unlike the va-api problem, the miko problem occurs on a specific PC and cannot be captured by either the microphone input or by monitor.
I can make WebRTC calls with no problem, and I can record with Audacity, but the behavior is unstable, freezing when accessing the audio source.
I also encountered the issue with the update window just closing. I then had black screens and had to do a hard shutdown. Now I have a broken system and no clue what to do 
I created a support post here with some more details, would appreciate some help if anybody has any ideas.
With this update, I encountered an issue for the first time: The creation of thumbnails from .psd (photoshop) files is broken on desktop and dolphin as well.