With Lucid we no longer use fdi files, so if the bug still exists there
it must be due to something different. Also, with lucid we are starting
to look more to -evdev than -evtouch for touchpad support, so the issue
is not one we have much interest in. If you still want to have it
explored with
I have a very similar problem with a 3M Microtouch EX-II touchpanel. It works
with the evtouch-driver (Ubuntu 9.10), but after a short period of time
(especially if many clicks are produced) the system freezes. I am using the
following (custom) fdi-file in
** Branch linked: lp:ubuntu/xorg-server
--
X crashes after a few minutes or seconds (Jaunty)
https://bugs.launchpad.net/bugs/368135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Eli's last fdi fixed it for me. However the calibration points are quite
different on mine. They shouldn't be in this file, as this overrides the
calibration generated by the GUI tool. I commented mine out and have not
had problems since.
--
X crashes after a few minutes or seconds (Jaunty)
There's an extra /deviceinfo at the bottom of
/usr/share/hal/fdi/policy/20thirdparty/50-elo-2700.fdi
This causes a parsing error and hal won't read the fdi..
just remove to fix..
--
X crashes after a few minutes or seconds (Jaunty)
https://bugs.launchpad.net/bugs/368135
You received this bug
Also affects Karmic, Lucid(Alpha2).
--
X crashes after a few minutes or seconds (Jaunty)
https://bugs.launchpad.net/bugs/368135
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
using 0.8.8-0ubuntu6.1 with the eGalax touchscreen another fdi is
needed:
?xml version=1.0 encoding=ISO-8859-1 ?
deviceinfo version=0.2
device
match key=info.product contains=eGalax Inc. USB TouchController
merge key=input.x11_driver type=stringevtouch/merge
merge
Thanks. The SendCoreEvents crash bug sounds like one we now have a
patch for in the xserver, so forcing SendCoreEvents on should not be
necessary.
I've also added your fdi into the package (except the now unnecessary
SendCoreEvents).
--
X crashes after a few minutes or seconds (Jaunty)
This bug was fixed in the package xf86-input-evtouch - 0.8.8-0ubuntu5
---
xf86-input-evtouch (0.8.8-0ubuntu5) karmic; urgency=low
* control: Add dependencies for ttf-freefont and x-ttcidfont-conf.
These dependencies are required by one of the earlier patches.
(LP: #299178)
** Tags added: jaunty
--
X crashes after a few minutes or seconds (Jaunty)
https://bugs.launchpad.net/bugs/368135
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
How have you switched off core events ?
Is it still hang ?
I have the same Problem.
--
X crashes after a few minutes or seconds (Jaunty)
https://bugs.launchpad.net/bugs/368135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have turned core events back on, and no crashes. I'm not sure which
change is the key unfortunately.
Is your touch screen configured by xorg.conf or a HAL fdi file? I have
also taken an fdi file into use, which could affect this issue.
--
X crashes after a few minutes or seconds (Jaunty)
I only use the ubuntu way, whitch means I have modified the file
/etc/evtouch/config.
--
X crashes after a few minutes or seconds (Jaunty)
https://bugs.launchpad.net/bugs/368135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
So, how did you ?
Maybe, you can send me your xorg.conf and fdi file please ?
--
X crashes after a few minutes or seconds (Jaunty)
https://bugs.launchpad.net/bugs/368135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
my xorg.conf is practically empty:
Section Monitor
Identifier Configured Monitor
EndSection
Section Screen
Identifier Default Screen
Monitor Configured Monitor
Device Configured Video Device
SubSection Display
No crashes today. I still have sendcoreevents set to false, and
additionally I changed CPU frequency scaling threshold from 95 to 40, so
CPU speed is increased more aggressively. In a day or two, if no
crashes, will try setting core events back on and see if freezing occurs
again. Now I also have
I have also experienced freezes in Jaunty using evtouch - system locks
up completely and I have to do a hard poweroff. This is with the same
exact xorg.conf that worked in Hardy without any problems. Still got
freezes after removing xorg.conf and creating fdi for touch screen.
Now running with
Have the same problem here, and many others reported a similar problem
and a lot of them seem to use eGalax touchscreens that use the xserver-
xorg-input-evtouch driver.
This problem came up for me in Jaunty and still ongoing in Karmic.
--
X crashes after a few minutes or seconds (Jaunty)
** Description changed:
My X server crashes (without reports in the log) after few time when I use my
touchscreen.
When I use my touchpad it doesn't. (first I thought it was a xorg-intel
problem)
Then I have to restart X via alt+print+K.
In Hardy, my touchscreen worked perfect
It seems to be solved!
I used my touchscreen for a while and there are no freezes anymore.
(normally there would be 10 freezes in that time))
Don't know which package did it, but I installed:
xserver-xorg-core-dbg (2:1.6.0-0ubuntu14)
xserver-xorg-input-tslib (0.0.5-1ubuntu2)
and the freezes are
F***!
The freezes are still there!
The first one came really late, but now they come quickly like before.
@ Uwe L. Korn
Can you post the eGalax beta-driver?
I don't get an answer from EETI!
Thanks.
Floyd
--
X crashes after a few minutes or seconds (Jaunty)
EDIT:
When I use my touchpad, then the touchscreen for 2-3 clicks, then touchpad,
then touchscreenfor 2-3..., and so on -- all is good.
But when I use only my touchscreen -- X crashes after a few hits.
I recognized, that when I use the touchpad and after the touchscreen --
X crashes later as
As this problem occurs with the eGalax driver too, I think this is maybe
related to another point of the system, could there be a problem with
the usbhid kernel module?
--
X crashes after a few minutes or seconds (Jaunty)
https://bugs.launchpad.net/bugs/368135
You received this bug notification
Just saw that that even when I am forcing X to use the eGalax driver, evtouch
is preferred and now everything works fine.
Info: I'm using a beta driver I received by an EETI employee, just mail them
and they will sent it to you.
--
X crashes after a few minutes or seconds (Jaunty)
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/26039851/Dependencies.txt
** Attachment added: LsHal.txt
http://launchpadlibrarian.net/26039852/LsHal.txt
** Attachment added: LsMod.txt
http://launchpadlibrarian.net/26039854/LsMod.txt
** Attachment added: LsPci.txt
** Tags added: crash
** Changed in: xf86-input-evtouch (Ubuntu)
Status: New = Confirmed
--
X crashes after a few minutes or seconds (Jaunty)
https://bugs.launchpad.net/bugs/368135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
26 matches
Mail list logo
