Please create a new Support thread regarding that. There are no known issues.
@philm By the way, !4371 was merged after a couple more commits. I’ve updated the patch.
Are you sure about that? 
❯ pacman -Ql linux614 | grep ntsync
linux614 usr/lib/modules/6.14.0-1-MANJARO/kernel/drivers/misc/ntsync.ko.zst
Note that manual configuration is required:
❯ cat /etc/modules-load.d/ntsync.conf
ntsync
❯ cat /etc/udev/rules.d/99-ntsync.rules
KERNEL=="ntsync", MODE="0644"
❯ lsmod | grep ntsync
ntsync 16384 0
Also note that it won’t do much unless one has a version of WINE built with it. There’s still an open merge request. Maybe Proton 10.0 will include it.
1 Like
Ubuntu’s quick-boot patch just always causes recordfail=1 to be written to grubenv:
It relies on a systemd unit to reset it to 0 after a successful boot:
https://git.launchpad.net/ubuntu/+source/grub2/tree/debian/grub-common.service
Since that’s not present in manjaro’s grub package, there is nothing resetting the flag to 0. So without that unit, it doesn’t really make sense to have the other patch.
3 Likes
@su_pid i think this is to update in case on boot success for the kernel selected ( show as * for the last boot ok) and try to not record if it fail
The quick boot patch is one that manjaro carries:
Without anything calling grub-editenv /boot/grub/grubenv unset recordfail after a successful boot, that will now lead to GRUB_RECORDFAIL_TIMEOUT be always used instead of the regular timeout, and ignore the “hidden” style.
Edit:
the patch I linked before was really something different, I didn’t pay enough attention. It’s a different unit that’s responsible for the reset:
https://git.launchpad.net/ubuntu/+source/grub2/tree/debian/grub-common.service
or:
https://git.launchpad.net/ubuntu/+source/grub2/tree/debian/grub-common.init
3 Likes
mutter 48.0-4.2 seems to be working well for me so far!
1 Like
I reverted to the older patch: [pkg-upd] 2.12.r260.gaae2ea6192.12.r260.gaae2ea619-2 (20f8c2b3) · Commits · Packages / core / grub · GitLab
3 Likes
Thanks @philm.
Looks like a new grub packge dropped this morning:
core/update-grub 2:2.12.r260.gaae2ea619-1 2:2.12.r260.gaae2ea619-2
(11/12) upgrading update-grub [--------------------------------------------------------------] 100%
:: To use the new features provided in this GRUB update, it is recommended
to install it to the MBR or UEFI. Due to potential configuration
incompatibilities, it is advised to run both, installation and generation
of configuration:
# UEFI: https://wiki.archlinux.org/title/GRUB#Installation
# BIOS: https://wiki.archlinux.org/title/GRUB#Installation_2
Do I have to do something else to “install” it like the output is saying? I’ve just been doing the sudo update-grub command.
Thanks!
sudo install-grub
You did read the output? … And followd the links to install instructions?
Well, the output links to the arch wiki (not Manjaro). I always ask since things are slightly different in the Manjaro world sometimes.
@philm - Also, if I had made the grub change so the previous update worked (by including the ‘GRUB_RECORDFAIL_TIMEOUT’ parameter), should I remove that before updating? I’m assuming the answer is yes.
Thanks everyone for answering my newbie questions. Your time and help is appreciated!
1 Like
Edit: disregard, this was pop-shell’s “Mouse cursor follows active window” being active in the extension’s settings.
@Yochanan the only odd thing I’m seeing now which may or may not be related is switching through workspaces via super + 1, 2, 3 etc…makes my mouse jump over to other monitors which is pretty annoying.
Shouldn’t this be in /dev/ntsync? At least cachyos kernel does not require manual setting.
Didn’t think it needed to be turn on manually, thanks for the answer.
Yes, I know that need a special version of wine, I built it
plasma-workspace and kwindowsystem were updated together on Arch to fix this bug.
Manjaro’s plasma-workspace needs a rebuild with the relevant patch.
EDIT: Patched plasma-workspace has been pushed to testing and unstable. Thanks, Manjaro team!
3 Likes
install lib32-nvidia-utils is the solution
Hey all, I have also question about 6.14, ntsync and the decisions for that. Could someone append a conclusion about this term or link to wiki article etc.?
I surely not the first person with this questions, but it’s hard to understand the current status out of this long thread 
Thx for help
Kyrindorx
Hey all, I have also question about 6.14, ntsync and the decisions for that. Could someone append a conclusion about this term or link to wiki article etc.?
1 Like
A friend of mine told me ntsync require an integration into proton to use the benefits of ntsync. So we have also wait for a new wine/proton version which supports ntsync? Or is something depending from todo’s of a distro?
Most likely, yes. You have to keep in mind that Windows applications running on top of a UNIX operating system via wine and friends are not using the UNIX-native syscalls — they are using Windows syscalls, which wine, proton and siblings must translate into UNIX syscalls on-the-fly.
Therefore, these translation protocols must keep up with the latest changes in the kernel — and possibly in other low-level systems, like glibc — in order to take advantage of these optimizations.
That said — and mind you, I am not a gamer and I don’t have any Windows software installed on my computer — I do expect that it won’t be all too long before thus-equipped versions of wine, proton and friends will appear.
