** 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/173833
Title:
evdev mouse fails on hardy: cannot open input pEvdev
--
ubuntu-bugs mailing
** 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/173833
Title:
evdev mouse fails on hardy: cannot open input pEvdev
--
ubuntu-bugs mailing
** Changed in: xorg-server
Importance: Unknown = Medium
--
evdev mouse fails on hardy: cannot open input pEvdev
https://bugs.launchpad.net/bugs/173833
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Using mouse driver would be enough for me if it recognized all buttons
of my mouse well. I've got Logitech MX310 and it has one special button,
in MS Windows used as application changer (a replacement for Alt+Tab).
Evdev recognizes it properly, whereas mouse driver thinks it's the
same as middle
Related trouble with evdev and mouse model A4 Tech SWOP-80PU8. I
eventually went with this config:
Section InputDevice
Identifier Mouse0
Driver mouse
Option Buttons 10
Option Name A4 Tech USB Laser Mouse
Option Protocol auto
Option
** Changed in: xorg-server
Status: Confirmed = Fix Released
--
evdev mouse fails on hardy: cannot open input pEvdev
https://bugs.launchpad.net/bugs/173833
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Can someone please paste a working sample for a evdev mouse section in
xorg.conf? I still get this:
**) Mouse1: always reports core events
(II) Mouse1: Found 3 relative axes.
(II) Mouse1: Configuring as pointer.
(II) Mouse1: Found 8 mouse buttons
(II) Mouse1: Configured 11 mouse buttons.
(WW)
As already mentioned by Michael above you should not use the /dev/input/by-path
link, you are supposed to use the
/dev/input/inputXX special file that is not a link. If you want to make sure
that a specific mouse gets a specific name in /dev/input you need to create a
udev rule (changing the
Repeating, don't use the by-path or the by-id link. At least for me,
it doesn't work.
Then you should report a separate bug because of course they should
work. Here is a part of my xorg.conf that is working in latest Hardy:
Section InputDevice
Identifier microsoft-kbd
I have just checked here. With the new xorg packages I can use the
/dev/input/by-id entry but not the
/dev/input/by-path entry. (I have a serial keyboard and mouse and another USB
set). The error I get in the log file is the same described in comment a
The device names are not the only problem. It seems evdev support is broken in
the current X.org:
Even if I get my mouse working with evdev, it is also recognized by the
xorg-input infrastructure, so all events are received double. And the
xorg-input drivers do not recognize a couple of buttons
This bug was fixed in the package xserver-xorg-input-evdev -
1:1.2.0-1ubuntu1
---
xserver-xorg-input-evdev (1:1.2.0-1ubuntu1) hardy; urgency=low
* 100_fix_b_map_data:
Initialise b_map_data to correct size. (fdo: #13991)
* 101_fix_error_message.diff:
More accurate error
Gabor: The problem you're describing seems to be a different bug than
what this report discusses. I'd suggest you file it seperately.
--
evdev mouse fails on hardy: cannot open input pEvdev
https://bugs.launchpad.net/bugs/173833
You received this bug notification because you are a member of
Do the /dev/input/by-id symlinks still work? If so, a better message
would be the following:
$IDENTIFIER: The 'Name' option has been removed in the transition to
Input Hotplug; please use 'Device' instead.
($IDENTIFIER is from xorg.conf.)
--
evdev mouse fails on hardy: cannot open input
This is *very* bad for me that the configuration option for by Name is
gone. w/ an Apple BT mouse, I don't have a nice symlink created for me
ever. I'm not sure how I'll ever be able to give it a 'Device' name.
--
evdev mouse fails on hardy: cannot open input pEvdev
- Original Message
From: Mario Limonciello [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, March 30, 2008 4:11:13
Subject: [Bug 173833] Re: evdev mouse fails on hardy: cannot open input pEvdev
This is *very* bad for me that the configuration option for by Name is
gone. w
This bug is caused by an configuration change that is undocumented, the
man page contains options that are no longer valid. This is made worse
by the fact that the error message is very unclear.
Both problems are resolved in upstream git (freedesktop.org, not
debian).
The Debian package is also
Good call Michael!
Using your trick of creating special udev rules works well. Hence, it
seems that the new evdev does not plays nice with symbolic links as
suggested by Iaga in comment 15 above and my other posts I saw on the
internet. In my case it worked with the serial keyboard and mouse
Don't suppose there's any way to get thu ButtonMapping option from evdev
working, either with an fdi file or an xorg.conf entry pointing at a
udev-generated device file?
--
evdev mouse fails on hardy: cannot open input pEvdev
https://bugs.launchpad.net/bugs/173833
You received this bug
Mike... I had multiseat working in Gutsy too. But it stopped working in
hardy with the new evdev.
I have found a solution to mine problem (for a 2 seat configuration at
least):
1) I had to add the line
Option AutoAddDevicesno
to the first first ServerLayout section.
You can find attached the 10-x11-input.fdi file edited to load the
options for a Brazilian keyboard as cited above.
** Attachment added: 10-x11-input.fdi
http://launchpadlibrarian.net/12839650/10-x11-input.fdi
--
evdev mouse fails on hardy: cannot open input pEvdev
/input/by-path/symlinks).
--- mike t.
- Original Message
From: Paulo J. S. Silva [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, March 24, 2008 21:58:20
Subject: [Bug 173833] Re: evdev mouse fails on hardy: cannot open input pEvdev
Mike... I had multiseat working in Gutsy too
, March 23, 2008 11:28:46
Subject: [Bug 173833] Re: evdev mouse fails on hardy: cannot open input pEvdev
Is there anyone here being able to use evdev to control two independent
sets of keyboard+mouse (for a multi-seat setup)?
--
evdev mouse fails on hardy: cannot open input pEvdev
https
Is there anyone here being able to use evdev to control two independent
sets of keyboard+mouse (for a multi-seat setup)?
I have a 2 seat setup that has been working for a year now. Since I have
two video-cards I basicully run two X sessions. I used evdev to control
the input devices. Now, I could
So basically, upstream went nuts and threw away most of the
configuration options that made evdev so interesting.
Great.
--
evdev mouse fails on hardy: cannot open input pEvdev
https://bugs.launchpad.net/bugs/173833
You received this bug notification because you are a member of Ubuntu
Bugs,
Okay, the above solution didn't work well with my multiseat setup. After
enabling the second X server in /etc/kde3/kdm/kdmrc, the mouse pointer
and the keyboard were frozen again in :0. Finally, I found out that just
removing the .fdi file and removing all InputDevice entries in xorg.conf
works
I've found that it's still possible to tell the evdev driver which
device he should use. This entry works for me:
Section InputDevice
Identifier dmouse
Driver evdev
Option Device /dev/input/by-id/usb-04d9_1400-event-mouse
EndSection
Regards,
Michael
--
evdev mouse fails on
I was also caught by this bug and i managed to make it work by copying
the .fdi to /etc/hal/fdi/policy and changing the Driver evdev
entries back to kbd or mouse. It's a shame that there's no backwards
compatibility, though. It's a bit annoying not to be able to login in
kdm because they keyboard
Just because nobody has mentioned it, I thought I would:
btnx is an amazing replacement for all this nonsensical evdev
tomfoolery. It's easy to configure via gui, live (no restarts) and has
profile management.
--
evdev mouse fails on hardy: cannot open input pEvdev
** Changed in: xorg-server
Status: Invalid = Confirmed
--
evdev mouse fails on hardy: cannot open input pEvdev
https://bugs.launchpad.net/bugs/173833
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I was able to get it working with this workaround, however, a number of
buttons for my mouse (Logitech MX Revolution) have stopped showing up in
xev. specifically, it does not detect wheel left and wheel right,
secondary wheel scroll up or down, and secondary wheel click. Is there
any way to get
** Changed in: xorg-server
Status: Unknown = Invalid
--
evdev mouse fails on hardy: cannot open input pEvdev
https://bugs.launchpad.net/bugs/173833
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
** Bug watch added: freedesktop.org Bugzilla #12655
https://bugs.freedesktop.org/show_bug.cgi?id=12655
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=12655
Importance: Unknown
Status: Unknown
--
evdev mouse fails on hardy: cannot open input pEvdev
I fully deleted the section:
Section InputDevice
Identifier Configured Mouse
Driver evdev
...
and deleted the string - InputDeviceConfigured Mouse
CorePointer from Section ServerLayout
however and not works, show please example of working xorg.conf
--
evdev
Yes - work (...I forgot to install xvkbd):
Section InputDevice
Identifier Configured Mouse
#Driver evdev
OptionProtocolAuto
Driver mouse
Option SendCoreEvents
Option CorePointer
Option Name
You also need to remove the evdev section in xorg.conf
/Mikael
tor 2008-01-31 klockan 16:36 + skrev kiev1:
copying /usr/share/doc/hal/examples/10-x11-input.fdi to
/etc/hal/fdi/policy not work
--
[EMAIL PROTECTED]
Plus ça change, plus c'est la même chose
--
evdev mouse fails on
copying /usr/share/doc/hal/examples/10-x11-input.fdi to
/etc/hal/fdi/policy not work
--
evdev mouse fails on hardy: cannot open input pEvdev
https://bugs.launchpad.net/bugs/173833
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I have the same bug!!!
--
evdev mouse fails on hardy: cannot open input pEvdev
https://bugs.launchpad.net/bugs/173833
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
On mån, 2007-12-24 at 08:23 +, Timo Aaltonen wrote:
You can test it by copying /usr/share/doc/hal/examples/10-x11-input.fdi
to /etc/hal/fdi/policy.
Nice! Works well here.
I had my buttons configured manually anyway, using xbindkey, and adding
that file and re-plugging the mouse made all
You can test it by copying /usr/share/doc/hal/examples/10-x11-input.fdi
to /etc/hal/fdi/policy.
What's missing is a way to make it use the correct keymap automatically
without editing any fdi file or such.
btw, this bug apparently is just due to misconfiguration with the new
evdev. The problem
** Changed in: xserver-xorg-input-evdev (Debian)
Status: New = Fix Released
--
evdev mouse fails on hardy: cannot open input pEvdev
https://bugs.launchpad.net/bugs/173833
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I think the bug in Debian is the same.
--
evdev mouse fails on hardy: cannot open input pEvdev
https://bugs.launchpad.net/bugs/173833
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Yep, upstream seems to think that input-hotplug is the only proper way
to use evdev. That's going to happen later in the hardy timeframe.
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Importance: Undecided = Medium
Status: New = Confirmed
--
evdev mouse fails on hardy: cannot open
** Changed in: xserver-xorg-input-evdev (Debian)
Status: Unknown = New
--
evdev mouse fails on hardy: cannot open input pEvdev
https://bugs.launchpad.net/bugs/173833
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
On tis, 2007-12-04 at 08:22 +, Timo Aaltonen wrote:
Yep, upstream seems to think that input-hotplug is the only proper way
to use evdev. That's going to happen later in the hardy timeframe.
Yes, evdev is awkward to configure manually. What component is missing
in Hardy for hotplug to work?
45 matches
Mail list logo
