This was already done in upstream commit
336d871860710af1cb3a55234d5051f01e842e02. The fix is in Jaunty already.
** Changed in: hal (Ubuntu)
Status: In Progress => Fix Released
--
Segfault in hald startup (hald/linux/devices.c)
https://bugs.launchpad.net/bugs/322798
You received this bug
Alternate fix on http://bazaar.launchpad.net/~carsten-munk/hal/led-
problem/revision/2 (incorrect name in changelog) - we ran into the same
issue on 2.6.21-omap1 on Nokia N8x0s. Issue happened sporadically.
--
Segfault in hald startup (hald/linux/devices.c)
https://bugs.launchpad.net/bugs/322798
Doesn't block current arm builds any more; patch might still make sense,
though.
Taking off the release radar.
** Changed in: hal (Ubuntu Jaunty)
Status: In Progress => Won't Fix
Target: ubuntu-9.04-beta => None
--
Segfault in hald startup (hald/linux/devices.c)
https://bugs.launc
** Changed in: hal (Ubuntu Jaunty)
Assignee: (unassigned) => Martin Pitt (pitti)
Status: New => In Progress
--
Segfault in hald startup (hald/linux/devices.c)
https://bugs.launchpad.net/bugs/322798
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Changed in: hal (Ubuntu Jaunty)
Target: None => ubuntu-9.04-beta
** Changed in: hal (Ubuntu Jaunty)
Importance: Undecided => High
** Tags added: arm
--
Segfault in hald startup (hald/linux/devices.c)
https://bugs.launchpad.net/bugs/322798
You received this bug notification because
** Attachment added: "Possible fix, based on the assumption that the code is
trying to process a NULL-terminated argument vector. This patch requires
sanity-checking with regard to what the code is trying to do: should arguments
_ever_ have fewer than three non-NULL elements, for example?"
