https://bugs.freedesktop.org/show_bug.cgi?id=99446
--- Comment #10 from Emil Velikov ---
Things can be improved on Mesa side as well. Due to the difference in
VKSurfaceKHR allocation [and related API] things can get rather nasty.
All we need is to set a flag as
https://bugs.freedesktop.org/show_bug.cgi?id=99446
yann changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=99446
Jason Ekstrand changed:
What|Removed |Added
Resolution|--- |NOTOURBUG
https://bugs.freedesktop.org/show_bug.cgi?id=99446
--- Comment #8 from Eero Tamminen ---
Sorry, that was yesterday's git, in today's upstream git, vulkaninfo handles
gracefully connection failures too.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=99446
--- Comment #7 from Eero Tamminen ---
Latest vulkaninfo from upstream git doesn't anymore coredump if DISPLAY is
missing (some other programs do). However, it will still coredump if it cannot
connect to the display
https://bugs.freedesktop.org/show_bug.cgi?id=99446
Jason Ekstrand changed:
What|Removed |Added
Status|NEW |NEEDINFO
---
https://bugs.freedesktop.org/show_bug.cgi?id=99446
--- Comment #5 from Jason Ekstrand ---
(In reply to Emil Velikov from comment #4)
> Skimming through the 30-37 commit log [1] I'm inclined to go with you _must_
> update your vulkan loader. Older versions are broken in
https://bugs.freedesktop.org/show_bug.cgi?id=99446
--- Comment #4 from Emil Velikov ---
Skimming through the 30-37 commit log [1] I'm inclined to go with you _must_
update your vulkan loader. Older versions are broken in funny ways and
attempting to workaround that in
https://bugs.freedesktop.org/show_bug.cgi?id=99446
--- Comment #3 from Shawn Starr ---
Version is: vulkan-1.0.30.0-2.fc25.x86_64
Which is what Fedora 25 ships right now.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact
https://bugs.freedesktop.org/show_bug.cgi?id=99446
--- Comment #2 from Emil Velikov ---
Issue sounds like a old libvulkan. We might be able to workaround that in the
drivers, but the version used and a back trace (as mentioned by Bas) is needed.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=99446
--- Comment #1 from Bas Nieuwenhuizen ---
Would it be possible to get a stacktrace with debug symbols for libvulkan, as
well as make sure it is somewhat up to date?
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=99446
Bas Nieuwenhuizen changed:
What|Removed |Added
QA Contact|intel-3d-bugs@lists.freedes
12 matches
Mail list logo