X crashes after a few minutes or seconds (Jaunty)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xf86-input-evtouch (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
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 (eGalax-driver), and in Jaunty it does too, except the freezes.
And the eGalax driver doesn't find a usb-controller, so I cann't use it either.
Description: Ubuntu 9.04
Release: 9.04
xserver-
Installiert: 0.8.8-0ubuntu3
Kandidat: 0.8.8-0ubuntu3
Versions-Tabelle:
*** 0.8.8-0ubuntu3 0
500 http://
100 /var/lib/
Hardware:
Acer Aspire One ZG5 modded with eGalax Touchscreen (Hoda - eBay)
1.5 GB Ram
(happens with normal and Sickboy's kernel)
Thanks in advance!
Floyd
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xserver-
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersion: Linux version 2.6.29.
SourcePackage: xf86-input-evtouch
Tags: ubuntu-unr
Uname: Linux 2.6.29.
[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GME Express Memory Controller Hub [8086:27ac] (rev 03)
Subsystem: Acer Incorporated [ALI] Device [1025:015b]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03)
Subsystem: Acer Incorporated [ALI] Device [1025:015b]
tags: | added: crash |
Changed in xf86-input-evtouch (Ubuntu): | |
status: | New → Confirmed |
description: | updated |
tags: | added: 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 when I use first (and only) the touchscreen.
Maybe this helps.
Sorry for the duplicated bug, but firefox hasn't reacted at the first button press so I pressed it a second time.
Also sorry for my poor English.
Floyd