< 1 week to go

Harald Sitter apachelogger at ubuntu.com
Fri Apr 11 15:50:53 UTC 2014

On Fri, Apr 11, 2014 at 5:35 PM, Nils Kassube <kassube at gmx.net> wrote:
> Jonathan Riddell wrote:
>> I'd be especially interested if that lightdm bug from 12.04LTS upgrade
>> can be recreated.
> I think you mean #1297936 which I advertised here recently. I just did
> the upgrade 12.04 -> 14.04 again. This time I did it in a VM where I
> created the offending config file before the upgrade. The bug is still
> there.
> If someone wants to verify the problem quickly, it is possible to do it
> on a trusty machine which doesn't have the package lightdm-gtk-greeter
> installed. And of course lightdm should be the display manager in use.
> Move the files /etc/lightdm/lightdm-kde-greeter.conf and
> /etc/lightdm/lightdm.conf out of the way and create the file
> /etc/lightdm/lightdm.conf with the contents
> [SeatDefaults]
> greeter-session=lightdm-gtk-greeter
> user-session=Lubuntu
> which I mentioned in the bug report. Then stop lightdm and it shouldn't
> be possible to start lightdm again as long as the faulty
> /etc/lightdm/lightdm.conf is present.
> Of course this quick test only partly verifies the problem, because it
> is still possible that the upgrader would remove the config file before
> the upgrade. But my test-upgrade today showed that the file is still
> there after the upgrade.

As I said in the bug report, that is quite simply an invalid config.
If you were to remove lightdm-kde-greeter you'd end up with an equally
broken config if the greeter-session was set to lightdm-kde-greeter.
Removing the config doesn't really solve that, at best that's a debian
packaging standard violating workaround.
What would need to happen is that lightdm needs to grow fallback logic
for when the configured greeter cannot be loaded so that it would then
continue trying to load an arbitrary greeter that works and continues
using that as default.

At any rate though this is something that has to be addressed by
lightdm at large, it is neither Kubuntu specific, nor does it have any
more impact on Kubuntu than on other flavors.


More information about the kubuntu-devel mailing list