Gnome40…
I use these extensions:
Dash To Panel / Auto Activities / Hot Edge
Gives good workflow for me. AH and HE should be part of DtP - then no need for DtD.
Before KDE was blazing fast but now is extremely slow
for example…
It takes around 1 min to display the login screen
Launching Dolphin takes literally 45sec to launch the app…
systemd-analyze blame
doesnt show anything that delays the system…
According to my limited experience, network issues (slow connection) could be the culprit for such things. I’d check it if I were you.
1 Like
it seems that power management daemon is not starting , maybe is something related with upower…
New updates today
This is unstable - there are new updates every day…
1 Like
Even several times per day. 
I’m having some desktop file association issues with the latest thunar 4.16.7. Files on the desktop specifically seem to want to open with another thunar window rather than launching the associated app to play/view them…
manjaro-release is out off sync. It’s on 21.0.3
The latest mesawayland in gdm. Gnome/Wayland and any other wayland desktop/window manager have disappeared from gdm's menu.
See also:
EDIT: Mmh, downgrading mesa didn’t help, but restoring to a snapshot prior to the latest gnome-shell/mutter update does, but I have to login and -out of a xsession first in order to get the wayland options in gdm's menu.
sudo journalctl -p 3 -xb gives:
May 12 16:54:23 manjaro kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
May 12 16:54:24 manjaro gnome-session-binary[647]: Unrecoverable failure in required component org.gnome.Shell.desktop
May 12 16:54:59 manjaro kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
May 12 16:55:02 manjaro bluetoothd[694]: Failed to set mode: Blocked through rfkill (0x12)
May 12 16:58:08 manjaro kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
May 12 16:58:21 manjaro gdm-password][1389]: gkr-pam: unable to locate daemon control file
May 12 16:58:21 manjaro kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
May 12 16:58:41 manjaro systemd-coredump[2023]: Process 1499 (gnome-shell) of user 1000 dumped core.
EDIT2: The symptoms keep changing, that’s why I keep editing. Right now (full update) I’m back at having to switch between tty’s to get gdm to show up (still without wayland options) - same journalctl output as above.
inxi -Gbzy:
System:
Kernel: 5.10.36-2-MANJARO x86_64 bits: 64 Desktop: GNOME 40.1
Distro: Manjaro Linux
Machine:
Type: Laptop System: ASUSTeK product: X556UQK v: 1.0 serial: <filter>
Mobo: ASUSTeK model: X556UQK v: 1.0 serial: <filter>
UEFI: American Megatrends v: X556UQK.313 date: 03/13/2018
Battery:
ID-1: BAT0 charge: 27.8 Wh (86.6%) condition: 32.1/38.0 Wh (84.6%)
volts: 7.6 min: 7.6
CPU:
Info: Dual Core Intel Core i5-7200U [MT MCP] speed: 600 MHz
min/max: 400/3100 MHz
Graphics:
Device-1: Intel HD Graphics 620 driver: i915 v: kernel
Device-2: NVIDIA GM108M [GeForce 940MX] driver: nouveau v: kernel
Device-3: IMC Networks USB2.0 VGA UVC WebCam type: USB driver: uvcvideo
Display: wayland server: X.Org 1.21.1.1 driver: loaded: intel,nouveau
unloaded: modesetting resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 21.1.0
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
driver: ath10k_pci
Drives:
Local Storage: total: 1.03 TiB used: 24.39 GiB (2.3%)
Info:
Processes: 217 Uptime: 7m Memory: 11.59 GiB used: 2.25 GiB (19.4%)
Shell: Zsh inxi: 3.3.04no testing-announcement yet, so info here: btrfs-progs 5.12 breaks snap-pac and snapper-gui: upgrade to 5.12 breaks snap-pac and snapper-gui on manjaro testing · Issue #371 · kdave/btrfs-progs · GitHub
edit: should be fixed in 5.12.1 in around two days according to dev.
hello , we have version conf for systemd-oom ( version 248 ) ( in testing )
in /etc/systemd/oom.conf
1 - this will override values swapiness in /etc/sysctl.d/100-manjaro.conf
2 - may be review values proposed
3 - can you confirm systemd-oom will be used instead of swapiness ?
4 - missing topic in Testing
[OOM]
#SwapUsedLimit=90%
#DefaultMemoryPressureLimit=60%
#DefaultMemoryPressureDurationSec=30salso be careful on kernels versions ,
version 5.10 LTS & 5.4 LTS are in head before version 5.11 /5.12 on kernels site ( version appears one day later , many patchs inside )
I got this message while updating to the latest packages today:
[2021-05-12T09:23:14-0500] [ALPM] running 'glib-compile-schemas.hook'...
[2021-05-12T09:23:14-0500] [ALPM-SCRIPTLET] No such key “antialiasing” in schema “org.gnome.settings-daemon.plugins.xsettings” as specified in override file “/usr/share/glib-2.0/schemas/99_manjaro-settings.gschema.override”; ignoring override for this key.
It seems like it is no big deal as I’m not having major issues so far. 
I see systemd 248 in testing now but there is no thread announcement for it so I’m writing feedback here:
Just installed it and enabled systemd-oomd with default settings, works as expected, no issues, it’s great to finally have it. It’s not enabled by default though, should consider doing that in the near future, having your machine freeze and needing a forced restart when some program eats up all RAM is not nice.
Seems like plymouth screwed things up. After removing it (again!) everything’s back to normal.
1 Like
I have this message: “vboxsf: Unknown parameter ``tag`” when I load a Virtual Machine in VirtualBox.