I have made a fix for this bug and attached it as a debdiff to this comment:
This is a very simple change to the code in debian/gdm.init - I remove line 73 which has an extra unmatched "fi"
Tested as follows:
Built binaries using sbuild in latest vivid environment on a trusty machine. Fired up an Ubuntu-Gnome vivid daily build (current for 4/2/2015) LiveCD in a virtual machine. Verified the bug failure on the plain vanilla vivid LiveCD as follows:
cd /etc/init.d
./gdm
Could not get the failure with "./gdm start" like mentioned in the bug report - had to leave out "start"
Copied all the .deb files from the vivid sbuild on the trusty machine onto the Ubuntu-Gnome vivid vm. Installed the four .deb files using "dpkg -i ..." Install succeeded, and visually inspecting /etc/init.d/gdm showed line 73 was indeed removed. Typed:
cd /etc/init.d
./gdm
At the command prompt and got no error about "fi" - just showed the informational message about usage (because I left out "start"). This confirms that the bug is fixed for the current version of vivid.
I have made a fix for this bug and attached it as a debdiff to this comment:
This is a very simple change to the code in debian/gdm.init - I remove line 73 which has an extra unmatched "fi"
Tested as follows:
Built binaries using sbuild in latest vivid environment on a trusty machine. Fired up an Ubuntu-Gnome vivid daily build (current for 4/2/2015) LiveCD in a virtual machine. Verified the bug failure on the plain vanilla vivid LiveCD as follows:
cd /etc/init.d
./gdm
Could not get the failure with "./gdm start" like mentioned in the bug report - had to leave out "start"
Copied all the .deb files from the vivid sbuild on the trusty machine onto the Ubuntu-Gnome vivid vm. Installed the four .deb files using "dpkg -i ..." Install succeeded, and visually inspecting /etc/init.d/gdm showed line 73 was indeed removed. Typed:
cd /etc/init.d
./gdm
At the command prompt and got no error about "fi" - just showed the informational message about usage (because I left out "start"). This confirms that the bug is fixed for the current version of vivid.