From: Steven Newbury <steve@snewbury.org.uk>
To: Hans de Goede <hdegoede@redhat.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: xf86-video-intel-2.99.912 with dri3 enabled breaks gnome-shell
Date: Thu, 26 Jun 2014 13:36:44 +0100 [thread overview]
Message-ID: <1403786204.20489.5.camel@artifact> (raw)
In-Reply-To: <539A18C7.3020705@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 940 bytes --]
On Thu, 2014-06-12 at 23:16 +0200, Hans de Goede wrote:
> Hi All,
>
> While preparing 1.15.99.903 server + 2.99.912 intel drv packages
> for Fedora 21, I noticed that both gdm and gnome-shell (tested
> with startx) hang, they show the initial background screen and
> then just sit there.
>
> Building the server with --disable-dri3, or building the
> intel drv with a hacked configure.ac to make it not build
> with dri3 support fixes this.
>
> Note this is with mesa 10.2.1, which has been build with xgl-dri3
> support, I've double checked this.
>
Hi Hans!
Have you got to the bottom of this? I see the same thing, and also
possibly with GLX contexts under XWayland also with gnome-shell. If
it's the same thing, it points to the mesa i965 DRI(3) driver side
rather than the DDX driver since it's not involved any more with
XWayland.
(using git master or latest unstable releases of relevant components)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-06-26 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 21:16 xf86-video-intel-2.99.912 with dri3 enabled breaks gnome-shell Hans de Goede
2014-06-13 10:07 ` Chris Wilson
2014-06-17 10:32 ` Chris Wilson
2014-06-26 12:36 ` Steven Newbury [this message]
2014-06-26 21:54 ` Rémi Cardona
2014-06-26 23:59 ` Dave Airlie
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=1403786204.20489.5.camel@artifact \
--to=steve@snewbury.org.uk \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@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