unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Marco van Hulten <marco@hulten.org>
To: ng0 <ng0@n0.is>
Cc: help-guix@gnu.org
Subject: Re: libvdpau: cannot open shared object
Date: Sun, 10 Dec 2017 16:04:16 +0100	[thread overview]
Message-ID: <20171210155916.23e66647@jasniac.instanton> (raw)
In-Reply-To: <20171210143028.mcxndf6cms6mrrkg@abyayala>

[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]

ng0—

Je 10 dec 14:30 skribis ng0:
> For what it's worth: I've been having crashes with Kodi
> for months now.

This is worth something: we can now share the pain :-)

> Now back on a new system (installed from
> my dev branch that is a couple of commits ahead of guix master)
> I get a Kodi that has no visible font characters (even with
> fonts installed in my profile, and rebooting + fc-cache -vf run)
> and an vdpau / nouveau error message on startup.

I am using the "intel" X11 module, so it does not appear to be related
to which video card one uses.

> Were you able to start Kodi before without issues?

About a month ago, I could start Kodi without issues, on the same
hardware on GuixSD 0.13.0.  When I then rolled back to the working
version, I could run kodi again.  After some more testing, rolling back
did not help anymore: kodi kept crashing.  I documented it in a thread
on this mailinglist about two weeks ago.

Yesterday I did a clean install of GuixSD 0.14.0.  Ludo' had pointed out
that reinstalling the system is not useful, but I tried anyway when
0.14.0 came out (partly because of the inconsistent roll-back
behaviour).  I think I still have the same problems (at least for the
VDPAU error).

—Marco

[-- Attachment #2: OpenPGP digitale handtekening --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2017-12-10 15:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10 14:14 libvdpau: cannot open shared object Marco van Hulten
2017-12-10 14:30 ` ng0
2017-12-10 15:04   ` Marco van Hulten [this message]
2017-12-10 20:08 ` Efraim Flashner
2017-12-12 16:44   ` Ludovic Courtès
2017-12-12 19:58     ` Efraim Flashner
2017-12-14  9:07       ` Ludovic Courtès
2017-12-15  6:38         ` Efraim Flashner
2017-12-15 11:02           ` Ludovic Courtès
2017-12-15 12:18             ` Efraim Flashner
2017-12-15 14:31               ` Ludovic Courtès
2017-12-16  8:08                 ` Marco van Hulten
2017-12-16 19:00                   ` Ricardo Wurmus
2017-12-16 17:05                 ` Efraim Flashner
2017-12-18 20:40                   ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171210155916.23e66647@jasniac.instanton \
    --to=marco@hulten.org \
    --cc=help-guix@gnu.org \
    --cc=ng0@n0.is \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).