Processing of xterm_324-2_source.changes
xterm_324-2_source.changes uploaded successfully to ftp-master.debian.org along with the files: xterm_324-2.dsc xterm_324-2.diff.gz Greetings, Your Debian queue daemon (running on host coccia.debian.org)
Processing of xterm_324-2_source.changes
xterm_324-2_source.changes uploaded successfully to localhost along with the files: xterm_324-2.dsc xterm_324-2.diff.gz Greetings, Your Debian queue daemon (running on host franck.debian.org)
xterm_324-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 08 May 2016 08:32:18 +0200 Source: xterm Binary: xterm Architecture: source Version: 324-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Sven Joachim Description: xterm - X terminal emulator Changes: xterm (324-2) unstable; urgency=medium . * Enable all hardening options. * Remove the menu file (see #741573). * Add libxinerama-dev to Build-Depends. * Update copy of XTerm FAQ to revision 1.317 (dated 2016/03/21). * Bump Standards-Version to 3.9.8. Checksums-Sha1: 5b0be426472bc16baa76b154894e450dff1bea4a 2072 xterm_324-2.dsc 2abb73de64550fc7359ca3c581a351613318464d 108120 xterm_324-2.diff.gz Checksums-Sha256: a2f0d552a2b01976114e436c6b80325f373e8521363cf4830021375b7b033480 2072 xterm_324-2.dsc 5570cb00d32dc48d79205932586803b6af15d4d3d0e5cfbcd3558dc04727a24f 108120 xterm_324-2.diff.gz Files: 4e89df60da3da1bd300a05f34bc2d98d 2072 x11 optional xterm_324-2.dsc 36042a2b83f5659db3df4b235f3e94f4 108120 x11 optional xterm_324-2.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJXLt3bAAoJEDsQbnGNazGsIwkP/1HXsNSgzCLpHgF7zrXWthR4 XI+18yT8vOtZslE1ylpAMFUFcpmwwzeBDJSqlorgbKdySR+/VaJcFMePapxlO6kV 7lq9s0OpW/wDe099YDds9VOyVSOxVFyVj9gzM+SSsBxggDMZ5PwDBEeBcIUuD1gj o+eCunslD6FQFewcpmHkHW0XqrBsmwGPdcV41jVP+sZGiFXCCbAk0gBfU7JwqLRF AvjJ7dcYEOtNQyijd7q518smlvXeOmJ0QPDOW5XZ1uZr42oepBqXVfOydRvUYegU BZc3EYCVLgj2C3tVnk/4Ct24xB4/hszapPiGpItd+ABifVbt6QVnGeDvcEqjLaeQ PYRUtHvcIAwW6nHMqzWvatmiUtZHEQpcceorB+exf2aP1pP4Lq9joU/L1O453iUb bYSy65QPjLvPoxAJCc0a5cFROMYauqwr6ztNGPAxYEJAcyl3UWKAJErLnknUoPxl EuGop5Fej2xAommi9QNV+3eakxg/dHEW2ahJJxQlMbCmSoKs3JC/KGXvyeFbfGyW 40bPWKNDDfW/zhNCvOjjZ1fiV2j4Y2cyB6m6r8V18Urho1EbDAMSRCUsldj1YOul tYnlwdb/G/q3WpQ34rNaJXx4AtWBVe3E6e+xLI3JKQI9oBZfm2IxY3i46etzDyKu 60stWdf/hqQ3LJKiPU7m =9sdq -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#822486: xserver-xorg: Synaptic driver stopped working.
On 30 April 2016 at 18:06, Julien Cristau wrote: > On Sat, Apr 30, 2016 at 12:09:17 +0100, Steven Price wrote: > > The mouse configuration > > (System->Preferences->Hardware->Mouse in Mate) doesn't have the touchpad tab > > like it used to. > > > > Is there now some other way of configuring the touchpad with the new > > xserver- > > xorg-input-libinput package? > > > There are some config options that can be set either through > xorg.conf(5) or xinput(1), see libinput(4). Thanks, but this still seems like a regression. Previously I was able to change the settings through the GUI in Mate (the touchpad tab in 'Mouse' settings) and these settings are per-user. I don't currently have an xorg.conf (the defaults work fine for everything else) and xinput is obviously only a temporary change. I'm not sure which package is wrong here, but either Mate needs to be updated to support the new libinput way of doing things, or xorg-input-libinput needs to support the synaptics configuration methods. For now I've just reverted xserver-xorg-input-all to allow me to uninstall xorg-input-libinput which gets everything working as expected. Cheers, Steve
Bug#822486: xserver-xorg: Synaptic driver stopped working.
On Sun, May 8, 2016 at 14:09:56 +0100, Steven Price wrote: > On 30 April 2016 at 18:06, Julien Cristau wrote: > > On Sat, Apr 30, 2016 at 12:09:17 +0100, Steven Price wrote: > > > The mouse configuration > > > (System->Preferences->Hardware->Mouse in Mate) doesn't have the touchpad > > > tab > > > like it used to. > > > > > > Is there now some other way of configuring the touchpad with the new > > > xserver- > > > xorg-input-libinput package? > > > > > There are some config options that can be set either through > > xorg.conf(5) or xinput(1), see libinput(4). > > Thanks, but this still seems like a regression. Previously I was able > to change the settings through the GUI in Mate (the touchpad tab in > 'Mouse' settings) and these settings are per-user. > > I don't currently have an xorg.conf (the defaults work fine for > everything else) and xinput is obviously only a temporary change. I'm > not sure which package is wrong here, but either Mate needs to be > updated to support the new libinput way of doing things, or > xorg-input-libinput needs to support the synaptics configuration > methods. For now I've just reverted xserver-xorg-input-all to allow me > to uninstall xorg-input-libinput which gets everything working as > expected. > Yes, mate needs to be updated to know about xf86-input-libinput settings. Cheers, Julien
Bug#823777: libinput10: Scroll wheel emulation is on by default, with no apparent way to turn it off
Package: libinput10 Version: 1.2.4-1 Severity: normal Tags: upstream My system is a Thinkpad with a trackpoint device. I updated my X server using apt, and when I tried using Blender I discovered I could no longer use my middle mouse button as such. Scroll wheel events were being generated instead. I was unable to find anything in /usr/share/X11/xorg.conf.d that was activating scroll wheel emulation, and my efforts to disable scroll wheel emulation using xorg.conf.d (by adding 'Option "EmulateWheel" "off"' to various files where pointer device classes were being set up) failed to be effective. >From an online search for the problem it seems that this is a design choice built into libinput. Apparently it can be disabled by running xinput but not permanently via configuration files. From the libinput docs on "Scrolling": "On-button scrolling is enabled by default for pointing sticks. This prevents middle-button dragging; all motion events while the middle button is down are converted to scroll events." It can be disabled by this call to xinput: xinput --set-prop 'TPPS/2 IBM TrackPoint' 'libinput Button Scrolling Button' 0 Placing that call in .xsessionrc solves the immediate problem and allows me to use Blender effectively on my laptop again. But I'd like this setting to be system-wide. I recognize that for many users, having middle-button scroll wheel emulation is probably way more useful than a middle mouse button, but for me the opposite is true. Whatever default is chosen, this should be configurable at the system level and visible in xorg.conf.d. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libinput10 depends on: ii libc6 2.22-7 ii libevdev2 1.4.6+dfsg-1 ii libmtdev1 1.1.5-1 ii libudev1 229-5 ii libwacom2 0.18-1 libinput10 recommends no packages. libinput10 suggests no packages. -- no debconf information
Bug#823286: xserver-xorg-input-libinput: Significant functional regressions for touchapds vs. xserver-xorg-input-synaptics
Package: xserver-xorg-input-libinput Followup-For: Bug #823286 Hello, seems like this problem bothers a lot of people (if you google there are a lot of forum threads about this). Mostly because this change happened without notification and everyone's confused. There should've been a warning during the installation that the synaptics driver will be replaced and the configs won't work anymore. Or better: Import the existing configs. But doing it without is pretty annoying. Also no tool out there seems to recognize the new drivers so you can't create new setting. Maybe you could manually but also all manuals are outdated now and there is no valid information available (at least not the manuals I found, like the debian wiki). Seems like everyone got shot between the eyes. The most common approach I found is to uninstall the xserver-xorg-input packages. But that might have side effects. Also I don't think that was the intended reaction. -- System Information: Debian Release: 8.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 2.6.32-042stab113.21 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#823286: xserver-xorg-input-libinput: Significant functional regressions for touchapds vs. xserver-xorg-input-synaptics
On Sun, 08 May 2016 23:08:18 +0200 Julian wrote: > Package: xserver-xorg-input-libinput > Followup-For: Bug #823286 > > > Hello, > > seems like this problem bothers a lot of people (if you google there are a lot of forum threads about this). Mostly because this change happened without notification and everyone's confused. There should've been a warning during the installation that the synaptics driver will be replaced and the configs won't work anymore. Or better: Import the existing configs. But doing it without is pretty annoying. > Also no tool out there seems to recognize the new drivers so you can't create new setting. Maybe you could manually but also all manuals are outdated now and there is no valid information available (at least not the manuals I found, like the debian wiki). Seems like everyone got shot between the eyes. > The most common approach I found is to uninstall the xserver-xorg-input packages. But that might have side effects. Also I don't think that was the intended reaction. > > > -- System Information: > Debian Release: 8.4 > APT prefers stable > APT policy: (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 2.6.32-042stab113.21 (SMP w/1 CPU core) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: sysvinit (via /sbin/init) > > The big issue here is that the libinput driver is limited compared to evdev/synaptics, some features found in evdev are not available in it (i had constant decelaration set and working fine, but in libinput i saw no such option and couldnt set the pointer speed to the old value via xset). The touchpad was neuthered, the hardware buttons weren't even working at all. Why adopt a new driver when it is inferior to the old one??