From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101832] [regression][bisect] sddm fails to start after f50aa21456d82c8cb6fbaa565835f1acc1720a5d
Date: Fri, 21 Jul 2017 13:00:32 +0000 [thread overview]
Message-ID: <bug-101832-502-QFrt5MLaEQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101832-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 761 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101832
Emil Velikov <emil.l.velikov@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |timothy.o.rowley@intel.com
--- Comment #5 from Emil Velikov <emil.l.velikov@gmail.com> ---
Right, so I may have misread the Xorg.log, but at least the AVX binaries will
not have unresolved symbols, props to
https://patchwork.freedesktop.org/patch/168170/
Possible symbol collision comes to mind, but I'm not working on either SWR or
radeonsi :-\
Tim, can you please have a look?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2276 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-07-21 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 23:06 [Bug 101832] [regression][bisect] sddm fails to start after f50aa21456d82c8cb6fbaa565835f1acc1720a5d bugzilla-daemon
2017-07-19 10:47 ` bugzilla-daemon
2017-07-19 13:22 ` bugzilla-daemon
2017-07-19 14:06 ` bugzilla-daemon
2017-07-19 14:14 ` bugzilla-daemon
2017-07-21 13:00 ` bugzilla-daemon [this message]
2017-07-24 15:30 ` bugzilla-daemon
2017-07-24 15:54 ` bugzilla-daemon
2017-08-16 10:59 ` 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-101832-502-QFrt5MLaEQ@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