init: environ_valid() does not accept dot in key
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Fix Released
|
Low
|
Scott James Remnant | ||
upstart (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: udev
Trying to configure my Logitech Marble for Lucid (amd64) as per
https:/
using udev rules. The rule is run, but fails with error
[13838.180329] usb 7-1: new low speed USB device using uhci_hcd and address 5
[13838.359037] usb 7-1: configuration #1 chosen from 1 choice
[13838.377529] input: Logitech USB Trackball as /devices/
[13838.379229] generic-usb 0003:046D:
upstart-
Now if I comment all x11_options like
#ENV{x11_
the "Env must be KEY=VALUE pairs" error is gone when plugging in the Logitech mouse.
So I tried to instead removed the dot (.) in the notation above
ENV{x11_
and then it works, meaning it runs the rule without the KEY=VALUE error. But of course the mouse configuration does not take place.
In response to forum post http://
it was pointed to http://
saying that this wont be fixed. Instead use xorg.conf, but that is not available by default in Lucid, nor is Hal, and now this.
I'm not sure of this just needs a documentation update or a udev fix. But removing Hal, xorg.conf, and the udev rules does not work puts the user in limbo.
Changed in upstart: | |
status: | Fix Committed → Fix Released |
Changed in upstart (Ubuntu): | |
status: | Invalid → New |
importance: | Low → Undecided |
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.
</rant>
If anyone can work out a solution that will make my Marble "just work", that'd be great.
I'll look at xorg.conf.d/ and see if I can figure out my old xorg.conf solution (which is long gone from my pc)...