Public bug reported:
Binary package hint: xserver-xorg-input-evdev
Ubuntu 9.04/8.10 and probably other.
The NextWindow touch screen is used on the HP TouchSmart systems however
doesn't work out of the box on 8.10 or 9.04.
Firstly it is allocated to a synaptic touchpad driver initially which is
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27042157/Dependencies.txt
** Attachment added: "LsHal.txt"
http://launchpadlibrarian.net/27042158/LsHal.txt
** Attachment added: "LsMod.txt"
http://launchpadlibrarian.net/27042160/LsMod.txt
** Attachment added: "LsPc
hey all,
just did a fresh install of lucid (32bit) and touch screen is working
out of the box.
According to above message i should probably close it but not sure if i
should as others are still having problems.
relevant dmesg:
[2.498018] input: NextWindow Touchscreen as
/devices/pci:00
** Attachment added: "lshal.txt"
http://launchpadlibrarian.net/48240333/lshal.txt
--
Handling NextWindow Touchscreen (multitouch)
https://bugs.launchpad.net/bugs/379313
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
/proc/bus/input/devices confirms that the device registers as NextWindow
Touchscreen
** Attachment added: "devices.txt"
http://launchpadlibrarian.net/30878956/devices.txt
--
Handling NextWindow Touchscreen (multitouch)
https://bugs.launchpad.net/bugs/379313
You received this bug notification
1926:003 is a device
** Attachment added: "lsusb.txt"
http://launchpadlibrarian.net/30878913/lsusb.txt
--
Handling NextWindow Touchscreen (multitouch)
https://bugs.launchpad.net/bugs/379313
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
dmesg (though older attached above)
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/30879137/dmesg.txt
--
Handling NextWindow Touchscreen (multitouch)
https://bugs.launchpad.net/bugs/379313
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I can confirm on hardy (haven't tried on jaunty) that evdev and evtouch
can cooperate however the 11-x11-synaptics.fdi is assumed to be the
driver.
I've also been using a different touchscreen on a different machine and
used the same technique to fix it (see patch), so i was thinking that
perhaps
Stuart: I think that's a really bad idea and is going to have each of
the clients trying to manage each of the distribution's system wide CAs
- and it really only handles the case where you are actually using the
system CAs. If you are using pip it seems unlikely you want to do that.
As a work aro
** Changed in: requests-mock
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535162
Title:
Doesn't work with the debian requests package.
To manage notifications about
Subscribed the ubuntu package maintainers of both requests and requests-
mock for there opinions.
** Also affects: python-requests-mock (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
We can't as an upstream python project start looking for CA certs from
an operating system. When installing from apt you will get the correct
behaviour, if you install from pip you will get the 'correct' python
behaviour.
This is a requests library issue.
** Changed in: python-keystoneclient
@Dolph: This would appear to me to be a keystone issue or possibly swift
should be doing gettext before importing the middleware. There are no
gettext translations in the client.
The exception here is coming from keystone - Swift should update to use
s3token from keystoneclient now that has been r
13 matches
Mail list logo
