** Changed in: xserver-xorg-input-elographics (Ubuntu Hardy)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/218671
Title:
MinY MaxY leads to unexpected
1.3.2 has been in ubuntu for some time. Leaving open for hardy.
** Changed in: xserver-xorg-input-elographics (Ubuntu)
Status: Confirmed = Fix Released
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a
** Tags added: hardy
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
@Bryce
Yes, upon further reviewing the GIT upstream I did find that the fix was pre
1.2.3 and that it infact was fixed in a later release of the ubuntu package.
The issue was not corrected when i upgraded the package because it did not
erase the old module somehow. Once I manually removed the
@Bryce
Yes, upon further reviewing the GIT upstream I did find that the fix was pre
1.2.3 and that it in fact was fixed in a later release of the ubuntu package.
The issue was not corrected when i upgraded the package because it did not
erase the old module somehow. Once I manually removed the
Thanks Bryce. I don't think the driver is relevant although I need to
fix that too. Video playback at that that reoslution (26 screen) using
VESA is unusable. Both the touchscreen and resolution issues I am having
seem related although not identical to this bug, and none of the fixes
proposed here
On Thu, Apr 16, 2009 at 02:15:21PM -, Fabián Rodríguez wrote:
I have filed separate bugs for both:
* EloTouch 2639L touchscreen (input device) possibly not properly
recognized, XY axis inverted (Bug #362308)
* Intel integrated Graphics [8086:2e13] resolution not properly detected,
not
I am a bit puzzled that I removed all drivers and the touchscreen seems
to work out of the box in Hardy for me. The suggested patches, etc.
don't work for me. Here's my relevant ouput from cat
/proc/bus/input/devices:
I: Bus=0003 Vendor=04e7 Product=0020 Version=0100
N: Name=Elo TouchSystems,
[Fabian's log: http://pastebin.com/f61746dc6]
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Fabian's lspci:
00:02.0 VGA compatible controller: Intel Corporation Eaglelake Integrated
Graphics Controller (rev 03) (prog-if 00 [VGA controller])
Subsystem: Dell Unknown device 027f
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at fe80 (64-bit, non-prefetchable) [size=4M]
Fabian, just to make sure I understand, could you explain the issue
you're seeing? You said it was the same issue, but it is possible you
may have an unrelated bug, so it would be helpful to hear directly.
Also, if possible it would be helpful if you could test against jaunty,
which has a newer
@William, you mention that git upstream has fixed this issue, and that
the fix is not present in 1.2.3, however there is only one actual change
in git that is not in 1.2.3, Fix InputDriverRec allocation and freeing
which doesn't look like it affects coordinate swapping behavior. Please
elaborate
I've put a hardy build of the -elographics 1.2.3 that's in Jaunty in my
PPA:
https://edge.launchpad.net/~bryceharrington/+archive/ppa/
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs,
I've put together a new hardy package that includes three patches from
the newer upstream tree, that may help with the MinX/MinY issue, and are
worth testing. If this package solves the issue on hardy, it may be
reasonable to consider putting an SRU to include it as a hardy update.
So please test
Fabian, I notice you are on an Eaglelake video chipset, which is not
supported in the hardy version of -intel. You may want to try the 2.5
backport of the driver available from xorg-edgers, to see if that helps:
https://edge.launchpad.net/~xorg-edgers/+archive/ppa/+sourcepub/469034
Having the same issue with an Elo TouchSystems 2700 IntelliTouch(r) USB
Touchmonitor Interface (USB ID 04e7:0020).
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: xserver-xorg-input-elographics (Ubuntu)
Status: Incomplete = Confirmed
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
git master on freedesktop.org has fixed this issue. The issue still
resides inside release 1.2.3. To from git you will need to pull an
updated copy of xutils-dev source from launchpad and overwrite the xorg-
marcos.m4 overtop the installed one from xutils-dev in repo.
also, i tested anothe
Please, let me what else we can do to move this along!
Filing a report upstream would be a solid step you could do to help move things
along.
Once upstream accepts a patch, I tend to have a lot more confidence about
pulling it into Ubuntu as well.
--
MinY MaxY leads to unexpected behaviour
Thanks, Bryce. No, I am not sure at all whether this should go into
stables, I just thought you could judge it much better.
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Tue, Mar 3, 2009 at 11:38 PM, Bryce Harrington
br...@bryceharrington.org wrote:
Basically I agree with comment #10. This bug should go upstream for
review. I have a suspicion that there is something hardware-specific
about this bug, but unfortunately none of the many people who have
Bryce, can you please review this and upload to hardy/intrepid-
proposed, and make sure it gets into jaunty? It seems to be fixed
upstream in 1.2.2. Thanks!
Martin, are you certain this should be uploaded? This bug has a number
of irregularities...
1. Several patches are mentioned in this bug
Basically I agree with comment #10. This bug should go upstream for
review. I have a suspicion that there is something hardware-specific
about this bug, but unfortunately none of the many people who have
confirmed this issue have indicated what hardware they have, so it's
impossible to determine
[Marking incomplete due to missing information, and patch needing
further work to avoid causing regressions for non-affected users.]
** Changed in: xserver-xorg-input-elographics (Ubuntu)
Assignee: Bryce Harrington (bryceharrington) = (unassigned)
Status: Triaged = Incomplete
--
Here is my touchscreen section in xorg.conf
#
# Touchscreen section #
#
Section Inputdevice
Identifier TouchScreen
Driver elographics
Option Device /dev/ttyS1
#Option AlwaysCore
Option ScreenNumber 0
Hello,
I am using Ubuntu 8.10 Intrepid with the elographics touchscreen driver.
My xorg.conf configuration is the same as the one previously posted on
this thread. I still have problems with the freezing of the mouse and
keyboard and it does not seem to work since I touch the screen and no
mouse
I've added alendubri's patched version for Hardy into my PPA:
https://edge.launchpad.net/~intuitivenipple/+archive?field.name_filter
=xserver-xorg-input-elographicsfield.status_filter=published
I'm also attaching a debdiff for Hardy (1:1.1.0-3ubuntu1).
** Attachment added: Hardy debdiff
** Changed in: xserver-xorg-input-elographics (Ubuntu)
Assignee: (unassigned) = Bryce Harrington (bryceharrington)
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Bryce, can you please review this and upload to hardy/intrepid-proposed,
and make sure it gets into jaunty? It seems to be fixed upstream in
1.2.2. Thanks!
** Changed in: xserver-xorg-input-elographics (Ubuntu Hardy)
Assignee: (unassigned) = Bryce Harrington (bryceharrington)
--
MinY MaxY
I just had the issue, applying the patch and rebuilding the driver
solved it. (In Intrepid)
** Changed in: xserver-xorg-input-elographics (Ubuntu)
Importance: Undecided = High
Status: Confirmed = Triaged
--
MinY MaxY leads to unexpected behaviour
This patch fixed thigns for me in Hardy! Here is a package for Hardy...
-Gadi
** Attachment added: Hardy package for elographics with patch
http://launchpadlibrarian.net/17475532/xserver-xorg-input-elographics_1.1.0-4_i386.deb
--
MinY MaxY leads to unexpected behaviour
Hi to all on the Forum!
I installed Ubuntu 8.04 on an industrial PC with integrated touchpad. The
touchpad is connected by the serial interface /dev/ttyS1. Then I use the
xserver-xorg-input-elographics package. The X system reports the following (on
Xorg.0.log):
--
Hi to all on the Forum!
I installed Ubuntu 8.04 on an industrial PC with integrated touchpad. The
touchpad is connected by the serial interface /dev/ttyS1. Then I use the
xserver-xorg-input-elographics package. The X system reports the following (on
Xorg.0.log):
--
Sorry for the duplicate comment :-( it was a failure of a newbie on
launchpad
Here goes the second patch file.
Regards,
Alberto E. Dubuc B. (alendubri)
** Attachment added: Inproved functionality patch for 1.2.2 of
xf86-input-elographics
On Fri, Aug 1, 2008 at 10:47 AM, BastiBense [EMAIL PROTECTED] wrote:
What's a reliable way to get this info? Mine is serial, but the
monitor is just labelled as a standard LG model. I don't see any
external indications.
Brian
This info should be in the Xorg.log (/var/log/Xorg.0.log). Simply
I get to the point where I use sudo debuild and it turns out with an
error:
debuild: fatal error at line 1247
Can anybody help me with this?
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Someone should verify that this doesn't cause problems on other models
of ELO touchscreens. In the first place I'd like to know why the Y-axis
got inverted all of the sudden... Is this due to a change in Xorg?
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You
** Changed in: xserver-xorg-input-elographics (Ubuntu)
Status: New = Confirmed
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Great !
The patch works fine, on Xubuntu 8.04
Thank you very much
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Ah, I finally got some information about what touch panel the POS system
is using:
(--) Elographics touchscreen is a AccuTouch, connected through a serial link.
(--) The controller is a model E271-2200, firmware revision 1.0.
--
MinY MaxY leads to unexpected behaviour
On Fri, Aug 1, 2008 at 8:50 AM, Cheetahcat [EMAIL PROTECTED] wrote:
Ah, I finally got some information about what touch panel the POS system
is using:
(--) Elographics touchscreen is a AccuTouch, connected through a serial link.
(--) The controller is a model E271-2200, firmware revision 1.0.
What's a reliable way to get this info? Mine is serial, but the
monitor is just labelled as a standard LG model. I don't see any
external indications.
Brian
This info should be in the Xorg.log (/var/log/Xorg.0.log). Simply search
for Elo and you should find the info formatted exactly like
This patch fixes the problem for me too! Thanks!
Since it looks like a pretty simple patch, hopefully someone can apply
it without a whole lot of review being required.
Thanks again
Brian
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received
Confirmed/fixed?
The vertical/Y-axis is inverted after upgrading to hardy.
I attached a quick patch to address this problem and it seems to work
just fine on my system. The problem is that for some reason the touch
screen provides the touch-position from the bottom of the screen while
Xorg
Forget the first part of the patch (row 733), that was just a changed
line break. :)
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Confirmed.
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
confirmed here as well.
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Confirmed in Xubuntu 8.04 with xf86-input-elographics-1.2.2
- Y-Axis is not inverted anymore and the calibration is okay now
- Mouse and keyboard (both USB) are frozen after touching the screen
- Touch does not perform 'mouse click'
Hopefully this will be fixed soon...
--
MinY MaxY leads to
Fixed in source package xf86-input-elographics-1.2.2.tar.gz (Debian unstable)
Cursor movement works properly now.
But still not recommended:
- After the first touch keyboard and mouse (both PS2) inputs are disabled
- Touch do not perform a mouse click
Tested with Xubuntu 8.04 and ELO 1739L
I have the same bug with 8.04
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Confirmed in released version of 8.04. (See duplicate bugs)
** Tags added: elo regression touchscreen
--
MinY MaxY leads to unexpected behaviour
https://bugs.launchpad.net/bugs/218671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
51 matches
Mail list logo
