vidia-kmod[-devel],
 x11/linux-nvidia-libs[-devel], graphics/nvidia-drm*-kmod[-devel],
 x11/nvidia-settings, x11/nvidia-xconfig: Update to 580.119.02
Date: Mon, 05 Jan 2026 09:44:42 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: junchoon@dec.sakura.ne.jp
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: kbowling@freebsd.org
X-Bugzilla-Flags: maintainer-feedback+ maintainer-feedback+
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-291919-7141-JkWpQIv2t0@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-291919-7141@https.bugs.freebsd.org/bugzilla/>
References: <bug-291919-7141@https.bugs.freebsd.org/bugzilla/>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
List-Id: X11 <freebsd-x11.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-x11
List-Help: <mailto:x11+help@freebsd.org>
List-Post: <mailto:x11@freebsd.org>
List-Subscribe: <mailto:x11+subscribe@freebsd.org>
List-Unsubscribe: <mailto:x11+unsubscribe@freebsd.org>
X-BeenThere: freebsd-x11@freebsd.org
Sender: owner-freebsd-x11@FreeBSD.org
MIME-Version: 1.0

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D291919

--- Comment #5 from Tomoaki AOKI <junchoon@dec.sakura.ne.jp> ---
(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 co=
des,
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.
=20
https://github.com/NVIDIA/egl-wayland/commit/f81fcd016bb232c12ba59dddb24064=
8203caaf4c

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 diffe=
rent
issue or not before submitting patch / open review for it.


For key delays, not sure that it really is related with nvidia drivers or n=
ot.
Is your installed ports/pkgs up to date "as a whole"?
If there are any leftovers especially related with libinput or evdev, it co=
uld
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

--=20
You are receiving this mail because:
You are on the CC list for the bug.=