Bug#678621: xserver-xorg-video-radeon: Unable to set native resolution

2012-06-23 Thread Michel Dänzer
On Sam, 2012-06-23 at 12:57 +0200, Per Blomqvist wrote: 
> 
> After an system update, the radeon -driver doesn’t support 1280x1024
> resolution.

What exactly changed during the system update? In particular, which
version of the kernel and xserver-xorg-video-radeon were you running
before and afterwards?


> Also, maybe another bug though, I tested to change "DefaultDepth24", 
> to
> 32.

Depth 32 isn't supported by the radeon driver, as it can't make any use
of the additional bits. Depth 24 uses 32 bits of storage for each pixel.


> That apparently froze my system (afterward 100++ logfiles).

That's a gdm3 bug, which should be fixed in gdm3 3.4.


> [   286.097] (II) RADEON(0): Output VGA-0 using monitor section JT198x4
[...] 
> [   286.377] (II) RADEON(0): EDID for output VGA-0
> [   286.377] (II) RADEON(0): Printing probed modes for output VGA-0
> [   286.377] (II) RADEON(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 
> 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
> [   286.377] (II) RADEON(0): Modeline "800x600"x60.3   40.00  800 840 968 
> 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
> [   286.377] (II) RADEON(0): Modeline "800x600"x56.2   36.00  800 824 896 
> 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
> [   286.377] (II) RADEON(0): Modeline "848x480"x60.0   33.75  848 864 976 
> 1088  480 486 494 517 +hsync +vsync (31.0 kHz e)
> [   286.377] (II) RADEON(0): Modeline "640x480"x59.9   25.18  640 656 752 800 
>  480 489 492 525 -hsync -vsync (31.5 kHz e)

Looks like the monitor connected to the VGA output is providing an EDID
specifying 1024x768 as the maximum resolution.

You might be able to override this though, either by adding a ModeLine
for "1280x1024" in Section "Monitor" or at runtime using the xrandr
utility.


> [   286.626] (**) RADEON(0): Display dimensions: (1280, 1024) mm
> [   286.626] (**) RADEON(0): DPI set to (20, 19)

Probably not directly related to your problem, but these are pretty
weird settings you're specifying in xorg.conf...

Have you tried without any xorg.conf?


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast |  Debian, X and DRI developer



--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1340449671.8260.40.camel@thor.local



Bug#678632: xserver-xorg-video-radeon: Unable to set native resolution

2012-06-23 Thread Julien Cristau
On Sat, Jun 23, 2012 at 13:36:34 +0200, root wrote:

> Section "Monitor"
>   Identifier  "JT198x4"
>   Option  "DPMS"
>   DisplaySize 1280 1024
> EndSection
> 
Is your monitor really 1280x1024 millimeters?

Cheers,
Julien


signature.asc
Description: Digital signature


Re: Processed: tagging as pending bugs that are closed by packages in NEW

2012-06-23 Thread Julien Cristau
On Fri, Jun 22, 2012 at 08:09:10 +, Debian Bug Tracking System wrote:

> Processing commands for cont...@bugs.debian.org:
> 
> > # Friday 22 June  08:03:52 UTC 2012
> > # Tagging as pending bugs that are closed by packages in NEW
> > # http://ftp-master.debian.org/new.html
> > #
[...]
> > # Source package in NEW:  > href="http://packages.qa.debian.org/libdrm";>libdrm
> > tags 667572 + pending
> Bug #667572 {Done: Julien Cristau } [src:libdrm] libdrm: 
> please provide OMAP API on armel and armhf
> Added tag(s) pending.
> >

libdrm source is *not* in NEW.  Please fix your script to ignore
non-source packages in NEW.

Cheers,
Julien


signature.asc
Description: Digital signature


Bug#656719: ln: failed to create symbolic link `build/dri/i386-linux-gnu/gallium/XvMCConfig': File exists (was: Please provide xvmc and vdpau Gallium3D video acceleration drivers (libg3dvl-mesa packag

2012-06-23 Thread Paul Menzel
Am Samstag, den 23.06.2012, 00:06 +0200 schrieb Paul Menzel:
> Am Freitag, den 22.06.2012, 23:52 +0200 schrieb Cyril Brulebois:
> > Paul Menzel  (22/06/2012):
> > > So the build dependency should be on `llvm-dev` which pulls in `llvm`
> > > with `llvm-config` the configure script is looking for.
> > 
> > 13-llvm-config-pick-a-version.diff disagrees.
> 
> Interesting. `configure.ac` in my current build directory does not have
> that patch applied. So it could be a result of the option `-nc`
> 
> $ dpkg-buildpackage -us -uc -B -j2 -nc
> 
> which does not clean the directory before the build again. But all
> patches from `debian/patches` should have been applied.
> 
> But I do not know and this is just a guess. I will try to reproduce the
> issue tomorrow and clean the working directory before. Using
> `llvm-2.9-dev` could also fix the build error I got.

Ok, although I always used `dpkg-buildpackage` with `-nc` something went
wrong.

$ LANG= dpkg-buildpackage -us -uc -B -j2
dpkg-buildpackage: source package mesa
dpkg-buildpackage: source version 8.0.3-2
dpkg-buildpackage: source changed by Timo 
dpkg-buildpackage: host architecture i386
 dpkg-source --before-build mesa
 fakeroot debian/rules clean
QUILT_PATCHES=debian/patches \
quilt --quiltrc /dev/null pop -a -R || test $? = 2
Patch 13-llvm-config-pick-a-version.diff does not remove cleanly 
(refresh it or enforce with -f)
make: *** [unpatch] Error 1
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit 
status 2

Thinking about it, I did `git reset --hard origin/debian-unstable`. That
probably reset the patched files too and `dpkg-buildpackage -n` does not
check that.

Manually fixing this by applying some patches manually,

$ debian/rules clean

worked and I started the next try. Running

$ dpkg-buildpackage -us -uc -B -j2

`configure.ac` was patched to pick up llvm-config-2.9 and the build
error, I reported, is gone now too, since llvm-2.9-dev is used instead
of llvm-3.1-dev.

I am still getting the following error. Hopefully resolving this, I will
get the packages.

$ dpkg-buildpackage -us -uc -B -j2
make[1]: Leaving directory `/opt/src/mesa/build/swx11+glu-i386-i686'
>debian/stamp/i486-linux-gnu-build-swx11+glu-i386-i686
>build-stamp
# XvMCConfig configuration file:
ln -s /etc/X11/XvMCConfig build/dri/i386-linux-gnu/gallium/XvMCConfig
 fakeroot debian/rules binary-arch
# XvMCConfig configuration file:
ln -s /etc/X11/XvMCConfig build/dri/i386-linux-gnu/gallium/XvMCConfig
ln: failed to create symbolic link 
`build/dri/i386-linux-gnu/gallium/XvMCConfig': File exists
make: *** [build] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error 
exit status 2

Removing that file does not help.

$ rm build/dri/i386-linux-gnu/gallium/XvMCConfig
$ dpkg-buildpackage -us -uc -B -j2 -nc
dpkg-buildpackage: source package mesa
dpkg-buildpackage: source version 8.0.3-2
dpkg-buildpackage: source changed by Timo 
dpkg-buildpackage: host architecture i386
 dpkg-source --before-build mesa
dpkg-buildpackage: warning: debian/rules must be updated to support the 
'build-arch' and 'build-indep' targets (at least 'build-arch' seems to be 
missing)
 debian/rules build
# XvMCConfig configuration file:
ln -s /etc/X11/XvMCConfig build/dri/i386-linux-gnu/gallium/XvMCConfig
 fakeroot debian/rules binary-arch
# XvMCConfig configuration file:
ln -s /etc/X11/XvMCConfig build/dri/i386-linux-gnu/gallium/XvMCConfig
ln: failed to create symbolic link 
`build/dri/i386-linux-gnu/gallium/XvMCConfig': File exists
make: *** [build] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error 
exit status 2

Any ideas? It is strange that the same output is there twice. Maybe this
is due to `-j2`?


Thanks,

Paul


signature.asc
Description: This is a digitally signed message part


Bug#656719: ln: failed to create symbolic link `build/dri/i386-linux-gnu/gallium/XvMCConfig': File exists

2012-06-23 Thread Paul Menzel
Am Samstag, den 23.06.2012, 13:43 +0200 schrieb Paul Menzel:
> Am Samstag, den 23.06.2012, 00:06 +0200 schrieb Paul Menzel:
> > Am Freitag, den 22.06.2012, 23:52 +0200 schrieb Cyril Brulebois:
> > > Paul Menzel  (22/06/2012):
> > > > So the build dependency should be on `llvm-dev` which pulls in `llvm`
> > > > with `llvm-config` the configure script is looking for.
> > > 
> > > 13-llvm-config-pick-a-version.diff disagrees.
> > 
> > Interesting. `configure.ac` in my current build directory does not have
> > that patch applied. So it could be a result of the option `-nc`
> > 
> > $ dpkg-buildpackage -us -uc -B -j2 -nc
> > 
> > which does not clean the directory before the build again. But all
> > patches from `debian/patches` should have been applied.
> > 
> > But I do not know and this is just a guess. I will try to reproduce the
> > issue tomorrow and clean the working directory before. Using
> > `llvm-2.9-dev` could also fix the build error I got.
> 
> Ok, although I always used `dpkg-buildpackage` with `-nc` something went
> wrong.
> 
> $ LANG= dpkg-buildpackage -us -uc -B -j2
> dpkg-buildpackage: source package mesa
> dpkg-buildpackage: source version 8.0.3-2
> dpkg-buildpackage: source changed by Timo 
> dpkg-buildpackage: host architecture i386
>  dpkg-source --before-build mesa
>  fakeroot debian/rules clean
> QUILT_PATCHES=debian/patches \
>   quilt --quiltrc /dev/null pop -a -R || test $? = 2
> Patch 13-llvm-config-pick-a-version.diff does not remove cleanly 
> (refresh it or enforce with -f)
> make: *** [unpatch] Error 1
> dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit 
> status 2
> 
> Thinking about it, I did `git reset --hard origin/debian-unstable`. That
> probably reset the patched files too and `dpkg-buildpackage -n` does not
> check that.
> 
> Manually fixing this by applying some patches manually,
> 
> $ debian/rules clean
> 
> worked and I started the next try. Running
> 
> $ dpkg-buildpackage -us -uc -B -j2
> 
> `configure.ac` was patched to pick up llvm-config-2.9 and the build
> error, I reported, is gone now too, since llvm-2.9-dev is used instead
> of llvm-3.1-dev.
> 
> I am still getting the following error. Hopefully resolving this, I will
> get the packages.
> 
> $ dpkg-buildpackage -us -uc -B -j2
> make[1]: Leaving directory `/opt/src/mesa/build/swx11+glu-i386-i686'
> >debian/stamp/i486-linux-gnu-build-swx11+glu-i386-i686
> >build-stamp
> # XvMCConfig configuration file:
> ln -s /etc/X11/XvMCConfig build/dri/i386-linux-gnu/gallium/XvMCConfig
>  fakeroot debian/rules binary-arch
> # XvMCConfig configuration file:
> ln -s /etc/X11/XvMCConfig build/dri/i386-linux-gnu/gallium/XvMCConfig
> ln: failed to create symbolic link 
> `build/dri/i386-linux-gnu/gallium/XvMCConfig': File exists
> make: *** [build] Error 1
> dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave 
> error exit status 2
> 
> Removing that file does not help.
> 
> $ rm build/dri/i386-linux-gnu/gallium/XvMCConfig
> $ dpkg-buildpackage -us -uc -B -j2 -nc
> dpkg-buildpackage: source package mesa
> dpkg-buildpackage: source version 8.0.3-2
> dpkg-buildpackage: source changed by Timo 
> dpkg-buildpackage: host architecture i386
>  dpkg-source --before-build mesa
> dpkg-buildpackage: warning: debian/rules must be updated to support 
> the 'build-arch' and 'build-indep' targets (at least 'build-arch' seems to be 
> missing)
>  debian/rules build
> # XvMCConfig configuration file:
> ln -s /etc/X11/XvMCConfig build/dri/i386-linux-gnu/gallium/XvMCConfig
>  fakeroot debian/rules binary-arch
> # XvMCConfig configuration file:
> ln -s /etc/X11/XvMCConfig build/dri/i386-linux-gnu/gallium/XvMCConfig
> ln: failed to create symbolic link 
> `build/dri/i386-linux-gnu/gallium/XvMCConfig': File exists
> make: *** [build] Error 1
> dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave 
> error exit status 2
> 
> Any ideas? It is strange that the same output is there twice. Maybe this
> is due to `-j2`?

It is not that. Using `-j1` also fails.

$ more debian/rules
[…]
build: build-stamp
# XvMCConfig configuration file:
ln -s /etc/X11/XvMCConfig 
build/dri/$(DEB_HOST_MULTIARCH)/gallium/XvMCConfig

Removing that `ln -s` line makes this error go away. I do not understand
how in the build `/etc/X11` of the build host seems to be used.
Especially since this file is already available in package `libxvmc1`.

$ dpkg -S /etc/X11/XvMCConfig
libxvmc1: /etc/X11/XvMCConfig

Any ideas what to do. Depend on `libxvmc1` and do not ship that file in
`libg3dvl-mesa`?

Now I get the next error.

  

Bug#678632: xserver-xorg-video-radeon: Unable to set native resolution

2012-06-23 Thread Per Blomqvist
Nope, its the max resolution, its removed now. Didn't affect the resolution.

On Sat, Jun 23, 2012 at 1:40 PM, Julien Cristau  wrote:
> On Sat, Jun 23, 2012 at 13:36:34 +0200, root wrote:
>
>> Section "Monitor"
>>       Identifier      "JT198x4"
>>       Option          "DPMS"
>>       DisplaySize     1280 1024
>> EndSection
>>
> Is your monitor really 1280x1024 millimeters?
>
> Cheers,
> Julien



-- 
Mvh, Per Blomqvist



--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAAdE4-faSQXQF7hTqc4+qdgLd=ajm5zmvz3rz8yahr-gq1v...@mail.gmail.com



Bug#677466: [xserver-xorg-video-intel] gnome3 energy saving hung GPU

2012-06-23 Thread Julian Andres Klode
On Thu, Jun 14, 2012 at 10:20:46AM +0200, Cyril Brulebois wrote:
> Riccardo Magliocchetti  (14/06/2012):
> > Package: xserver-xorg-video-intel
> > Version: 2:2.19.0-3
> > Severity: important
> > 
> > Hello,
> > 
> > when gnome3 blanks the screen the GPU hangs, this make the
> > gnome-shell crash and won't start again without a machine reboot. So
> > filing it as important. This looks like a regresion from 2.19.0-1 to
> > 2.19.0-3.
> 
> The changes between both should only be about option initialization, to
> make it possible to switch from UXA to SNA if one feels lucky. Are you
> sure you didn't switch kernels at the same time? Alternatively: if you
> downgrade, does the hang go away?

This bug is a regression from 

uxa: Only consider an output valid if the kernel reports it attached

and fixed in commit c4eb5528a456b65c673f7c984d14a622ac67cdca:

uxa: Check for DPMS off before scheduling a WAIT_ON_EVENT

Regression from commit 3f3bde4f0c72f6f31aae322bcdc20b95eade6631
Author: Chris Wilson 
Date:   Thu May 24 11:58:46 2012 +0100

uxa: Only consider an output valid if the kernel reports it attached

When backporting from SNA, a key difference that UXA does not track DPMS
state in its enabled flag and that a DPMS off CRTC is still bound to the
fb. So we do need to rescan the outputs and check that we have a
connector enabled *and* the pipe is running prior to emitting a scanline
wait.

References: https://bugs.freedesktop.org/show_bug.cgi?id=50668
Signed-off-by: Chris Wilson 

Please cherry-pick.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120623155457.ga15...@jak-linux.org



Bug#677466: [xserver-xorg-video-intel] gnome3 energy saving hung GPU

2012-06-23 Thread Cyril Brulebois
Julian Andres Klode  (23/06/2012):
> This bug is a regression from 
> 
> uxa: Only consider an output valid if the kernel reports it attached
> 
> and fixed in commit c4eb5528a456b65c673f7c984d14a622ac67cdca:

[…]

> Please cherry-pick.

Oh yay. Thanks.

Mraw,
KiBi.


signature.asc
Description: Digital signature


xserver-xorg-video-intel: Changes to 'debian-unstable'

2012-06-23 Thread Julien Cristau
 debian/changelog|8 
 src/intel_display.c |   15 +++
 2 files changed, 23 insertions(+)

New commits:
commit ab4c2c4dd666d7506829e1840b812d66af1d122c
Author: Julien Cristau 
Date:   Sat Jun 23 19:17:42 2012 +0200

Upload to unstable

diff --git a/debian/changelog b/debian/changelog
index 5bc9fe1..f23fe06 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+xserver-xorg-video-intel (2:2.19.0-4) unstable; urgency=medium
+
+  * uxa: Check for DPMS off before scheduling a WAIT_ON_EVENT.  Fixes
+regression from a cherry-pick in 2:2.19.0-2.  Thanks to Julian Andres
+Klode for tracking this down.
+
+ -- Julien Cristau   Sat, 23 Jun 2012 19:16:28 +0200
+
 xserver-xorg-video-intel (2:2.19.0-3) unstable; urgency=low
 
   * Add patch to avoid X segfaults with Driver-less Device sections in

commit 9b92aefec37b34044a9e12d01ccdadeb7e9853de
Author: Chris Wilson 
Date:   Tue Jun 5 16:04:16 2012 +0100

uxa: Check for DPMS off before scheduling a WAIT_ON_EVENT

Regression from commit 3f3bde4f0c72f6f31aae322bcdc20b95eade6631
Author: Chris Wilson 
Date:   Thu May 24 11:58:46 2012 +0100

uxa: Only consider an output valid if the kernel reports it attached

When backporting from SNA, a key difference that UXA does not track DPMS
state in its enabled flag and that a DPMS off CRTC is still bound to the
fb. So we do need to rescan the outputs and check that we have a
connector enabled *and* the pipe is running prior to emitting a scanline
wait.

References: https://bugs.freedesktop.org/show_bug.cgi?id=50668
Signed-off-by: Chris Wilson 
(cherry picked from commit c4eb5528a456b65c673f7c984d14a622ac67cdca)

diff --git a/src/intel_display.c b/src/intel_display.c
index 89f7259..75d4998 100644
--- a/src/intel_display.c
+++ b/src/intel_display.c
@@ -1703,13 +1703,28 @@ int intel_crtc_to_pipe(xf86CrtcPtr crtc)
 Bool intel_crtc_on(xf86CrtcPtr crtc)
 {
struct intel_crtc *intel_crtc = crtc->driver_private;
+   xf86CrtcConfigPtr xf86_config = XF86_CRTC_CONFIG_PTR(crtc->scrn);
drmModeCrtcPtr drm_crtc;
Bool ret;
+   int i;
 
if (!crtc->enabled)
return FALSE;
 
/* Kernel manages CRTC status based on output config */
+   ret = FALSE;
+   for (i = 0; i < xf86_config->num_output; i++) {
+   xf86OutputPtr output = xf86_config->output[i];
+   if (output->crtc == crtc &&
+   intel_output_dpms_status(output) == DPMSModeOn) {
+   ret = TRUE;
+   break;
+   }
+   }
+   if (!ret)
+   return FALSE;
+
+   /* And finally check with the kernel that the fb is bound */
drm_crtc = drmModeGetCrtc(intel_crtc->mode->fd, crtc_id(intel_crtc));
if (drm_crtc == NULL)
return FALSE;


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1siu2y-un...@vasks.debian.org



Bug#677444: xserver-xorg-video-intel: White screen/freeze on Intel HD Graphics 4000 when logging out of Gnome or KDE or switching to VT

2012-06-23 Thread Julien Cristau
On Wed, Jun 13, 2012 at 20:01:59 -0400, Robert A. Kelly III wrote:

> Package: xserver-xorg-video-intel
> Version: 2:2.13.0-6
> Severity: normal
> 
> 
> When logging out of Gnome or KDE or switching to VT, I get a white screen.
> Shortly after this, capslock and numlock quit responding and the system
> freezes completely.
> 
Note that according to the X log in your report, you're using the vesa
X driver, not intel.

Cheers,
Julien


signature.asc
Description: Digital signature


Bug#678621: xserver-xorg-video-radeon: Unable to set native resolution

2012-06-23 Thread Per Blomqvist

Hi Muchel, i submitted this bugreport twice (#678632 same).

On 06/23/2012 01:07 PM, Michel Dänzer wrote:

On Sam, 2012-06-23 at 12:57 +0200, Per Blomqvist wrote:

After an system update, the radeon -driver doesn’t support 1280x1024
resolution.

What exactly changed during the system update? In particular, which
version of the kernel and xserver-xorg-video-radeon were you running
before and afterwards?

Dono, scores of update. Kernel 3.2 lotz. Il use framebuffer in the 
console (set at bootup) 1024x780.



Also, maybe another bug though, I tested to change "DefaultDepth24", to
32.

Depth 32 isn't supported by the radeon driver, as it can't make any use
of the additional bits. Depth 24 uses 32 bits of storage for each pixel.



That apparently froze my system (afterward 100++ logfiles).

That's a gdm3 bug, which should be fixed in gdm3 3.4.



[   286.097] (II) RADEON(0): Output VGA-0 using monitor section JT198x4

[...]

[   286.377] (II) RADEON(0): EDID for output VGA-0
[   286.377] (II) RADEON(0): Printing probed modes for output VGA-0
[   286.377] (II) RADEON(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 
1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   286.377] (II) RADEON(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  
600 601 605 628 +hsync +vsync (37.9 kHz e)
[   286.377] (II) RADEON(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  
600 601 603 625 +hsync +vsync (35.2 kHz e)
[   286.377] (II) RADEON(0): Modeline "848x480"x60.0   33.75  848 864 976 1088  
480 486 494 517 +hsync +vsync (31.0 kHz e)
[   286.377] (II) RADEON(0): Modeline "640x480"x59.9   25.18  640 656 752 800  
480 489 492 525 -hsync -vsync (31.5 kHz e)

Looks like the monitor connected to the VGA output is providing an EDID
specifying 1024x768 as the maximum resolution.

You might be able to override this though, either by adding a ModeLine
for "1280x1024" in Section "Monitor" or at runtime using the xrandr
utility.


Tested ModeLine "1280x1024", X didnt start, 100++ logfiles again.




[   286.626] (**) RADEON(0): Display dimensions: (1280, 1024) mm
[   286.626] (**) RADEON(0): DPI set to (20, 19)

Probably not directly related to your problem, but these are pretty
weird settings you're specifying in xorg.conf...

Have you tried without any xorg.conf?




nope, have u?




--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4fe6105d.2030...@lsn.se



xserver-xorg-video-intel: Changes to 'debian-unstable'

2012-06-23 Thread Cyril Brulebois
 debian/changelog |7 ---
 1 file changed, 4 insertions(+), 3 deletions(-)

New commits:
commit 6f0873ac6f94e72aa93a2de15172e9f272c28133
Author: Cyril Brulebois 
Date:   Sat Jun 23 21:08:17 2012 +0200

Add bug closure, and really upload to unstable.

diff --git a/debian/changelog b/debian/changelog
index f23fe06..9c97d52 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,10 +1,11 @@
 xserver-xorg-video-intel (2:2.19.0-4) unstable; urgency=medium
 
+  [ Julien Cristau ]
   * uxa: Check for DPMS off before scheduling a WAIT_ON_EVENT.  Fixes
-regression from a cherry-pick in 2:2.19.0-2.  Thanks to Julian Andres
-Klode for tracking this down.
+regression from a cherry-pick in 2:2.19.0-2 (Closes: #677466).
+Thanks to Julian Andres Klode for tracking this down.
 
- -- Julien Cristau   Sat, 23 Jun 2012 19:16:28 +0200
+ -- Cyril Brulebois   Sat, 23 Jun 2012 21:06:26 +0200
 
 xserver-xorg-video-intel (2:2.19.0-3) unstable; urgency=low
 


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1sivv8-0007tf...@vasks.debian.org



xserver-xorg-video-intel: Changes to 'refs/tags/xserver-xorg-video-intel-2_2.19.0-4'

2012-06-23 Thread Cyril Brulebois
Tag 'xserver-xorg-video-intel-2_2.19.0-4' created by Cyril Brulebois 
 at 2012-06-23 19:08 +

Tagging upload of xserver-xorg-video-intel 2:2.19.0-4 to unstable.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEABECAAYFAk/mFCsACgkQeGfVPHR5Nd2LgACgmRlCNxYgSZKs6Oh9HmUoZYvs
BDkAoMC3nvTFPx0vYUvGZurL2HkWIxVh
=/kGw
-END PGP SIGNATURE-

Changes since xserver-xorg-video-intel-2_2.19.0-3:
Chris Wilson (1):
  uxa: Check for DPMS off before scheduling a WAIT_ON_EVENT

Cyril Brulebois (1):
  Add bug closure, and really upload to unstable.

Julien Cristau (1):
  Upload to unstable

---
 debian/changelog|9 +
 src/intel_display.c |   15 +++
 2 files changed, 24 insertions(+)
---


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1sivv9-0007te...@vasks.debian.org



Processing of xserver-xorg-video-intel_2.19.0-4_amd64.changes

2012-06-23 Thread Debian FTP Masters
xserver-xorg-video-intel_2.19.0-4_amd64.changes uploaded successfully to 
localhost
along with the files:
  xserver-xorg-video-intel_2.19.0-4.dsc
  xserver-xorg-video-intel_2.19.0-4.diff.gz
  xserver-xorg-video-intel_2.19.0-4_amd64.deb
  xserver-xorg-video-intel-dbg_2.19.0-4_amd64.deb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1sivyh-xv...@franck.debian.org



xserver-xorg-video-intel_2.19.0-4_amd64.changes ACCEPTED into unstable

2012-06-23 Thread Debian FTP Masters



Accepted:
xserver-xorg-video-intel-dbg_2.19.0-4_amd64.deb
  to 
main/x/xserver-xorg-video-intel/xserver-xorg-video-intel-dbg_2.19.0-4_amd64.deb
xserver-xorg-video-intel_2.19.0-4.diff.gz
  to main/x/xserver-xorg-video-intel/xserver-xorg-video-intel_2.19.0-4.diff.gz
xserver-xorg-video-intel_2.19.0-4.dsc
  to main/x/xserver-xorg-video-intel/xserver-xorg-video-intel_2.19.0-4.dsc
xserver-xorg-video-intel_2.19.0-4_amd64.deb
  to main/x/xserver-xorg-video-intel/xserver-xorg-video-intel_2.19.0-4_amd64.deb


Changes:
xserver-xorg-video-intel (2:2.19.0-4) unstable; urgency=medium
 .
  [ Julien Cristau ]
  * uxa: Check for DPMS off before scheduling a WAIT_ON_EVENT.  Fixes
regression from a cherry-pick in 2:2.19.0-2 (Closes: #677466).
Thanks to Julian Andres Klode for tracking this down.


Override entries for your package:
xserver-xorg-video-intel-dbg_2.19.0-4_amd64.deb - extra debug
xserver-xorg-video-intel_2.19.0-4.dsc - source x11
xserver-xorg-video-intel_2.19.0-4_amd64.deb - optional x11

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 677466 


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1siw4t-0001i7...@franck.debian.org