I can confirm this bug happening with Karmic. Tablet: G-Pen 560
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bugs.launchpad.net/bugs/355021
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-aiptek in ubuntu.
__
** Tags added: jaunty
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bugs.launchpad.net/bugs/355021
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-aiptek in ubuntu.
___
Mail
It's working with the Peter Hutterer's patch at
https://bugs.freedesktop.org/attachment.cgi?id=28772 on 1.2.0 version of
input aiptek driver.
Thanks to him.
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bugs.launchpad.net/bugs/355021
You received this bug notification because you are
** Changed in: xserver
Status: Confirmed => Fix Released
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bugs.launchpad.net/bugs/355021
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-aiptek in ubuntu.
__
Forgot to add: I'm using an Aiptek SlimTablet 600U (Model WCK-C121) and
have NOT installed xserver-xorg-input-aiptek but xserver-xorg-input-
wacom (the tablet also uses the "wacom" kernel module). The problem
seems to be the same though. So it might have nothing to do with the
specific input driver
Just wanted to add that for me (Jaunty, all updates as of today) X/GDM
won't start correctly if the tablet is plugged in. Also I got X crashing
when trying to start a new console (Terminator) while the tablet is
plugged in. And yes, unplugging the tablet also hangs and then restarts
X.
--
Unplugg
** Changed in: xserver
Status: Unknown => Confirmed
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bugs.launchpad.net/bugs/355021
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-aiptek in ubuntu.
___
** Bug watch added: freedesktop.org Bugzilla #22693
https://bugs.freedesktop.org/show_bug.cgi?id=22693
** Also affects: xserver via
https://bugs.freedesktop.org/show_bug.cgi?id=22693
Importance: Unknown
Status: Unknown
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bug
The breakpoints only seemed to trigger once.
** Attachment added: "with breakpoints"
http://launchpadlibrarian.net/27824229/jaunty-gdb-with-breakpoints.txt
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bugs.launchpad.net/bugs/355021
You received this bug notification because you a
Had to set up a VM, so it took a while longer than expected. Hopefully
the following backtraces will be useful. If not, let me know what to do.
Remote access to this VM can also be arranged if wanted.
** Attachment added: "without breakpoints"
http://launchpadlibrarian.net/27824138/jaunty-gdb1
This bug is also present in Arch Linux current, with xf86-input-aiptek
1.2.0 and xorg-server 1.6.1. These packages are unpatched, so it is
almost certain that this is an upstream problem. There has not been any
commits to the aiptek driver git repo after 1.2.0
Some information I've gathered (likel
Backtrace with more debugging symbols available...
** Attachment added: "backtrace_full_02.txt"
http://launchpadlibrarian.net/26733344/backtrace_full_02.txt
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bugs.launchpad.net/bugs/355021
You received this bug notification because you
btw, this also explains why the apport crash reporter didn't detect the
crash. It's not actually a traditional "segmentation fault", instead
it's a consistency check in the C library that notices that something is
not right and then abort the program.
One thing that perplexes me about this backtra
There are some stack frames that still miss proper function names, for
example there is:
#12 0xb7f22749 in ?? () from /usr/lib/libhal.so.1
to get a proper function name for that one you need to install debug
symbols for the package that ships the file "/usr/lib/libhal.so.1" and
to find out
The backtrace
** Attachment added: "bactrace_full.txt"
http://launchpadlibrarian.net/26728565/bactrace_full.txt
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bugs.launchpad.net/bugs/355021
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
After crash and restart, not trying backtrace yet.
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/26727189/Xorg.0.log
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bugs.launchpad.net/bugs/355021
You received this bug notification because you are a member of Ubuntu
After crash and restart, not trying backtrace yet.
** Attachment added: "Xorg.0.log.old"
http://launchpadlibrarian.net/26727182/Xorg.0.log.old
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bugs.launchpad.net/bugs/355021
You received this bug notification because you are a member o
I'll run the backtraces in a bit, when I can get to a machine to ssh in
from.
Neil
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/26726658/lspci.txt
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bugs.launchpad.net/bugs/355021
You received this bug notification bec
Okay, what we need is to collect a full backtrace where each stacktrace
has both local variable information and a proper function name. For this
we're going to need debug symbols installed. Start by installing these
packages (you mostly need the core package but it doesn't hurt to throw
in all of t
** Attachment added: "lsusb.txt"
http://launchpadlibrarian.net/26722587/lsusb.txt
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bugs.launchpad.net/bugs/355021
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-aiptek
Ok Martin.
I've tried to use apport to capture a crash report, but it just isn't
happening... What appears to be a crash to me, the instant ending of my
x session on unplugging the tablet isn't appearing as a crash to apport.
I have run "lsusb -v" and "dmesg" as you have asked and am uploading t
@Neil, can you please start the automatic crasher reporter and then
trigger the bug? This will hopefully give us a full backtrace showing
exactly where in the X server the crash happens. To start the crash
reporter run this command:
sudo force_start=1 /etc/init.d/apport start
...afterwards just u
Problem persists for me in the released version of Jaunty. I'd be happy
to provide more information or do more tests (maybe even lend the
tablet) if anyone wants to work on this.
--
Unplugging USB tablet crashes xserver (Jaunty)
https://bugs.launchpad.net/bugs/355021
You received this bug notifi
23 matches
Mail list logo
