| Bug ID | 101787 |
|---|---|
| Summary | colours all messed up |
| Product | Mesa |
| Version | 17.1 |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | critical |
| Priority | medium |
| Component | Drivers/DRI/R100 |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | mad_fer_it@msn.com |
| QA Contact | dri-devel@lists.freedesktop.org |
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 me=
ssed
up as you can see from the screen...reported it on federa forums but they t=
old
me it could be a video driver issue since terminal is giving me=20
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?
| What | Removed | Added |
|---|---|---|
| Component | Drivers/DRI/R100 | Drivers/Gallium/r600 |
just a quick update...tried edit an mp4 video and even convert= ing 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 messa= ge (and the dmesg output just after boot) and also output when setting GST_DEBUG=3D6 Does it work with older fedora/mesa/kernel (i.e. regression) ? You can try to compare with: gst-launch-1.0 filesrc location=3Dtest.mp4 ! qtdemux ! h264parse ! vaapih26= 4dec ! capsfilter caps=3D"video/x-raw(memory:VASurface)" ! vaapih264enc = ! qtmux ! filesink location=3Dres.mp4
Created attachment 132=
735 [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 132738 <=
a href=3D"attachment.cgi?id=3D132738&action=3Dedit" title=3D"dmesg afte=
r boot">[details]
dmesg after boot
inserted all you requested...also, inputting your command in t= erminal results in "wrong pipeline, no vaapih264enc"
Thx for the logs but I do not see anything that could be assoc= iated to "radeon: The kernel rejected CS, see dmesg for more information (-22)" in the f= irst dmesg attached. Also about GST_DEBUG=3D6, do: GST_DEBUG=3D6 transmageddon &> gst_d= ebug.log then do trigger the transcoding that generates the error above.
Created attachment 1327=
42 [details]
gst.debug transmaggeddon
this is the log for transmaggeddon after that error was triggered...maybe
anyway is something related to mesa drivers?
| What | Removed | Added |
|---|---|---|
| Attachment #132737 is obsolete | 1 |
(In reply to 247 from = comment #3) > and to answer your question, yes it was perfectl= y 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=3Dtest.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 synt=
ax
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 sol=
ve
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...
(In reply to 247 from comment #10) > Created attachment 132816 [details] > vainfo >=20 > 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 ? >=20 > 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 cinn= amon > 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 th= is result >=20 > 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:xvimages= ink0: > 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... >=20 >=20 > 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 dr= iver > but had exactly the same error...so don't think comparing gnome or cin= namon > 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 > >=20 > > 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:xvi= magesink0: > > 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... > >=20 > >=20 > > of course i translated everything into english...anyway i don't t= hink it's a > > matter of x.org or wayland cause i've tried to set x.org as displ= ay driver > > but had exactly the same error...so don't think comparing gnome o= r cinnamon > > will help at this point... >=20 > 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 abi= lity 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=3Dcontext, gst.vaapi.Display=3D(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=3Dfile:///home/you/test.mp4 -v
Created attachment 133177
References:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[IPv6:2610:10:20:722:a800:ff:fe98:4b55])
by gabe.freedesktop.org (Postfix) with ESMTP id E47F76EDB8
for ; Tue, 1 Aug 2017 16:58:45 +0000 (UTC)
In-Reply-To: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============0629750576==
Content-Type: multipart/alternative; boundary="15016067250.44Ae.27498";
charset="UTF-8"
--15016067250.44Ae.27498
Date: Tue, 1 Aug 2017 16:58:45 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D101787
--- Comment #19 from 247 ---
the gst command you gave me before, on the same file result in "WARNING : w=
rong
pipeline: no uri property for the element filesrc0"
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15016067250.44Ae.27498
Date: Tue, 1 Aug 2017 16:58:45 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Comme=
nt # 19
on bug 10178=
7
from 247
the gst command you gave me before, on the same file result in=
"WARNING : wrong
pipeline: no uri property for the element filesrc0"
You are receiving this mail because:
- You are the assignee for the bug.
=
--15016067250.44Ae.27498--
--===============0629750576==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============0629750576==--
From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 101787] colours all messed up
Date: Mon, 07 Aug 2017 07:29:05 +0000
Message-ID:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id CA1BE6E316
for ; Mon, 7 Aug 2017 07:29:04 +0000 (UTC)
In-Reply-To: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============0822332070==
Content-Type: multipart/alternative; boundary="15020909440.2DAA.11656";
charset="UTF-8"
--15020909440.2DAA.11656
Date: Mon, 7 Aug 2017 07:29:04 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D101787
--- Comment #20 from 247