From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101787] colours all messed up
Date: Tue, 01 Aug 2017 13:54:46 +0000 [thread overview]
Message-ID: <bug-101787-502-CbIDov1XF2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101787-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1131 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101787
--- Comment #13 from 247 <mad_fer_it@msn.com> ---
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...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1849 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-08-01 13:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 7:53 [Bug 101787] colours all messed up bugzilla-daemon
2017-07-14 8:16 ` bugzilla-daemon
2017-07-16 17:00 ` bugzilla-daemon
2017-07-17 9:08 ` bugzilla-daemon
2017-07-17 15:33 ` bugzilla-daemon
2017-07-17 15:44 ` bugzilla-daemon
2017-07-17 15:50 ` bugzilla-daemon
2017-07-17 15:51 ` bugzilla-daemon
2017-07-17 15:57 ` bugzilla-daemon
2017-07-18 6:59 ` bugzilla-daemon
2017-07-18 14:12 ` bugzilla-daemon
2017-07-21 10:00 ` bugzilla-daemon
2017-07-21 14:27 ` bugzilla-daemon
2017-07-31 15:35 ` bugzilla-daemon
2017-07-31 22:33 ` bugzilla-daemon
2017-08-01 13:54 ` bugzilla-daemon [this message]
2017-08-01 14:14 ` bugzilla-daemon
2017-08-01 14:15 ` bugzilla-daemon
2017-08-01 14:37 ` bugzilla-daemon
2017-08-01 15:37 ` bugzilla-daemon
2017-08-01 16:55 ` bugzilla-daemon
2017-08-01 16:58 ` bugzilla-daemon
2017-08-07 7:29 ` bugzilla-daemon
2017-08-07 8:14 ` bugzilla-daemon
2017-08-08 15:57 ` bugzilla-daemon
2017-08-12 8:55 ` bugzilla-daemon
2019-09-18 19:23 ` bugzilla-daemon
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=bug-101787-502-CbIDov1XF2@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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