<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Jan 2, 2026 at 10:12 AM Alain via mythtv-users <<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 1/2/26 14:52, Will Dormann wrote:<br>
> On 1/2/26 8:41 AM, Alain via mythtv-users wrote:<br>
>> #0 0x00007fffee670364 in XDisplayString () at /lib/x86_64-linux-gnu/ <br>
>> libX11.so.6<br>
>> #1 0x00007fff20205f05 in __vaDriverInit_1_0 () at /usr/lib/x86_64- <br>
>> linux-gnu/dri/nvidia_drv_video.so<br>
>> #2 0x00007fffee615873 in vaInitialize () at /lib/x86_64-linux-gnu/ <br>
>> libva.so.2<br>
><br>
><br>
> I'll let the experts jump in here, but I'd say that this is indicative <br>
> of an nvidia driver problem. I seem to recall nvidia drivers being <br>
> tied to Ubuntu OS releases, so it's possible that from your jumps from <br>
> 20.04 to 22.04 and 22.04 to 24.04, something got stuck on a non-ideal <br>
> version.<br>
><br>
> Personally, I'd try making sure that your nvidia drivers are up to <br>
> date. Caution, though, as I think that some nvidia driver versions <br>
> are tied to support of specific ranges of GPUs. So finding the right <br>
> version may require some trial and error.<br>
><br>
><br>
><br>
> -WD<br>
> _______________________________________________<br>
<br>
With respect to Nvidia, I've tried different drivers. Including the most <br>
recent one, 580, all to the same results on the backend server. This is <br>
the current configuration:<br>
<br>
nvidia-compute-utils-570/noble-updates,noble-security,now <br>
570.195.03-0ubuntu0.24.04.1 amd64 [installed,automatic]<br>
nvidia-driver-570-open/noble-updates,noble-security,now <br>
570.195.03-0ubuntu0.24.04.1 amd64 [installed]<br>
nvidia-firmware-570-570.195.03/noble-updates,noble-security,now <br>
570.195.03-0ubuntu0.24.04.1 amd64 [installed,automatic]<br>
nvidia-kernel-common-570/noble-updates,noble-security,now <br>
570.195.03-0ubuntu0.24.04.1 amd64 [installed,automatic]<br>
nvidia-kernel-source-570-open/noble-updates,noble-security,now <br>
570.195.03-0ubuntu0.24.04.1 amd64 [installed,automatic]<br>
nvidia-prime/noble,noble,now 0.8.17.2 all [installed]<br>
nvidia-settings/noble,now 510.47.03-0ubuntu4 amd64 [installed]<br>
nvidia-utils-570/noble-updates,noble-security,now <br>
570.195.03-0ubuntu0.24.04.1 amd64 [installed,automatic]<br>
<br>
However, given that I'm getting the exact same results when trying <br>
to display remotely mythfrontend (see previous mails on this thread), <br>
the local nvidia driver shouldn't be the root cause.<br>
<br>
But as I look back in the backtrace, even though DISPLAY is set to <br>
remote (localhost:12.0), mythfrontend still goes through the same back <br>
trace which I don't understand.<br>
<br>
I have tried the Nouveau driver, but the X server/GUI doesn't even <br>
start. I had enough other issues to troubleshoot and I went back to <br>
NVidia, but to a different driver.<br>
<br>
Also on the topic of Nvidia, I had to also upgrade to Ubuntu 24.04 to <br>
keep up with my backend. On my desktop, I never had an issue with the <br>
mythfrontend. On the desktop, I'm using nvidia 580.95.<br>
<br>
So, while the crash occurs through the NVidia driver, there is <br>
something else which contributes to those core dumps. Otherwise, this <br>
forum would be flooded with complaints.<br>
<br>
In the meanwhile, I'll try other releases of Nvidia.<br>
<br>
Alain<br></blockquote><div><br></div><div>Have you attempted to clear out and rebuild the old nvidia dkms modules (substitute the right version for xxx.yyy.zz)?</div><div><br></div>sudo dkms remove -m nvidia -v xxx.yyy.zz --all (Removes all versions)<br>sudo dkms add -m nvidia -v xxx.yyy.zz<br>sudo dkms install -m nvidia -v xxx.yyy.zz -k $(uname -r) </div></div>