[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-09-02 Thread Scott James Remnant
Ah, I'd read the following from the shell guide: Variables set by the user must have a name consisting solely of alphabet‐ ics, numerics, and underscores - the first of which must not be numeric. But SUS says, elsewhere: Environment variable names used by the utilities in the Shell and

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-08-27 Thread Martin Pitt
This is actually a problem in upstart. environ_valid() doesn't take into account that key names can have dots in them. However, this should just be a cosmetical problem, and not related to the mouse actually working (X.org talks directly to udev, not through upstart). ** Package changed: udev (Ubu

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-05-21 Thread Daniel Hahler
I do not get the error, but the following from "udevadm monitor -e" (at the end): UDEV [1274463750.051633] add /devices/pci:00/:00:02.0/usb2/2-7/2-7:1.0/input/input6/event3 (input) UDEV_LOG=3 ACTION=add DEVPATH=/devices/pci:00/:00:02.0/usb2/2-7/2-7:1.0/input/input6/event3 SU

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-05-19 Thread Daniel Hahler
This regressed in the end of the Lucid development cycle. See also http://daniel.hahler.de/hal-configuration-for-kingsis-peripherals-evoluent-verticalmouse-3 for what stopped working for me. ** Changed in: udev (Ubuntu) Status: New => Triaged ** Changed in: udev (Ubuntu) Importance: U

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-05-18 Thread Frode Egeland
Ruslan, try moving button mappings around (the "ButtonMapping" option). Andreas, try my solution, see comment #7 in this bug. -- udev rules with dot in key fails with Env must be KEY=VALUE pairs https://bugs.launchpad.net/bugs/567068 You received this bug notification because you are a member of

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-05-18 Thread Andreas Raster
Same problem here, trying to get my Marble Mouse working the way I had it working under 9.04. These are the udev rules I am using: ENV{ID_VENDOR}=="Logitech", \ ENV{ID_MODEL}=="USB_Trackball", \

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-05-08 Thread Ruslan
So, any ideas? -- udev rules with dot in key fails with Env must be KEY=VALUE pairs https://bugs.launchpad.net/bugs/567068 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https:/

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-05-05 Thread Ruslan
Yes, but with this scrolling works only by right small button(it is good for left handed people). How to make that scrolling was working with left small button? -- udev rules with dot in key fails with Env must be KEY=VALUE pairs https://bugs.launchpad.net/bugs/567068 You received this bug noti

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-05-04 Thread Frode Egeland
Solution: Ignore the talk of "/etc/X11/xorg.conf.d/" - if I put a file in there, my USB keyboard fails to start, so I can't type anything. Instead, add this to /etc/X11/xorg.conf: ### START FILE SNIPPET ### Section "InputClass" Identifier "Marble Mouse" MatchProduct "Logitech US

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-05-04 Thread Frode Egeland
I just tried this, as /etc/X11/xorg.conf.d/marblemouse.conf: ### START OF FILE ### Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-05-03 Thread Guido I
Great, it worked Pasting my conf $ cat /etc/X11/xorg.conf Section "InputClass" Identifier "Synaptics Custom Settings" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "synaptics" Option "SHMConfig" "On" Option "TapButton1""1

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-05-03 Thread Guido I
Hi everyone, After some googling I found this excellent clarification on the issue: https://fedoraproject.org/wiki/Input_device_configuration#xorg.conf.d (it's from fedora but applies exactly to ubuntu too, since both distros follow the same linux fs hierarchy guidelines) Basically it says that:

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-05-01 Thread Adamantios
The attached xorg.conf worked for me. Adjust to your needs and please share your findings. ** Attachment added: "xorg.conf.ubuntu.10.04" http://launchpadlibrarian.net/46926201/xorg.conf.ubuntu.10.04 -- udev rules with dot in key fails with Env must be KEY=VALUE pairs https://bugs.launchpad.ne

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-05-01 Thread Adamantios
I appended the following in /etc/X11/xorg.conf... Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol"

[Bug 567068] Re: udev rules with dot in key fails with Env must be KEY=VALUE pairs

2010-04-30 Thread Frode Egeland
This is really annoying - we had to use xorg.conf settings for Ubuntu 8.xx, a HAL fdi file for 9.xx and now although the help site says to use udev, it doesn't work! Being told to once again use xorg.conf settings, after hal worked *perfectly*, seems so pointless. If anyone can work out a sol