** Changed in: xorg-server
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/97643
Title:
evdev mice: Fatal server error:bogus pointer event from ddx
--
ubuntu-bugs
** Changed in: xorg-server
Importance: Medium = Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/97643
Title:
evdev mice: Fatal server error:bogus pointer event from ddx
--
ubuntu-bugs
Intrepid uses input-hotplug now, so this situation is not possible
anymore and should just work.
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: New = Fix Released
--
evdev mice: Fatal server error:bogus pointer event from ddx
https://bugs.launchpad.net/bugs/97643
You received
I'm voting for the solution in comment 9 as well. Finally all my mice
work happily together and I can switch from the mouse to the trackball
without interruption. Even the special buttons of some of the mice work
correctly.
Are there any drawbacks to that solution or could it be made the default
** Changed in: xorg-server
Status: Unknown = Invalid
--
evdev mice: Fatal server error:bogus pointer event from ddx
https://bugs.launchpad.net/bugs/97643
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Indeed, the issue is that a CorePointer cannot match multiple devices
(the MX revolution exposes several devices, including some keyboard
buttons).
solution: as mentioned, use SendCoreEvents for the evdev device as James
said. Sorry James, I did not understand that you had solved it and
how...
For what it's worth - this issue still persists in latest gutsy. With my
Logitech MX Revolution plugged in, I can't start X with the default
evdev configuration, and thus I am not able to use my MX buttons.
--
evdev mice: Fatal server error:bogus pointer event from ddx
I was having the same problem and found using SendCoreEvents in the
ServerLayout section.
The pertinent sections of my 'xorg.conf' are as follows:
Section InputDevice
Identifier mouse
Driver evdev
Option evBits+1-2
Option
FWIW, I'm having the same problem, but a different reason for not liking
the static configuration solution: My keyboard's got a scroll wheel, so
it's both keyboard and pointer. Yes, I *can* set this up statically, but
it's far more sensible to avoid the keyboard/mouse dichotomy in the
first place.
FWIW, I'm having the same problem, but a different reason for not liking
the static configuration solution: My keyboard's got a scroll wheel, so
it's both keyboard and pointer. Yes, I *can* set this up statically, but
it's far more sensible to avoid the keyboard/mouse dichotomy in the
first place.
configuration error, see
http://www.chrisweldon.net/index.php?/archives/60-Xorg-7.1-and-evdev-
problems-Solved.html
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Unconfirmed = Rejected
--
evdev mice: Fatal server error:bogus pointer event from ddx
I'm sorry, can you be a bit more explicit about the configuration error?
According to evdev(4), the following is the correct way to configure an
evdev entry for *all mice*, which is what I want:
And the following for all mice:
Section InputDevice
Identifier mouse
The rejection was in error, I believe.
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Rejected = Unconfirmed
--
evdev mice: Fatal server error:bogus pointer event from ddx
https://launchpad.net/bugs/97643
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
why don't you even try the solution from the url? It wouldn't be the
first time when manpage is obsolete, and in that case it should be
fixed. But since I've had success reports on this package and it didn't
work for you before... that's why it got rejected.
--
evdev mice: Fatal server
tor 2007-03-29 klockan 10:17 + skrev Timo Aaltonen:
why don't you even try the solution from the url? It wouldn't be the
first time when manpage is obsolete, and in that case it should be
fixed. But since I've had success reports on this package and it
didn't
work for you before... that's
Oh, the log also contains a default pointer:
~$ grep default pointer Xorg.0.log
(**) |--Input Device default pointer
(WW) default pointer: No Device specified, looking for one...
(II) default pointer: Setting Device option to /dev/input/mice
(--) default pointer: Device: /dev/input/mice
(==)
16 matches
Mail list logo
