From owner-freebsd-multimedia@FreeBSD.ORG  Mon Jan 26 23:30:23 2015
Return-Path: <owner-freebsd-multimedia@FreeBSD.ORG>
Delivered-To: freebsd-multimedia@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 07E61C6D
 for <freebsd-multimedia@freebsd.org>; Mon, 26 Jan 2015 23:30:23 +0000 (UTC)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com
 [IPv6:2607:f8b0:4003:c06::22a])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id BE98F17C
 for <freebsd-multimedia@freebsd.org>; Mon, 26 Jan 2015 23:30:22 +0000 (UTC)
Received: by mail-oi0-f42.google.com with SMTP id i138so9813001oig.1
 for <freebsd-multimedia@freebsd.org>; Mon, 26 Jan 2015 15:30:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:date:message-id:subject:from:to:content-type;
 bh=Z28E9aa+g1FCIhRN6vt2b3u+y23IdhJlgBC6TOTcJq0=;
 b=YH8/XJd65WzQ+CsiQVkn2qLPR0Px7Ho17nM/ZzYIvq+wpCJy3RMeJ684hv05TnahB0
 Stk52Z0LT3i9jooI+p7/fvd9/apDyuttDxcmtYbWAWTyH8lo5ZM5fMJojwajf/LSwk+G
 3A4h7QxxCvNJnT8rMGJfb+hodD1eAXSyBRZU3n+x2HsFboA+b9k1E2gaj3trETz0hGyS
 K/Qd4bVKC0TKoLF7qNFAl42C8Vtn8LVEraUeuIUqkH7P0UXaKKX7YDvodCKi2xEWRE5G
 sFTtJAqL25f4u+gGCK9i9cyMooVSqhRwz7BCWnp1AbvKZ2zNcP7R78PKFz1maNKKeMTP
 sufQ==
MIME-Version: 1.0
X-Received: by 10.60.76.138 with SMTP id k10mr14510715oew.86.1422315022171;
 Mon, 26 Jan 2015 15:30:22 -0800 (PST)
Sender: tom.lislegaard@gmail.com
Received: by 10.202.230.65 with HTTP; Mon, 26 Jan 2015 15:30:22 -0800 (PST)
Date: Tue, 27 Jan 2015 00:30:22 +0100
X-Google-Sender-Auth: 20wBllVH0LuRzX8mJ_rFOWhfdZI
Message-ID: <CAFxxQFynRdywPMbnKDm4Bs3kbi9ZgKnUr-51m_z6avBF-YaAxA@mail.gmail.com>
Subject: Re: Mythfrontend fails with segfault after system upgrade
From: Tom Lislegaard <tom@lislegaard.net>
To: freebsd-multimedia@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
X-BeenThere: freebsd-multimedia@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Multimedia discussions <freebsd-multimedia.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-multimedia>, 
 <mailto:freebsd-multimedia-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-multimedia/>
List-Post: <mailto:freebsd-multimedia@freebsd.org>
List-Help: <mailto:freebsd-multimedia-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia>, 
 <mailto:freebsd-multimedia-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 23:30:23 -0000

As it turns out this is a known problem with recent versions of the
nvidia-driver.
It was fixed upstream some time ago, but apparently hasn't made it into the
port yet.

The necessary patch is this one

https://code.mythtv.org/cgit/mythtv/commit/?h=fixes/0.27&id=583395f5a376637efcd408a102fa64d0f188c12f

-tom