From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108572] Could not start gimp (probably due to opencl)
Date: Mon, 18 Feb 2019 01:48:03 +0000 [thread overview]
Message-ID: <bug-108572-502-0ZEs986zAo@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108572-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 767 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108572
Jan Vesely <jv356@scarletmail.rutgers.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|NEW |RESOLVED
--- Comment #7 from Jan Vesely <jv356@scarletmail.rutgers.edu> ---
This looks like a duplicate of 108879. I'm going to close this one as 108879 is
more generic.
KABINI si afaik CIK class GPU. Unfortunately I can't investigate as I don't
have any CIK hw.
*** This bug has been marked as a duplicate of bug 108879 ***
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2464 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-02-18 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-108572-502@http.bugs.freedesktop.org/>
2018-11-28 22:37 ` [Bug 108572] Could not start gimp (probably due to opencl) bugzilla-daemon
2018-11-29 0:56 ` bugzilla-daemon
2018-11-29 11:04 ` bugzilla-daemon
2019-02-11 22:34 ` bugzilla-daemon
2019-02-11 23:21 ` bugzilla-daemon
2019-02-17 23:51 ` bugzilla-daemon
2019-02-18 1:48 ` bugzilla-daemon [this message]
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-108572-502-0ZEs986zAo@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