Bug#761163: libgl1-mesa-dri: DRI3 causes error messages on i915 driver

2014-09-11 Thread Erich Schubert
Package: libgl1-mesa-dri Version: 10.3.0~rc3-1 Severity: minor Any application using libGL will report the following errors to stderr: libGL error: Version 4 or later of flush extension not found libGL error: failed to load driver: i915 The reason is that the i915 driver does not support DRI3 (y

Bug#761182: xserver-xorg-video-nouveau: NV94: screen black after resume from S3, floods of kernel errors

2014-09-11 Thread Zack Weinberg
Package: xserver-xorg-video-nouveau Version: 1:1.0.11-1 Severity: important After resume from S3, the monitor does not turn back on and there are floods of "PGRAPH" error messages in the kernel log. The OS is otherwise functional (one can ssh in, for instance) but an attempt to reboot hangs indef

Bug#761182: xserver-xorg-video-nouveau: NV94: screen black after resume from S3, floods of kernel errors

2014-09-11 Thread Sven Joachim
On 2014-09-11 15:34 +0200, Zack Weinberg wrote: > Package: xserver-xorg-video-nouveau > Version: 1:1.0.11-1 > Severity: important > > After resume from S3, the monitor does not turn back on and there are > floods of "PGRAPH" error messages in the kernel log. The OS is otherwise > functional (one

Processed: Bug#758217: xserver-xorg-video-nouveau: Nvidia card no more listed in 'xrandr --listproviders' on Optimus laptop

2014-09-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 758217 https://bugs.freedesktop.org/show_bug.cgi?id=74692 Bug #758217 [xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: Nvidia card no more listed in 'xrandr --listproviders' on Optimus laptop Set Bug forwarded-to-address to 'ht

Bug#757982: xserver segmentation fault

2014-09-11 Thread repron
Dnia 9 września 2014 5:13 Michel Dänzer napisał(a): > On 08.09.2014 20:32, repron wrote: > > > Last several freezes of Xorg, coused that Xorg.o.log file ended > > > suddenly,> without SIGSEGV. > > I am still trying to reproduce exactly the same state of "freeze" as> > > mentioned in the bug. >