Processed: your mail

2013-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: severity 690081 grave Bug #690081 [libwayland0] libwayland0:i386 and libwayland0:amd64 are conflicting, blocking multiarch gtk2.0 installation Severity set to 'grave' from 'wishlist' tag 690081 +experimental Bug #690081 [libwayland0]

Bug#612836: xserver-xorg: keyboard input is duplicated on virtual (text) terminal in dual seat configuration

2013-03-19 Thread Sergey Spiridonov
I found workaround for this problem. I do not get duplicated input anymore in Wheezy with gdm from Squeeze and with option Option GrabDevice True added to every evdev keyboard section. Thanks It must go into multiseat howto here: http://wiki.debian.org/Multi_Seat_Debian_HOWTO -- Best

xorg-server: Changes to 'ubuntu'

2013-03-19 Thread Maarten Lankhorst
debian/changelog |7 debian/control |1 debian/patches/drm_device_keep_trying.patch |8 debian/patches/os-use-libunwind-to-generate-backtraces.patch | 206 +++

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

2013-03-19 Thread Timo Aaltonen
ChangeLog| 946 NEWS | 38 configure.ac |2 debian/changelog |2 src/intel_driver.c |4 src/intel_driver.h | 18 src/intel_module.c |4

xserver-xorg-video-intel: Changes to 'upstream-experimental'

2013-03-19 Thread Timo Aaltonen
NEWS | 38 configure.ac |2 src/intel_driver.c |4 src/intel_driver.h | 18 src/intel_module.c |4 src/sna/Makefile.am |2 src/sna/compiler.h | 13 src/sna/gen2_render.c|

xserver-xorg-video-intel: Changes to 'ubuntu'

2013-03-19 Thread Timo Aaltonen
ChangeLog| 946 NEWS | 38 configure.ac |2 debian/changelog | 15 src/intel_driver.c |4 src/intel_driver.h | 18 src/intel_module.c |4

Bug#690081: Processed: your mail

2013-03-19 Thread Julien Cristau
Control: severity 690081 wishlist On Tue, Mar 19, 2013 at 08:45:13 +, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: severity 690081 grave Bug #690081 [libwayland0] libwayland0:i386 and libwayland0:amd64 are conflicting, blocking multiarch gtk2.0

Processed: Re: Processed: your mail

2013-03-19 Thread Debian Bug Tracking System
Processing control commands: severity 690081 wishlist Bug #690081 [libwayland0] libwayland0:i386 and libwayland0:amd64 are conflicting, blocking multiarch gtk2.0 installation Severity set to 'wishlist' from 'grave' -- 690081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690081 Debian Bug

Bug#690081: Processed: your mail

2013-03-19 Thread Erich Schubert
Control: severity 690081 grave No, this bug is in no way grave. Sure it is, by definition of grave: http://www.debian.org/Bugs/Developer#severities grave makes the package in question unusable or mostly so [...] The package is *unusable* (as in: *uninstallable*) on multiarch. This

Processed: Re: Processed: your mail

2013-03-19 Thread Debian Bug Tracking System
Processing control commands: severity 690081 grave Bug #690081 [libwayland0] libwayland0:i386 and libwayland0:amd64 are conflicting, blocking multiarch gtk2.0 installation Severity set to 'grave' from 'wishlist' -- 690081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690081 Debian Bug

Bug#690081: Processed: your mail

2013-03-19 Thread Julien Cristau
On Tue, Mar 19, 2013 at 19:57:17 +0100, Erich Schubert wrote: Control: severity 690081 grave No, this bug is in no way grave. Sure it is, by definition of grave: http://www.debian.org/Bugs/Developer#severities grave makes the package in question unusable or mostly so [...]

Processed: severity of 690081 is wishlist

2013-03-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: # stop fucking with my bugs kthxbye severity 690081 wishlist Bug #690081 [libwayland0] libwayland0:i386 and libwayland0:amd64 are conflicting, blocking multiarch gtk2.0 installation Severity set to 'wishlist' from 'grave' thanks Stopping

Bug#703291: [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang

2013-03-19 Thread Sven Joachim
On 2013-03-18 22:44 +0100, Guy Heatley wrote: Sven - I can confirm that your downgrading suggestion fixes this problem. On 18/03/13 17:03, Sven Joachim wrote: Kernel folks, this appears to be a regression resulting from the DRM 3.4 backport. Can you confirm that downgrading