Bug 22728 - Update candidate: renderdoc 1.0
Summary: Update candidate: renderdoc 1.0
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: QA Team
QA Contact:
Keywords: advisory, has_procedure
Depends on: 22657
  Show dependency treegraph
Reported: 2018-03-09 16:07 CET by Rémi Verschelde
Modified: 2018-03-22 17:29 CET (History)
2 users (show)

See Also:
Source RPM: renderdoc-0.34-2.mga6
Status comment:


Description Rémi Verschelde 2018-03-09 16:07:16 CET
RenderDoc is a tool for graphics engineers to debug rendering issues in OpenGL and Vulkan applications. It's a leaf package and specialized enough that we can push a new version as an update, especially as this new version is the 1.0 release.


Updated renderdoc package brings latest stable release

  This update brings RenderDoc 1.0 to Mageia 6, with many new features and
  fixes to existing features. See the referenced release announcements for


 - https://github.com/baldurk/renderdoc/releases/tag/v0.90
 - https://github.com/baldurk/renderdoc/releases/tag/v0.91
 - https://github.com/baldurk/renderdoc/releases/tag/v0.92
 - https://github.com/baldurk/renderdoc/releases/tag/v1.0

RPMs in core/updates_testing:


SRPMs in core/updates_testing:


Testing procedure:

None yet, but I'll do initial testing and try to document it here.
Comment 1 claire robinson 2018-03-09 19:30:51 CET
Advisory uploaded

Keywords: (none) => advisory

Comment 2 claire robinson 2018-03-10 17:57:23 CET
Info: https://renderdoc.org/docs/getting_started/quick_start.html

Testing mga6 32

It opens too wide for the screen settings but was able to test.

Before: Entered /usr/games/voxelands into the executable path and clicked to launch it.

After: Found it requires Qt from testing. Adding the Depends.

Keywords: (none) => has_procedure
Depends on: (none) => 22657

Comment 3 Herman Viaene 2018-03-13 11:35:33 CET
MGA6-32 on Dell Latitude D600 Mate
No installation issues.
qrenderdoc at CLI gives Qt5 problem. Following Comment 2, I installed all libqt5 packages from testing (81 of them) and tried again.
Now qrenderdoc starts.
Tried to launch mousepad from it (by preference a light program since this laptop is short of RAM):
first error box appears: "Error launching for capture. Renderdoc injection failed", but thereafter mousepad appears. I will check for info on the error and check whether capture works. To be continued .....

CC: (none) => herman.viaene

Comment 4 Herman Viaene 2018-03-13 12:01:36 CET
The diagnostic log gives only:
Warning - Couldn't locate renderdoc target control listening port between 38920 and 38927 in /proc/17416/net/tcp
Tried to capture mousepad by pressing F12, no result.
Tried lauching sol from renderdoc: same error message and same warning in the diagnostic log . Tried to capture sol by pressing Prtscreen, error appeared that mate-screenshot could not be found. Installed that one, tried again, but same messages at launch and no result.
I am not sure what is exactly the meaning in the Renderdoc Quickstart: "When ready, press the Capture Key (F12 or Print Screen) and the next frame after the keypress will be captured,...". When I launch anything its frame is present, so what is "next frame"???
Comment 5 Herman Viaene 2018-03-13 13:37:13 CET
Tried voxelands as per Comment 2, but not...
The voxelands window displays "OpenGL. Context not created via CreateContextAttribs. Capturing disabled. Only OpenGL 3.2+ contexts are supported."
How to find a program that can be captured ?????
Comment 6 Len Lawrence 2018-03-22 17:29:27 CET
Tried this for mga6 x86_64 on Plasma.
Installed it before enabling testing and tried launching voxelands from the configuration window.  It seemed to work in that the overlay appeared on the voxelands window.  Also tried stellarium (yes, this now works) and it launched successfuly with the overlay.

Updated renderdoc and tried these two applications again but in neither case did the gui window appear.  Don't know where to go from here.

CC: (none) => tarazed25

Note You need to log in before you can comment on or make changes to this bug.