Another excellent stable update. Thank you, everyone. No issues in LXQt on a Ryzen CPU and AMD GPU with the various graphics driver updates, Linux updates, and all the rest.
Question: At what point in the development cycle is it normal for Manjaro’s build of Linux to contain the usual patches, e.g. Fsync? 5.13-rc4 and now -rc5 lack such creature comforts and are (predictably) more ‘raw’ than the 5.12 stable Linux series.
Hi, I just got an update notification for systemd 248.3-3 from 248.3-2. Is this a part of this update?
Edit: A few days ago, I got the update for 247 → 248
BTW
Anyone know why the LXQT community edition was removed from the downloads ?
At last LXQT 0.17 solved the multiple sudo admins policykit issue and yet the edition is gone.
I was curious and I tested all LTS kernels on my old DELL E6500 after the systemd fixes with Plasma.
Results:
5.10 OK
5.4 OK
4.19 OK
4.14 crash and kernel panic, no x
4.9 mouse cursor on blank screen , crash, kernel panic after slow load of Plasma
4.4 “proc: unrcognized mount option hidepid=invisible or missing value”
mouse cursor on blank screen , no SDDM screen
Noticed this error : “cgroup: cgroup2: unknown option “nsdelegate, memory_recursiveprot””
Power management could not be started.
Not only did the update go without a hitch, but it also fixed my Bluetooth earphone dropouts problem! Thanks Manjaro team!
I’m still struggeling with this change from pulseaudio to pipewire. pulseffects does not work, pulseeffects sink has no function ans so forth. i could get audio to run but it fails periodically. i read dozens of wiki, threads here, searching the internet but i could not find any tutorial or troubleshooting that gave a solution. it’s chaotic
My first manjaro kde update with my new [Clevo NL51LU 15.6-inch Metal Design] from laptopwithlinux.
Update works fine without any issue.
Thank you
Anybody else have a problem with DNS over HTTPS on Firefox?
I actually first noticed this after stable update 2021-06-06 although could have been introduced earlier…
I was getting this issue using ‘pacman -Syu’:
Used ‘pamac update’ as recommended and updated successfully.
I am using an installation that I started with the last official Manjaro LXQt stable branch .iso from earlier this year (Downloading File /lxqt/20.2.1 - Manjaro ISO Archive - OSDN). That .iso is growing stale and might not update smoothly any more, but you do have a few options. (1) @Jim.B generously takes the time to design and build nice, up-to-date LXQt stable .isos that include (2) (unlike current official releases) the most up-to-date version of the Manjaro Architect, thereby offering either a sensible LXQt preset installation via Calamares or limitless installation customization via the Architect: SbK Lxqt 21.0.5 Further (3), it looks like LXQt is making a comeback, as we do have some unstable branch .isos available in OSDN: Downloading File /lxqt/21.0.3 - Manjaro ISO Archive - OSDN I think that you should be able to switch to the stable or testing branch after installation.
Right now I got 3 kernels installed, I have timeshift creating daily backups, and lastly if I’m going to update I also do full disk backup(system disk) using clonezilla. But so far since my last clean installed, I didnt’ got a chance to use to restore those backups. 
You can check if service is available
resolvectl status
if not, enable it
systemctl enable --now systemd-resolved
I had a small problem, the login process took around 20s after the update. I used
systemd-analyze blame and it looked like user@1000 took about 25s. Then I checked the process with systemctl status user@1000 and there was this line:
pulseaudio[1161]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
That means this is a bluetooth issue. I don’t need bluetooth therefore I disabled it and that solved it for me.
Hope they are fixed now: [xfce] update shasums (97b1f65e) · Commits · WEB / manjaro.org · GitLab
Why have you downgraded python-wxpython from 4.1.1-1 to 1:4.0.7.2-1 version in last update off June 14?
updated using pamac as recommended, no issues booting. However, it appears that the software i use to set my wallpaper (nitrogen) is broken after the update. Not the end of the world, as I can just use feh to accomplish the same task.
Thanks, I also installed from manjaro-lxqt-20.0-200423-linux56.iso downloaded earlier this year , just wondered why it’s no longer maintained and offered .
Because FS#70908
Open nitrogen in the terminal to see what are the errors.
After this update, I get the following error on every reboot/shutdown:
[FAILED]: Failed unmounting Temporary Directory (/tmp).
The system shuts down regularly, though.
After a quick check at the journal, this is what I get:
19:35:07 systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully.
19:35:07 systemd[1]: Stopped Create Volatile Files and Directories.
19:35:07 systemd[1]: Stopped target Local File Systems.
19:35:07 systemd[1]: Unmounting /boot/efi...
19:35:07 systemd[1]: Unmounting /home...
19:35:07 systemd[1]: Unmounting Temporary Directory (/tmp)...
19:35:07 umount[2597]: umount: /tmp: target is busy.
19:35:07 systemd[1]: boot-efi.mount: Deactivated successfully.
19:35:07 systemd[1]: Unmounted /boot/efi.
19:35:07 systemd[1]: tmp.mount: Mount process exited, code=exited, status=32/n/a
19:35:07 systemd[1]: Failed unmounting Temporary Directory (/tmp).
19:35:07 kernel: fbcon: Taking over console
19:35:07 kernel: Console: switching to colour frame buffer device 240x67
19:35:07 systemd[1]: Stopped target Swap.
19:35:07 systemd[1]: Deactivating swap /dev/disk/by-id/nvme-Samsung_SSD_980_PRO_1TB_S5GXNF0NC35518H-part1...
19:35:07 systemd[1]: systemd-fsck@dev-disk-by\x2duuid-1D53\x2dE902.service: Deactivated successfully.
19:35:07 systemd[1]: Stopped File System Check on /dev/disk/by-uuid/1D53-E902.
19:35:07 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-fsck@dev-disk-by\x2duuid-1D53\x2dE902 comm="system>
19:35:07 audit: BPF prog-id=9 op=UNLOAD
19:35:07 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dnvme\x2d1\x2dpart1.swap: Deactivated successfully.
19:35:07 systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:03:00.0-nvme-1-part1.
19:35:07 systemd[1]: dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_PRO_1TB_S5GXNF0NC35518H-part1.
19:35:07 systemd[1]: dev-disk-by\x2did-nvme\x2deui.002538bc01b0a830\x2dpart1.swap: Deactivated successfully.
19:35:07 systemd[1]: Deactivated swap /dev/disk/by-id/nvme-eui.002538bc01b0a830-part1.
19:35:07 systemd[1]: dev-disk-by\x2dpartuuid-5f3f1a03\x2d5c75\x2d2448\x2d9e80\x2df1b018656d04.swap: Deactivated successfully.
19:35:07 systemd[1]: Deactivated swap /dev/disk/by-partuuid/5f3f1a03-5c75-2448-9e80-f1b018656d04.
19:35:07 systemd[1]: dev-nvme0n1p1.swap: Deactivated successfully.
19:35:07 systemd[1]: Deactivated swap /dev/nvme0n1p1.
19:35:07 systemd[1]: dev-disk-by\x2duuid-a8990893\x2d435c\x2d4b5c\x2db57e\x2d0b0dc56f5649.swap: Deactivated successfully.
19:35:07 systemd[1]: Deactivated swap /dev/disk/by-uuid/a8990893-435c-4b5c-b57e-0b0dc56f5649.
19:35:08 systemd[1]: home.mount: Deactivated successfully.
19:35:08 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-fsck@dev-disk-by\x2duuid-c1917749\x2d2a19\x2d4c7b\>
19:35:08 systemd[1]: Unmounted /home.
19:35:08 systemd[1]: Reached target Unmount All Filesystems.
19:35:08 systemd[1]: systemd-fsck@dev-disk-by\x2duuid-c1917749\x2d2a19\x2d4c7b\x2d9b5c\x2d6c7a7157a736.service: Deactivated successfully.
19:35:08 systemd[1]: Stopped File System Check on /dev/disk/by-uuid/c1917749-2a19-4c7b-9b5c-6c7a7157a736.
19:35:08 systemd[1]: Removed slice system-systemd\x2dfsck.slice.
19:35:08 systemd[1]: Stopped target Local File Systems (Pre).
19:35:08 systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
19:35:08 systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
A couple of things that sound strange to me: i) systemd reports “Reached target Unmount All Filesystems” even if unmounting /tmp has failed; ii) the service systemd-tmpfiles-setup-dev.service is deactivated after attempting to unmount /tmp.
Anyone else encountering this issue? Is this something I can safely ignore?
As always, thanks to the Manjaro Team for the great work, and to the Forum for the support. 