[Touch-packages] [Bug 1576784] Re: MatchIsTouchscreen also matches touchpads in 16.04

2016-05-11 Thread machrider
I'm seeing the same problem with my Dell touchpad since upgrading to
16.04. /proc/bus/input/devices shows my touchpad as:

I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input5
U: Uniq=
H: Handlers=mouse0 event6 
B: PROP=5
B: EV=b
B: KEY=e520 1 0 0 0 0
B: ABS=66080001103

The touchscreen is:

I: Bus=0003 Vendor=06cb Product=1ac3 Version=0111
N: Name="SYNAPTICS Synaptics Large Touch Screen"
P: Phys=usb-:00:14.0-6/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/0003:06CB:1AC3.0001/input/input14
U: Uniq=
H: Handlers=mouse1 event13 
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 0 0
B: ABS=2608003

Previously MatchIsTouchscreen only matched my touchscreen, but now it's
matching the touchpad, too.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1576784

Title:
  MatchIsTouchscreen also matches touchpads in 16.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Previously in 15.10 I had the following rule in 
/usr/share/X11/xorg.conf.d/99-no-touchscreen.conf:
  Section "InputClass"
  Identifier "Touchscreen disable"
  MatchIsTouchscreen "on"

  Option "Ignore" "on"
  EndSection

  This worked in disabling the touchpad on my lenovo T440s

  After the upgrade to 16.04 I noticed that my touchpad would not work. And I 
found the following lines in the log:
  [  3107.956] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad 
(/dev/input/event6)
  [  3107.956] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass 
"Touchscreen disable"
  [  3107.956] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad 
(/dev/input/mouse0)
  [  3107.956] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass 
"Touchscreen disable"

  So I had to disable the rule in order to be able to use the touchpad,
  and now  I can't disable the touchscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Apr 29 09:39:23 2016
  InstallationDate: Installed on 2015-03-18 (407 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576784/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1290847] Re: pyvenv fails due to mising ensurepip module

2014-08-13 Thread machrider
Anyone know if and when this fix is planned to be backported to trusty
(i.e. the current Ubuntu release)? There doesn't seem to be any
information in this bug report to indicate one way or the other. I
actually don't even know which version of the python3.4 package fixes
it. (Isn't that something bug trackers normally track?)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1290847

Title:
  pyvenv fails due to mising ensurepip module

Status in “python3-defaults” package in Ubuntu:
  Fix Released
Status in “python3.4” package in Ubuntu:
  Fix Released
Status in “python3.4” package in Debian:
  Fix Released

Bug description:
  Hello,

  I noticed the following

  # fails
  python3.4 -m venv --clear python-venv
  Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 
'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1

  # works, but no pip
  python3.4 -m venv --clear --without-pip python-venv

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp