Created attachment 132682 [details] a screen of the bug as the title said i have problems with colours...everytime i try to watch a video with a desktop player that actually use gstreamer colours gets all messed up as you can see from the screen...reported it on federa forums but they told me it could be a video driver issue since terminal is giving me radeon: The kernel rejected CS, see dmesg for more information (-22). i am using fedora 26 with mesa 17.1.4 and an ati radeon 4570 hd...anything i can do to solve the problem?
just a quick update...tried edit an mp4 video and even converting with transmageddon but the result is the same...is there any solution to this?it is solvable by a mesa update?or i just have to surrender?
Can you attach output of dmesg as suggested by the error message (and the dmesg output just after boot) and also output when setting GST_DEBUG=6 Does it work with older fedora/mesa/kernel (i.e. regression) ? You can try to compare with: gst-launch-1.0 filesrc location=test.mp4 ! qtdemux ! h264parse ! vaapih264dec ! capsfilter caps="video/x-raw(memory:VASurface)" ! vaapih264enc ! qtmux ! filesink location=res.mp4
Created attachment 132735 [details] this is the dmesg file... this is the dmesg file...i will post dmesg after boot and other thing you requested in a moment... and to answer your question, yes it was perfectly working in fedora 25...
Created attachment 132737 [details] dmesg gst debug_6
Created attachment 132738 [details] dmesg after boot
inserted all you requested...also, inputting your command in terminal results in "wrong pipeline, no vaapih264enc"
Thx for the logs but I do not see anything that could be associated to "radeon: The kernel rejected CS, see dmesg for more information (-22)" in the first dmesg attached. Also about GST_DEBUG=6, do: GST_DEBUG=6 transmageddon &> gst_debug.log then do trigger the transcoding that generates the error above.
Created attachment 132742 [details] gst.debug transmaggeddon this is the log for transmaggeddon after that error was triggered...maybe anyway is something related to mesa drivers?
(In reply to 247 from comment #3) > and to answer your question, yes it was perfectly working in fedora 25... You can try to bisect mesa. From the logs you attached I could not see anything abivous. Do you really want hardware decoding btw ? Also does gst-launch-1.0 filesrc location=test.mp4 ! qtdemux ! h264parse ! vaapih264dec ! videoconvert ! xvimagesink And what is the output of vainfo ? (just install vainfo package)
Created attachment 132816 [details] vainfo just attached the vainfo result...the gst command instead results in a syntax error...just in case there are no errors in mesa, maybe a hint where i could look for help? just in case : updated to latests gstreamer/mesa/kernel but that didn't solve my problem, and i tried a fresh installation with fedora 26 cinnamon and it's perfectly working, but i don't know if it count since i have problems in a gnome environment...
no hint on this one?sorry but is really driving me mad...
(In reply to 247 from comment #10) > Created attachment 132816 [details] > vainfo > > just attached the vainfo result... Please also attach the output when running vainfo in fedora36-cinnamon. > the gst command instead results in a > syntax error...just in case there are no errors in mesa, maybe a hint where > i could look for help? What was the syntax error ? > > just in case : updated to latests gstreamer/mesa/kernel but that didn't > solve my problem, and i tried a fresh installation with fedora 26 cinnamon > and it's perfectly working, but i don't know if it count since i have > problems in a gnome environment... What is the difference between fedora26-cinnamon(OK) and fedora26-gnome(KO) ? (x11 vs wayland ?)
tried again and this time the command gave me this result error: XDG_RUNTIME_DIR not set in the environment. No protocol specified No protocol specified error: XDG_RUNTIME_DIR not set in the environment. No protocol specified No protocol specified set pipelines to PAUSED ... No protocol specified ERROR: pipelines don't wan't to pause. ERROR: from the element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: Could not initialise Xv output additional debug informations: xvimagesink.c(1759): gst_xv_image_sink_open (): /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: Could not open display (null) set pipeline to NULL ... free execution on the pipeline... of course i translated everything into english...anyway i don't think it's a matter of x.org or wayland cause i've tried to set x.org as display driver but had exactly the same error...so don't think comparing gnome or cinnamon will help at this point...
(In reply to 247 from comment #13) > tried again and this time the command gave me this result > > error: XDG_RUNTIME_DIR not set in the environment. > No protocol specified > No protocol specified > error: XDG_RUNTIME_DIR not set in the environment. > No protocol specified > No protocol specified > set pipelines to PAUSED ... > No protocol specified > ERROR: pipelines don't wan't to pause. > ERROR: from the element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: > Could not initialise Xv output > additional debug informations: > xvimagesink.c(1759): gst_xv_image_sink_open (): > /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: > Could not open display (null) > set pipeline to NULL ... > free execution on the pipeline... > > > of course i translated everything into english...anyway i don't think it's a > matter of x.org or wayland cause i've tried to set x.org as display driver > but had exactly the same error...so don't think comparing gnome or cinnamon > will help at this point... Try installing libxv1 or try to use ximagesink (instead of xvimagesink)
(In reply to Julien Isorce from comment #14) > (In reply to 247 from comment #13) > > tried again and this time the command gave me this result > > > > error: XDG_RUNTIME_DIR not set in the environment. > > No protocol specified > > No protocol specified > > error: XDG_RUNTIME_DIR not set in the environment. > > No protocol specified > > No protocol specified > > set pipelines to PAUSED ... > > No protocol specified > > ERROR: pipelines don't wan't to pause. > > ERROR: from the element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: > > Could not initialise Xv output > > additional debug informations: > > xvimagesink.c(1759): gst_xv_image_sink_open (): > > /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: > > Could not open display (null) > > set pipeline to NULL ... > > free execution on the pipeline... > > > > > > of course i translated everything into english...anyway i don't think it's a > > matter of x.org or wayland cause i've tried to set x.org as display driver > > but had exactly the same error...so don't think comparing gnome or cinnamon > > will help at this point... > > Try installing libxv1 or try to use ximagesink (instead of xvimagesink) Ah if this is wayland, then try: waylandsink (instead of xvimagesink), or autovideosink
that's the result with waylandsink error: XDG_RUNTIME_DIR not set in the environment. No protocol specified No protocol specified Impostazione della pipeline a PAUSED ... error: XDG_RUNTIME_DIR not set in the environment. ERROR: pipeline don't wan't to pause. WARNING: to the element /GstPipeline:pipeline0/GstWaylandSink:waylandsink0: Could not initialise Wayland output Additional debug informations: gstwaylandsink.c(294): gst_wayland_sink_find_display (): /GstPipeline:pipeline0/GstWaylandSink:waylandsink0: Failed to create GstWlDisplay: 'Failed to connect to the wayland display '(default)'' Set pipeline to NULL ... Free execution on the pipeline... if i ipunt the command a second time i get : set pipeline to PAUSED ... ** (gst-launch-1.0:9446): WARNING **: Wayland compositor is missing the ability to scale, video display may not work properly. ** (gst-launch-1.0:9446): WARNING **: Could not bind to zwp_linux_dmabuf_v1 ERRORE: lpipeline does not wan't to pause. Got context from element 'vaapidecode_h264-0': gst.vaapi.Display=context, gst.vaapi.Display=(GstVaapiDisplay)"\(GstVaapiDisplayWayland\)\ vaapidisplaywayland1"; ERROR: to the element /GstPipeline:pipeline0/GstFileSrc:filesrc0: Resource not found. Additional debug information: gstfilesrc.c(535): gst_file_src_start (): /GstPipeline:pipeline0/GstFileSrc:filesrc0: No such file "test.mp4" Set pipeline to NULL ... Free execution on the pipeline...
(In reply to 247 from comment #16) > No such file "test.mp4" Yes you need to point to a valid mp4 file. Also try gst-launch-1.0 playbin uri=file:///home/you/test.mp4 -v
Created attachment 133177 [details] gst launch -v this is the output of the second command you gave me...now i'll output even the other one...
the gst command you gave me before, on the same file result in "WARNING : wrong pipeline: no uri property for the element filesrc0"
now even kodi (which was the only player working) started to give me the same problems and seems i can't play mp4 and mkv anymore...think i will just give up and end up doing a clean install...
just a quick update...since wayland is quite laggy to me i returned to xorg...my problems with kodi started with that, so i decided to return back to wayland to see if kodi worked, and it's perfectly working...so now the situation is : no player is working on xorg and no player except kodi is working on wayland... this bug will make me mad :P
at the end i just gave up and done a fresh install...problem solved now...
a quick update for this one...as you may have read i just done a fresh install and everything was fine...this until i installed the m4a codec for sound converter. Now i have done another fresh install and i have installed every needed codec (even m4a for rhythmbox and mpeg4 for videos) but i am actually missing the m4a codec for sound converter and averything works fine, so i assume there is some sort of conflict with codecs...
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/607.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.