Launching Login Screen (LightDM) in KDE systemsettings always crashes systemsettings on my machine.
# dpkg -l *lightdm* | grep ii
ii liblightdm-gobject-1-0 1.10.2-1 amd64 simple display manager (gobject library)
ii liblightdm-qt-3-0 1.10.2-1 amd64 simple display manager (Qt library)
ii lightdm 1.10.2-1 amd64 simple display manager
ii lightdm-gtk-greeter 1.8.5-1 amd64 simple display manager (GTK+ greeter)
ii lightdm-kde-greeter 0.3.2.2-1 amd64 LightDM KDE greeter
ii siduction-settings-lightdm-gtk-december 2014.07.18 all Settings for installed siduction lightdm
Can anybody reproduce this bug, or, better, give a hint for resolving?
Greetings
Tom
I just tried and it's not crashing for me. However, we do differ on the results for "dpkg -l *lightdm* | grep ii"
# dpkg -l *lightdm* | grep ii
ii liblightdm-gobject-1-0 1.10.2-1 amd64 simple display manager (gobject library)
ii lightdm 1.10.2-1 amd64 simple display manager
ii lightdm-gtk-greeter 1.8.5-1 amd64 simple display manager (GTK+ greeter)
ii siduction-settings-lightdm-gtk-december 2014.07.18 all Settings for installed siduction lightdm
I don't have liblightdm-qt-3-0 or lightdm-kde-greeter. Whether or not this is related to your problem, might be something worth looking into.
apt-get remove --purge lightdm-kde-greeter
Thank you, both, for quick and helpful replies. :D
Next questions arise:
I have to avoid lightdm-kde-greeter in its present desolate state?
Is there a GUI for configuring lightdm-gtk-greeter?
Greetings
Tom
if you consider geany as a gui - yes :D - but the config file is very well documentated
Hi samoht,
yes I can confirm that!
dpkg -l *lightdm* | grep ii
ii liblightdm-gobject-1-0 1.10.2-1 amd64 simple display manager (gobject library)
ii liblightdm-qt-3-0 1.10.2-1 amd64 simple display manager (Qt library)
ii lightdm 1.10.2-1 amd64 simple display manager
ii lightdm-gtk-greeter 1.8.5-1 amd64 simple display manager (GTK+ greeter)
ii siduction-art-lightdm-ridersonthestorm 0.1.23 all lightdm theme for the siduction 12-2.0 release
Now my system is affected too :(.
Was it a systemsettings update?
https://bugs.kde.org/show_bug.cgi?id=339715