https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291919
--- Comment #5 from Tomoaki AOKI <[email protected]> ---
(In reply to Sean Farley from comment #4)
I'm not using x11-wm/picom. But no issue like you described happenes for me.
Mate DE + Compiz (also a derivative work from compton).
GPU is RTX A400 (Ampere generation of architecture).
Note that Compiz components are not of ports tree but newer version
that Ken DEGUCHI is maintaining as overlay.
https://github.com/kdeguchi/compiz-reloaded-ports
And looking into issues at picom upstream repo, found below.
https://github.com/yshui/picom/issues/1488
Is your issue with screen flickering like above?
If so, as the picom issue is reported (initially) for Linux, maybe we can
nothing to do until nvidia releases fixed version of their drivers (likely the
issue is on binary only proprietary part that I have no access to source codes,
common codebase with Linux and FreeBSD (and maybe Solaris, too).
Another possibility is somehow related with graphics/egl-wayland.
But as I'm not sure how picom calls GPU drivers, not sure this commit
upstream could help or not.
https://github.com/NVIDIA/egl-wayland/commit/f81fcd016bb232c12ba59dddb240648203caaf4c
If the description looks related, I can update graphics/egl-wayland to 1.1.21,
which is newer than the one in Linux version (Linux has 1.1.20 and we have
the same version to keep in sync), but need some tests that it causes different
issue or not before submitting patch / open review for it.
For key delays, not sure that it really is related with nvidia drivers or not.
Is your installed ports/pkgs up to date "as a whole"?
If there are any leftovers especially related with libinput or evdev, it could
be the cause.
If you're using any IME (Japanese, Chinese,...), it can affect, too.
Not 100% sure, but IIRC, I've bitten something alike using ibus years ago, and
switching to scim (at the moment) helped. Now I'm using fcitx5-mozc ported and
maintained by Ken DEGUCHI as overlay.
https://github.com/kdeguchi/mozc-ports
--
You are receiving this mail because:
You are on the CC list for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.