https://bugs.freedesktop.org/show_bug.cgi?id=99400
--- Comment #5 from Olivier Fourdan ---
(In reply to Ilia Mirkin from comment #4)
> This may come as some surprise, but nv30 is not a hotbed of development
Understandable :)
> activity. If you can figure out a change in mesa
https://bugs.freedesktop.org/show_bug.cgi?id=99400
--- Comment #7 from Olivier Fourdan ---
(In reply to Ilia Mirkin from comment #6)
> How did you get this trace? I can't seem to replay it - none of the context
> setup stuff is there. (And it seems to like doing glFlush *a
Le vendredi 13 janvier 2017 16:11:59 CET, vous avez écrit :
In addition, i noticed the following :
xrand --output HDMI-1 --auto
show the following messages in the dmesg :
24957.310638] nouveau :01:00.0: DRM: resuming kernel object tree...
[24957.310873] nouveau :01:00.0: priv:
https://bugs.freedesktop.org/show_bug.cgi?id=99400
--- Comment #6 from Ilia Mirkin ---
(In reply to Olivier Fourdan from comment #1)
> apitrace of Xwayland available here:
>
> https://people.freedesktop.org/~ofourdan/xwayland-apitrace-bug-99400.bz2
How did you get this
https://bugs.freedesktop.org/show_bug.cgi?id=92077
--- Comment #30 from Andrey Mazo ---
(In reply to Ilia Mirkin from comment #29)
> Can someone see whether sticking
>
> QSG_RENDER_LOOP=basic
>
> into /etc/environment helps anything?
I could try, but looks like it's used by
https://bugs.freedesktop.org/show_bug.cgi?id=99400
--- Comment #8 from Ilia Mirkin ---
(In reply to Olivier Fourdan from comment #7)
> (In reply to Ilia Mirkin from comment #6)
> > How did you get this trace? I can't seem to replay it - none of the context
> > setup stuff
https://bugs.freedesktop.org/show_bug.cgi?id=99396
--- Comment #1 from a...@cornell.edu ---
I've managed to reproduce the crash fairly consistently by doing the following:
1. Open two Firefox windows on one virtual desktop
2. Open a gnome-terminal window on another desktop
3. Repeatedly alt-tab
On Thu, Jan 12, 2017 at 3:51 AM, Sylvain Fabre wrote:
> xrand
>
> Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
> eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
> axis) 344mm x 194mm
> 1920x1080 60.02*+ 47.99
>
https://bugs.freedesktop.org/show_bug.cgi?id=99396
Bug ID: 99396
Summary: Crash in nouveau_dri.so when switching apps with
alt-tab in Gnome
Product: Mesa
Version: git
Hardware: Other
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=99400
Bug ID: 99400
Summary: [nouveau] garbled rending with glamor on G71
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity:
>
> OK, so I think that these are not the HDMI/DP outputs connected to
> your secondary device. They are the ones connected to your primary
> device (might not be pinned out, or might only be available via an
> optional dock). Normally there'd be an extra -1- in the name of such
> outputs. But
https://bugs.freedesktop.org/show_bug.cgi?id=99400
Olivier Fourdan changed:
What|Removed |Added
Summary|[nouveau] garbled rending |[nouveau] garbled
https://bugs.freedesktop.org/show_bug.cgi?id=99400
--- Comment #2 from Ilia Mirkin ---
Not that it's of much consolation, but the nv30 GL driver sucks. There are a
number of unhandled situations, and I wouldn't be overly surprised if glamor
were to hit one or several of
On Fri, Jan 13, 2017 at 10:11 AM, Sylvain Fabre wrote:
> xrandr --setprovideroutputsource 1 0 seems to do nothing, either with a
> monitor connected to HDMI-1 or not. The second monitor is detected and
> available in the screen configuration tool of KDE, but it remains
https://bugs.freedesktop.org/show_bug.cgi?id=99400
--- Comment #4 from Ilia Mirkin ---
(In reply to Olivier Fourdan from comment #3)
> (In reply to Ilia Mirkin from comment #2)
> > Not that it's of much consolation, but the nv30 GL driver sucks. There are a
> > number of
Le vendredi 13 janvier 2017, 10:35:49 CET Ilia Mirkin a écrit :
>
> OK. So it sees the monitor, and detects its modes. Can you confirm
> that these are *not* listed in xrandr? In your original xrandr paste,
> the DP-1/HDMI-1 connectors were listed as disconnected. Perhaps you
> ran that xrandr
https://bugs.freedesktop.org/show_bug.cgi?id=99400
--- Comment #3 from Olivier Fourdan ---
(In reply to Ilia Mirkin from comment #2)
> Not that it's of much consolation, but the nv30 GL driver sucks. There are a
> number of unhandled situations, and I wouldn't be overly
17 matches
Mail list logo