Comment 5 for bug 217654

I can confirm the bug on two separate workstations.

I just tried the sed fix but it will not run correctly, or so it seems.
It gives me the sed help (twice) and at the end

<code>bash: s/^Path=/#Path=/: No such file or directory</code>