Fsck hook is not needed, we have a systemd hook that takes care of it.
2 Likes
Hi. I’m using Gnome. I have a USB mouse that I set its primary mouse button to the right button (Left handed setting). When I disconnect the mouse and reconnect it, the setting appears to remain the same in the mouse settings graphical interface, but the primary button is switched to the left button (Right handed/default). Anyone else has this problem? Any idea how to solve?
What makes it problematic for me is that I’m also facing an issue where the mouse keeps reconnecting automatically (without unplugging) and the button keeps switching every now and then. This reconnecting issue is not related to the update though.
In KDE sometimes the sound output through PulseEffects to the device is disabled (muted).
Sometimes it doesn’t work right after the system boots, sometimes later for no clear reason. But for sure, if you try to change the output in the settings, then the output through PulseEffects stops working.
These two entries appear in the journal at that moment:
06.11.2020 21:47 plasmashell org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
06.11.2020 21:47 plasmashell kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecatedAfter updating on my Dell Inspiron 3558 running the KDE edition, PulseAudio doesn’t switch from headphones to speakers like it did prior to updating.
For anyone else having a similar issue, I got it working again by commenting out the downgrading to an older version of pulseaudio and it’s dependencies.load-module module-switch-on-port-available line in /etc/pulse/default.pa.
3 Likes
I have the same issue after upgrading gnome.
1 Like
Great update. Thanks Manjaro team!
Gnome 3.38.1
Linux 5.4.74-1
thanks for the update.
looking gooooood
and another linux lesson for me 
https://wiki.archlinux.org/index.php/Mkinitcpio
plasma/5.8/440
Updated two systems - KDE - no problems this side.
My KDE system has the busybox hooks by default. Is there a benefit or risk to switching over to the systemd hooks?
Anything else need to be done besides making the changes to the .conf file and updating mkinitcpio and grub in Terminal?
I second that, Manjaro as Guest in VMware Workstation Pro 15 does not work well. Especially Visual Studio Code becomes unusable. I had the same problem with OpenSuSE.
I tracked it down to the recent mesa update. Downgrading from 20.2.1 to 20.1.8 solved my problem.
Seems to be already fixed upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3599.
1 Like
Had the same issue with Workstation Pro 16. Downgrading mesa to 20.1.8 did the trick, thanks! Looks like it was fixed in the master branch but wasn’t backported to 20.2.x branch.
1 Like
It doesn’t work well for me – it switches sound to headphones, but plasma still says it is speakers and pulseeffects equalizer doesnt change its profile until i manually change speakers to headphones in plasma
Works on bare metal.
I’m running Manjaro Gnome on my Lenovo C340 Convertible.
Since the update I have problems with the tablet mode
The physical keyboard still gets disabled (as it should be).
But at the same time automatic screen rotation and the onscreen keyboard won’t get activated like before the update.
Using the systemd hooks has shaved off 1 second from my boot time. I have not experienced any adverse effects. 
Nope. 
2 Likes
Update went fine…
Gnome + Linux59
All went well on two machines: Kernel 5.8, XFCE
Just updated this morning. so far, so good. 
Updated to manjaro-release-20.2pre-1 on Nov. 5th, and since next reboot I now have a very strange behavior:
- Manjaro via grub works as usual, graphical environment is ready for login within approx. 10 seconds
- After login, the Xfce desktop shows up within 5 seconds, but: with Manjaro default background
- thereafter, without any input or mouse actions, my customized background shows up approx 60 seconds later.
- after that, most applications that I start will come up almost immediately, as usual, but some have an annoying delay: for example, thunar starts up immediate but takes 60 seconds before my Home directory is displayed, and rejects any response to mouse actions until then.
I looked for anything strange in dmesg and system journal, but found nothing that might give an indication of whats going wrong.
Obviously, this misbehavior seems to be related to programs accessing the (home?) file system.
I will be grateful for any hints on how to solve this issue.
Output from “inxi -Fza”:
System: Kernel: 5.7.19-2-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.7-x86_64 root=UUID=27c7c49d-1ad3-4699-b89d-8a17ba31a557 rw quiet
udev.log_priority=3
Desktop: Xfce 4.14.2 tk: Gtk 3.24.20 info: xfce4-panel wm: xfwm4 dm: LightDM 1.30.0 Distro: Manjaro Linux
Machine: Type: Desktop Mobo: MSI model: H170A GAMING PRO (MS-7978) v: 1.0 serial: <filter>
UEFI [Legacy]: American Megatrends v: 2.E0 date: 07/04/2018
CPU: Info: Quad Core model: Intel Core i7-7700K socket: U3E1 bits: 64 type: MT MCP arch: Kaby Lake family: 6
model-id: 9E (158) stepping: 9 microcode: D6 L1 cache: 256 KiB L2 cache: 8192 KiB L3 cache: 8000 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 67224
Speed: 800 MHz min/max: 800/4500 MHz base/boost: 4200/8300 volts: 1.2 V ext-clock: 100
Graphics: Device-1: NVIDIA TU106 [GeForce RTX 2070] vendor: Micro-Star MSI driver: nvidia v: 440.100
alternate: nouveau,nvidia_drm bus ID: 01:00.0 chip ID: 10de:1f02
Display: server: X.Org 1.20.9 driver: nvidia display ID: :0.0 screens: 1
Screen-1: 0 s-res: 3440x1440 s-dpi: 96 s-size: 910x381mm (35.8x15.0") s-diag: 987mm (38.8")
Monitor-1: DP-2 res: 3440x1440 hz: 60 dpi: 109 size: 798x335mm (31.4x13.2") diag: 865mm (34.1")
OpenGL: renderer: GeForce RTX 2070/PCIe/SSE2 v: 4.6.0 NVIDIA 440.100 direct render: Yes
Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
bus ID: 00:1f.3 chip ID: 8086:a170
Device-2: NVIDIA TU106 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 01:00.1
chip ID: 10de:10f9
Sound Server: ALSA v: k5.7.19-2-MANJARO
Network: Device-1: Intel Ethernet I219-V vendor: Micro-Star MSI driver: e1000e v: 3.2.6-k port: f000
chip ID: 8086:15b8
IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 2.63 TiB used: 143.03 GiB (5.3%)
ID-1: /dev/sda vendor: Crucial model: CT525MX300SSD1 family: Micron BX/MX1/2/3/500,
size: 489.05 GiB sata: 3.2 speed: 6.0 Gb/s scheme: GPT
SMART: yes state: enabled health: PASSED on: 354d 11h cycles: 1108 written: 5.04 TiB
ID-2: /dev/sdb vendor: SanDisk model: SDSSDHII240G family: Marvell based SSDs size: 223.57 GiB sata: 3.2 speed: 6.0 Gb/s scheme: MBR
SMART: yes state: enabled health: PASSED on: 165d 21h cycles: 1323
ID-3: /dev/sdc vendor: Western Digital model: WD20EARX-00PASB0 family: Green size: 1.82 TiB sata: 3.0 speed: 6.0 Gb/s scheme: MBR
SMART: yes state: enabled health: PASSED on: 2y 200d 0h cycles: 3392
ID-4: /dev/sdd vendor: SanDisk model: SD8SBAT128G1122 size: 119.24 GiB sata: 3.2 speed: 6.0 Gb/s scheme: MBR
SMART: yes state: enabled health: PASSED on: 10d 4h cycles: 1781 read: 3.0 MiB written: 1.2 MiB Old-Age: media wearout: 100
Partition: ID-1: / raw size: 40.05 GiB size: 38.92 GiB (97.18%) used: 19.49 GiB (50.1%) fs: ext4 block size: 4096 B
dev: /dev/sdd3
ID-2: /home raw size: 489.05 GiB size: 481.25 GiB (98.41%) used: 123.54 GiB (25.7%) fs: ext4 block size: 4096 B
dev: /dev/sda1
Swap: Kernel: swappiness: 60 (default) cache pressure: 100 (default)
ID-1: swap-1 type: partition size: 2.00 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdd4
Sensors: System Temperatures: cpu: 34.0 C mobo: 29.8 C gpu: nvidia temp: 33 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 31%
Info: Processes: 242 Uptime: 4h 26m Memory: 31.31 GiB used: 3.26 GiB (10.4%) Init: systemd v: 246 Compilers: gcc: 10.2.0
Packages: pacman: 1404 lib: 392 flatpak: 0 Shell: Bash (sudo) v: 5.0.18 running in: xfce4-terminal inxi: 3.1.08