Bug#632772: KDE refuses to remember display resolution settings

2011-07-20 Thread T Elcor
Spoke too soon, after a reboot it became clear that the second issue is still unresolved, that is: KDE refuses to remember display resolution settings: I set it to 1600x1200 and click the "Save as Default" button, yet after logging out (and hanging and resetting, see #1 above) KDE reverts to 12

xdm: Changes to 'debian-unstable'

2011-07-20 Thread Julien Cristau
debian/changelog |1 + debian/control |2 +- 2 files changed, 2 insertions(+), 1 deletion(-) New commits: commit f5e7abe4435674ba87910e3deab394a243da329d Author: Julien Cristau Date: Wed Jul 20 20:46:18 2011 +0200 Use linux-any wildcard for libselinux build-dep (closes: #634466)

Processed: tagging 598777, tagging 634466

2011-07-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 598777 + pending Bug #598777 [xdm] [INTL:da] Danish translation of the debconf templates xdm Added tag(s) pending. > tags 634466 + pending Bug #634466 [xdm] xdm: debian/control uses hardcoded list of non-Linux architectures Added tag(s) pend

xserver-xorg-input-joystick: Changes to 'debian-unstable'

2011-07-20 Thread Julien Cristau
debian/changelog |6 ++ debian/control |2 +- 2 files changed, 7 insertions(+), 1 deletion(-) New commits: commit c142949988d9067b17e7af434061f6ff4371939a Author: Julien Cristau Date: Wed Jul 20 20:52:19 2011 +0200 Use kfreebsd-any wildcard for libusbhid build-dep (closes: #

Processed: limit source to xserver-xorg-input-joystick, tagging 634707

2011-07-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > #xserver-xorg-input-joystick (1:1.6.0-2) UNRELEASED; urgency=low > # > # * Use kfreebsd-any wildcard for libusbhid build-dep (closes: #634707). > # > limit source xserver-xorg-input-joystick Limiting to bugs with field 'source' containing at leas

libxtst: Changes to 'refs/tags/libxtst-2_1.2.0-3'

2011-07-20 Thread Cyril Brulebois
Tag 'libxtst-2_1.2.0-3' created by Cyril Brulebois at 2011-07-20 21:11 + Tagging upload of libxtst 2:1.2.0-3 to unstable. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEABECAAYFAk4nRIcACgkQeGfVPHR5Nd20pACgrK+Gsq1ABmtP1ZCUC+cxOLtb RSUAoJ1iK8V+6kVcLN7/ZT68gekKIWpb =5Guc

libxtst: Changes to 'debian-unstable'

2011-07-20 Thread Cyril Brulebois
debian/changelog | 14 ++ debian/control | 10 +- debian/libxtst6-udeb.install |1 + debian/rules |2 +- 4 files changed, 25 insertions(+), 2 deletions(-) New commits: commit ab768430a7e9abc5f8237e8a654b8cea47a11899 Author:

Processing of libxtst_1.2.0-3_amd64.changes

2011-07-20 Thread Debian FTP Masters
libxtst_1.2.0-3_amd64.changes uploaded successfully to localhost along with the files: libxtst_1.2.0-3.dsc libxtst_1.2.0-3.diff.gz libxtst6_1.2.0-3_amd64.deb libxtst6-udeb_1.2.0-3_amd64.udeb libxtst6-dbg_1.2.0-3_amd64.deb libxtst-dev_1.2.0-3_amd64.deb Greetings, Your Debian qu

libxtst_1.2.0-3_amd64.changes ACCEPTED into unstable

2011-07-20 Thread Debian FTP Masters
Accepted: libxtst-dev_1.2.0-3_amd64.deb to main/libx/libxtst/libxtst-dev_1.2.0-3_amd64.deb libxtst6-dbg_1.2.0-3_amd64.deb to main/libx/libxtst/libxtst6-dbg_1.2.0-3_amd64.deb libxtst6-udeb_1.2.0-3_amd64.udeb to main/libx/libxtst/libxtst6-udeb_1.2.0-3_amd64.udeb libxtst6_1.2.0-3_amd64.deb

Bug#617763: possible fix... regarding #629207, #629310, #631284, #617763

2011-07-20 Thread Sven Hartge
Michael Schmitt wrote: > I had a brief conversation about that issue with a develeoper of compiz > on IRC (#compiz@freenode): > 14:54:12 you can cite: 'A simple recompile of the > compiz(-gnome) package should be sufficient to get things in order again' > He could confirm the bug, tried to

Re: handling proprietary vendor libs for OpenGL ES [Was: implement gles-alternatives like glx-alternatives]

2011-07-20 Thread Christopher James Halse Rogers
On Mon, 2011-07-18 at 13:50 +0200, Heiko Stübner wrote: > Hi, > > short summary for debian-x: > It seems that also on embedded systems vendors start shipping proprietary > graphics drivers and OpenGL ES implementations like NVidia and AMD do for x86. > Therefore I talked to Andreas on what would