Hmm! Sorry for the redirect, but this looks like a bug report. Would you mind 
filing it on GitHub, where we’ll be able to keep track of its status more 
precisely?

Thanks!

Adrian


> On Jan 6, 2017, at 12:08 AM, David Herring <[email protected]> wrote:
> 
> Hello everyone!
> 
> I am doing a multi-thousand song/album import and after "a while" (time frame 
> varies) the terminal window I am using gets inundated with errors such as the 
> following:
> 
> error: XDG_RUNTIME_DIR not set in the environment.
> libva info: VA-API version 0.39.0
> libva info: va_getDriverName() returns 0
> libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
> libva info: Found init function __vaDriverInit_0_39
> libva info: va_openDriver() returns 0
> 
> So what I have to do is abort the import, start the import again, and 
> "resume."  Then after a while, the errors start scrolling again. It's not on 
> the same track, not the same artist, not the same album, not the same file. 
> In fact I haven't found as yet anything in terms of a pattern. Seems random. 
> 
> I am running beets 1.4.2 on Ubuntu 16.04. It is a headless machine, well 
> technically it does have Intel graphics and the proper drivers are loaded, 
> only I don't use it. I always access the machine via ssh in a terminal 
> window.  I am not using X windows, or any kind of GUI, only command line. I 
> am running the latest generally available versions of all software. In fact I 
> just ran a complete update on the machine earlier on in my troubleshooting 
> which did not change the problem at all.
> 
> Running beets is the ONLY time these errors appear and running beets is the 
> only way I have found to recreate the problem.  Aborting the beets import 
> causes the errors to cease. Seems to show cause and effect.
> 
> The command line I use is "beets import <path to music to import>"
> 
> Here is my beets config file:
> 
> directory: /DataVolume/MediaLib/MusicLib
> library: /DataVolume/MediaLib/.beets_database
> plugins: chroma fetchart embedart scrub discogs replaygain
> chroma:
>    auto: yes
> replaygain:
>    auto: yes
>    backend: gstreamer
>    overwrite: yes
> import:
>    copy: yes
>    write: yes
>    resume: ask
>    quiet_fallback: skip
>    timid: no
>    log: beetslog.txt
> ignore: .AppleDouble ._* *~ .DS_Store
> ignore_hidden: yes
> art_filename: albumart
> threaded: yes
> ui:
>    color: no
> 
> paths:
>    default: $albumartist - $album%aunique{}/$track - $title
>    singleton: Non-Album - $album%aunique{}/$track - $title
>    comp: Compilations - $album%aunique{}/$track - $title
>    albumtype:soundtrack: Soundtracks - $album%aunique{}/$track - $title
> 
> I've scoured the beets docs, this group and Google searches in general and 
> have not learned anything that has helped. These messages make me think there 
> is something in beets that's trying to access the console graphically though 
> I cannot imagine why.
> 
> So, has anyone seen this before?  Any ideas what is causing it and what to do 
> to address it? 
> 
> I know there are similar errors being looked at in the Linux forums, so I 
> imagine they are investigating, but my reason for asking the question here is 
> more related to why beets is trying to access my video drivers and if there 
> is a way to make it stop. :-)  
> 
> Thanks and all the best,
> David
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "beets" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"beets" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to