[Bug 567068] Re: init: environ_valid() does not accept dot in key

Steve Langasek steve.langasek at canonical.com
Thu Sep 29 21:25:33 UTC 2011


Upstart 1.3 included in Ubuntu oneiric.

** Changed in: upstart (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/567068

Title:
  init: environ_valid() does not accept dot in key

Status in Upstart:
  Fix Released
Status in “upstart” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: udev

  Trying to configure my Logitech Marble for Lucid (amd64) as per
  https://help.ubuntu.com/community/Logitech_Marblemouse_USB
  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/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/input/input17
  [13838.379229] generic-usb 0003:046D:C408.0008: input,hidraw3: USB HID v1.10 Mouse [Logitech USB Trackball] on usb-0000:00:1d.1-1/input0
  upstart-udev-bridge[423]	Env must be KEY=VALUE pairs

  Now if I comment all x11_options like
  #ENV{x11_options.Buttons}="9"
  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_optionsButtons}="9"
  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://ubuntuforums.org/showthread.php?t=1458123
  it was pointed to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576811
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/567068/+subscriptions




More information about the foundations-bugs mailing list