Github messages for voidlinux
 help / color / mirror / Atom feed
From: datenwolf <datenwolf@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Vulkan-Tools-1.2.135_1 has a regression in `vulkaninfo`: no output for headless configuration
Date: Sat, 11 Apr 2020 13:52:25 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20875@inbox.vuxu.org> (raw)

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

New issue by datenwolf on void-packages repository

https://github.com/void-linux/void-packages/issues/20875

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->

There is a regression in the official Vulkan-Tools-1.2.135, that breaks this behavior. This regression has been fixed in the current git master HEAD (v1.2.135-21-g490e3937) however no release yet.

The most recent official version without that regression is tag v1.2.133 (git 16cf5591e399aed1de1401150cd47264132e6e0b)

### System

* xuname:  Void 5.4.29_1 x86_64 GenuineIntel notuptodate rrrrrmmdnFFFFF
* package:  Vulkan-Tools-1.2.135_1

### Expected behavior
Running outside of a display environment (X11, Wayland, and such) vulkaninfo is supposed to report headless rendering capabilities.

    DISPLAY='' vulkaninfo
    … lots of output …

### Actual behavior

    DISPLAY='' vulkaninfo
    ERROR at /builddir/Vulkan-Tools-1.2.135/vulkaninfo/vulkaninfo.h:990: 'DISPLAY' environment variable not set... skipping surface info

### Steps to reproduce the behavior

Install Vulkan-Tools-1.2.135 and run `vulkaninfo` outside of a display environment.

             reply	other threads:[~2020-04-11 11:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-11 11:52 datenwolf [this message]
2020-04-20 13:46 ` [ISSUE] [CLOSED] " Hoshpak

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

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

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20875@inbox.vuxu.org \
    --to=datenwolf@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 NNTP newsgroup(s).