And the Package Maintainer spake, saying, “Thou shalt not upgrade from pacman-mirrors 4.23.2-2 to 4.23.2-3. 4.23.2-2 shalt be the the version thou shalt keep, and the number of the version shall be 4.23.2-2. 4.23.2-4 shalt thou not upgrade to. 4.23.2-5 is right out.”
After switching to the unstable branch, updating everything from it and rebooting, Gnome shell crashed after a few minutes use.
Turning off all extensions, logging out and in and everything has been fine so far.
It is simple: Gnome 42 finally uses libadwaita, the only UI design officially supported. Let’s see what the wider user community comes up with to bring their beloved theming back. For developers it might be easier only to concentrate their UI design on Adwaita.
Trying to get there.
It’s a slow process though. And a hack.
Here’s what I have gotten to, it’s still not even alpha and full of inconsistencies, but it’s a start.
+1
Let Gnome be Gnome and see how it goes
Did you entirely remove the manjaro-gdm-theme package?
Why?
I had absolutely no problem with it and now the highlighted user in GDM is in blue, which is the worst highlight color you can possibly get (even worse with a dark background). And it has nothing to do with Manjaro colors.
Could you please put it back as an optional dependency or something (if it causes problems for others)?
If not, how can I change it? Otherwise I will need to get rid of GDM.
Yes.
It hasn’t been updated for GDM 42 and has been causing problems.
Not until we’re able to fix the issues with it. You’re free to keep it installed if you wish.
Just want to say that I’ve been using Matcha dark theme even for libawaita apps and it works flawlessly, the setting looks a bit weird but I prefer these colors to the default gnome.
After the most recent update for Bluegriffon in the Unstable repos it no longer launches, stating:
Segmentation fault (core dumped)
Downgrading the package doesn’t work as it throws the following error after making the necessary symlinks:
XPCOMGlueLoad error for file /usr/lib/bluegriffon/libxul.so:
/usr/lib/bluegriffon/libxul.so: undefined symbol: unorm2_normalizeSecondAndAppend_70
Couldn't load XPCOM.
I’ve swapped branches back to the stable branch and it’s working on there.
Following new version of rsync, Timeshift is not creating backups anymore.
Solution for now, downgrading to previous rsync version.
Related links:
Seems I haven’t had new snapshots since the 18th either 
huhti 23 16:00:01 jp-gentoo CROND[51637]: (root) CMD (timeshift --check --scripted)
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT ((process:51637): GLib-GIO-CRITICAL **: 16:00:01.755: g_file_get_path: assertion 'G_IS_FILE (file)' failed)
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT ()
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT (** (process:51637): CRITICAL **: 16:00:01.755: tee_jee_file_system_path_combine: assertion 'path1 != NULL' failed)
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT ()
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT (** (process:51637): CRITICAL **: 16:00:01.755: tee_jee_file_system_dir_exists: assertion 'dir_path != NULL' failed)
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT ()
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT (/dev/md0 is mounted at: /run/timeshift/backup, options: rw,relatime,stripe=512)
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT ()
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT (Daily snapshots are enabled)
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT (Last daily snapshot is more than 1 day old)
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT (------------------------------------------------------------------------------)
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT (Creating new snapshot...(RSYNC))
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT (Saving to device: /dev/md0, mounted at path: /run/timeshift/backup)
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT (Linking from snapshot: 2022-04-18_23-00-01)
huhti 23 16:00:01 jp-gentoo CROND[51636]: (root) CMDOUT (Synching files with rsync...)
huhti 23 16:00:07 jp-gentoo CROND[51636]: (root) CMDOUT ( 13.93% complete (00:00:06 remaining) 27.70% complete (00:00:02 remaining) 42.96% complete (00:00:02 remaining) 69.84% complete (00:00:01 remaining) 89.35% complete (00:00:00 remaining) 94.96% complete (00:00:00 remaining) E: rsync returned an error)
huhti 23 16:00:07 jp-gentoo CROND[51636]: (root) CMDOUT (E: Failed to create new snapshot)
huhti 23 16:00:07 jp-gentoo CROND[51636]: (root) CMDOUT (Failed to create snapshot)
huhti 23 16:00:07 jp-gentoo CROND[51636]: (root) CMDOUT (------------------------------------------------------------------------------)
huhti 23 16:00:07 jp-gentoo CROND[51636]: (root) CMDOUT (Removing snapshots (incomplete):)
huhti 23 16:00:07 jp-gentoo CROND[51636]: (root) CMDOUT (------------------------------------------------------------------------------)
huhti 23 16:00:07 jp-gentoo CROND[51636]: (root) CMDOUT (Removing '2022-04-23_16-00-01'...)
huhti 23 16:00:08 jp-gentoo rtkit-daemon[1237]: Supervising 10 threads of 8 processes of 1 users.
huhti 23 16:00:08 jp-gentoo rtkit-daemon[1237]: Supervising 10 threads of 8 processes of 1 users.
huhti 23 16:00:09 jp-gentoo CROND[51636]: (root) CMDOUT ( 59.78% complete (00:00:00 remaining) 94.96% complete (00:00:00 remaining) Removed '2022-04-23_16-00-01')
huhti 23 16:00:09 jp-gentoo CROND[51636]: (root) CMDOUT (------------------------------------------------------------------------------)
huhti 23 16:00:09 jp-gentoo crontab[51762]: (root) LIST (root)
huhti 23 16:00:09 jp-gentoo crontab[51763]: (root) LIST (root)
huhti 23 16:00:09 jp-gentoo CROND[51636]: (root) CMDEND (timeshift --check --scripted)
huhti 23 16:01:01 jp-gentoo CROND[51956]: (root) CMD (run-parts /etc/cron.hourly)
huhti 23 16:01:01 jp-gentoo CROND[51955]: (root) CMDEND (run-parts /etc/cron.hourly)
Manual snapshots are made, but don’t appear in the GUI, while scheduled ones error out.
Edit: CLI Timeshift doesn’t see the manual snapshot I just made…
Edit: Trying to create a new snapshot via CLI errors out, and removed the manual snapshot made via GUI 
May be:
using Kernel 5.17.4-1 sometimes I got while rebooting:
Failed to send Watchdog=1 message: Transport endpoint is not connected
Machine reboots after 15 Minutes - using Kernel 5.15.35-1 not affected…
I’m on Testing so maybe it is not relevant, but I only use the GUI and do manual snapshots, and it works no problem this way (RSYNC with EXT4, no BTRFS here).
Because Testing has an older version of rsync.
Edit: Version 3.2.4 has landed to Testing now as well.
Can’t find the answer to this issue:
[demo@manjaro etc]$ sudo pacman -Syu
[sudo] password for demo:
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing nvidia-utils (510.68.02-1) breaks dependency 'nvidia-utils=510.60.02' required by linux516-nvidia
[demo@manjaro etc]$
Remove linux516-nvidia and install nvidia-dkms. Either that or install a supported kernel like 5.17 stable or 5.15 LTS and remove the 5.16 kernel altogether from Manjaro Settings Manager. It’s been EOL for a couple weeks now.
Hi!
Please check that the
pacman -Si linux518 | grep 'Ver' 21:41:51
Version : 5.18rc3.220425.gaf2d861-1
has proper kernel version string.
By date it was issued (25-Apr) and its commit’s hash of af2d861 it looks like it should be named as rc4.
Thank you!