And it's equally hard for us.., neigh impossible, to gather more info then
already has been gathered with all the bug reports.
If there is a way: tell us how. Do not tell us how to create a new bugreport.
Tell us how to get more info about THIS bug.
It's not that I do not want to help, and
Still there in 12.10:
Oct 19 11:01:35 tribble kernel: [ 1939.477224] psmouse serio4: TouchPad at
isa0060/serio4/input0 lost sync at byte 1
Oct 19 11:01:35 tribble kernel: [ 1939.478635] psmouse serio4: TouchPad at
isa0060/serio4/input0 lost sync at byte 1
Oct 19 11:01:35 tribble kernel: [
Yes, I saw that. So somewhere there May be a new bug report. I do not
know. No link to the new bugreport, no number to search on, etc.
So I'm still filing it here.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in
You don't understand I think. The original bugreporter maybe, perhaps,
perhaps not, decided to create a new bug report. How can I know?
I do know that creating another on my account makes no sense when there
is a perfectly good bugreport already here.
By the way, this bug report already seems to
I compiled from the source and experienced the same problem using Karmic
and an Intel graphics card. I think it is gnome/gtk related when I look
at the backtrace.
** Attachment added: gnusound.log
http://launchpadlibrarian.net/34807476/gnusound.log
--
gnusound crashes X session immediately
5 matches
Mail list logo