I removed today the lightdm display-manager from my system where I updated several times from lower fedora versions. There have been removed 3 files. When I do try to reinstall it again,it gives me the mega list below …
As I do understand the lightdm is not just used for deepin. Mate and others also use it.
What is the reason to make such a huge dependency list ?
On every new release we do fight about megabytes, so that we can fit the ISO’s on a CD. And now such a “Litght” app is getting blown up so much because of widgets and Background images !
Is there a way to install lightdm still as a light app?
sudo dnf install lightdm
Last metadata expiration check: 2:37:58 ago on Thu 07 Dec 2023 09:39:57 AM -03.
Package Architecture Version Repository Size
lightdm x86_64 1.32.0-5.fc39 fedora 240 k
appres x86_64 1.0.6-4.fc39 fedora 16 k
deepin-control-center-lib x86_64 5.5.158-1.fc39 fedora 224 k
deepin-desktop-base noarch 2023.03.31-1.fc39 fedora 34 k
deepin-network-core x86_64 1.1.9-1.fc39 fedora 1.3 M
deepin-network-core-lib x86_64 1.1.9-1.fc39 fedora 187 k
deepin-qt-dbus-factory x86_64 5.5.22-6.fc39 fedora 730 k
deepin-screensaver-data noarch 5.0.5-6.fc39 fedora 663 k
deepin-session-shell x86_64 5.5.93-1.fc39 fedora 965 k
dtkcommon x86_64 5.6.9-1.fc39 fedora 9.9 k
dtkcore x86_64 5.6.13-1.fc39 fedora 570 k
dtkgui x86_64 5.6.12-1.fc39 fedora 374 k
dtkwidget x86_64 5.6.12-1.fc39 fedora 15 M
gsettings-qt x86_64 0-0.28.20180723bzr85.fc39 fedora 40 k
kf5-networkmanager-qt x86_64 5.111.0-1.fc39 updates 350 k
libgle x86_64 3.1.0-29.fc39 fedora 52 k
libqtxdg x86_64 3.11.0-1.fc39 fedora 128 k
lightdm-gobject x86_64 1.32.0-5.fc39 fedora 62 k
lightdm-qt5 x86_64 1.32.0-5.fc39 fedora 44 k
lshw x86_64 B.02.19.2-12.fc39 fedora 331 k
perl-Clone x86_64 0.46-4.fc39 fedora 22 k
perl-Data-Dump noarch 1.25-8.fc39 fedora 32 k
perl-Digest-HMAC noarch 1.04-8.fc39 fedora 22 k
perl-Digest-SHA x86_64 1:6.04-501.fc39 fedora 61 k
perl-Encode-Locale noarch 1.05-27.fc39 fedora 18 k
perl-File-Copy noarch 2.41-502.fc39 updates 20 k
perl-File-Listing noarch 6.16-1.fc39 fedora 25 k
perl-File-Slurper noarch 0.014-3.fc39 fedora 21 k
perl-HTML-Parser x86_64 3.81-3.fc39 fedora 124 k
perl-HTML-Tagset noarch 3.20-54.fc39 fedora 18 k
perl-HTTP-Cookies noarch 6.10-10.fc39 fedora 37 k
perl-HTTP-Date noarch 6.06-2.fc39 fedora 24 k
perl-HTTP-Message noarch 6.44-3.fc39 fedora 101 k
perl-HTTP-Negotiate noarch 6.01-36.fc39 fedora 19 k
perl-I18N-Langinfo x86_64 0.22-502.fc39 updates 22 k
perl-IO-HTML noarch 1.004-11.fc39 fedora 28 k
perl-LWP-MediaTypes noarch 6.04-15.fc39 fedora 33 k
perl-Module-Load noarch 1:0.36-500.fc39 fedora 17 k
perl-NTLM noarch 1.09-36.fc39 fedora 22 k
perl-Net-HTTP noarch 6.23-2.fc39 fedora 39 k
perl-Time-HiRes x86_64 4:1.9775-500.fc39 fedora 57 k
perl-TimeDate noarch 1:2.33-11.fc39 fedora 57 k
perl-Try-Tiny noarch 0.31-6.fc39 fedora 41 k
perl-WWW-RobotRules noarch 6.02-37.fc39 fedora 19 k
perl-diagnostics noarch 1.39-502.fc39 updates 214 k
perl-libwww-perl noarch 6.72-1.fc39 fedora 209 k
perl-subs noarch 1.04-502.fc39 updates 12 k
qt5-qttools x86_64 5.15.11-1.fc39 updates 41 k
xscreensaver-base x86_64 1:6.08-1.fc39 updates 502 k
xscreensaver-extras x86_64 1:6.08-1.fc39 updates 2.3 M
xscreensaver-extras-base x86_64 1:6.08-1.fc39 updates 227 k
xscreensaver-gl-base x86_64 1:6.08-1.fc39 updates 17 k
xscreensaver-gl-extras x86_64 1:6.08-1.fc39 updates 11 M
Installing weak dependencies:
deepin-screensaver x86_64 5.0.5-6.fc39 fedora 47 k
deepin-wallpapers noarch 1.7.7-15.fc39 fedora 62 M
perl-IO-Compress-Brotli x86_64 0.004001-10.fc39 fedora 27 k
perl-PerlIO-utf8_strict x86_64 0.010-4.fc39 fedora 26 k
Install 57 Packages
Total download size: 99 M
Installed size: 158 M
Is this ok [y/N]:
Light refers primarily to the memory and cpu: these are the critical resources that have permanently to be shared among all processes, and the use of these resources needs power/battery.
I think today it is mostly assumed that storage in these amounts ain’t an issue: it does neither impact the critical resources nor does it impact power consumption/battery. The only impact is the decrease of storage space.
Yet, it might be questioned if all that packages are really necessary. But in the end, Fedora is less intended for very old hardware or specialized hardware that needs to count MB I guess.
In your case, I would suggest to remain with the initial solution suggested by Flo: try it without the soft dependencies. But I suggest to even do that only if you really need storage space because I am not sure if some types of testing (that are conducted before pushing packages to stable) assume the soft dependencies to be installed, just to avoid issues that are avoidable.
Thanks for your answers. Unfortunately I could not solve it yet. I tested all tree options and I still get an error that lightdm could not been started. For the moment I use lxmd and it looks horrible.
As mentioned above I updated the system several times I guess since F35/36.
Something must have been changed (even if it is just overwriting the config file while updating). Then wen I see the systemctl status lightdm it just says about something with dependencies is not fine.
I tested fedora mate in a virtual machine and there it works I could also change from slick to the gtk greeter in /etc/lightdm/lightdm.conf
The DM has been made years ago and has been made for Hardware where is now “old” but still works. So to not trow away the hardware I still use it for my Boy. He plays SuperMario and is happy with that.
This argument is ok for Gnome where gets pushed to the best and really is more for new Hardware. The majority of the spins are more for older device and even Rasppery Pi, where also not has hardware specs to spoil.
I really wish that we do distinguish between spins and that a low memory/spec version is available without have to download crap where belongs to a desktop where has been made to replace MS-Windows mainly for the Chinese market and newer Hardware.
As an example lightdm-basic and lightdm could make clear a separation. If we use the -basic package for example it should not be tight to a specific distribution’s desktop as we do have now.
The problem is how dnf handles multiple providers of a feature, in this case the lightdm-greeter feature. So far dns does not have a mind reader feature to help to chose the right package to provide that feature, so it just takes the first available to install.
There is nothing deepin can do about and there is nothing lightdm can do about it, unless you remove the flexibility and only allow one greeter implementation in connection with lightdm.
If they name their lightdm deepin-lightdm, we do have the name lightdm free to use and install it as an independent project … as we do with all the other ones. SDDM also not pushes the whole KDE stuff to use it on a other project, right?
Or name their greeter/config different and make it similar as we do on fedora … that’s why I asked to create a Fedora Folder as they do for Archlinux and Debian … is this not best practice ?
SDDM install list:
sudo dnf install sddm
Last metadata expiration check: 0:33:13 ago on Tue 12 Dec 2023 08:37:09 AM -03.
Package Architecture Version Repository Size
sddm x86_64 0.20.0-4.fc39 fedora 1.8 M
aml x86_64 0.3.0-2.fc39 fedora 20 k
libseat x86_64 0.8.0-1.fc39 fedora 29 k
neatvnc x86_64 0.7.1-1.fc39 updates 65 k
sddm-wayland-generic noarch 0.20.0-4.fc39 fedora 11 k
turbojpeg x86_64 2.1.4-3.fc39 fedora 214 k
weston x86_64 12.0.2-1.fc39 fedora 661 k
weston-libs x86_64 12.0.2-1.fc39 fedora 419 k
Install 8 Packages
Total download size: 3.1 M
Installed size: 6.2 M
Is this ok [y/N]:
The core LightDM project does not provide any greeter with it; you should install a greeter appropriate to your system. Popular greeter projects are:
sudo dnf info lightdm:
Last metadata expiration check: 0:44:32 ago on Tue 12 Dec 2023 08:37:09 AM -03.
Name : lightdm
Version : 1.32.0
Release : 5.fc39
Architecture : x86_64
Size : 585 k
Source : lightdm-1.32.0-5.fc39.src.rpm
Repository : @System
From repo : fedora
Summary : A cross-desktop Display Manager
URL : https://www.freedesktop.org/wiki/Software/LightDM/
License : (LGPLv2 or LGPLv3) and GPLv3+
Description : Lightdm is a display manager that:
: * Is cross-desktop - supports different desktops
: * Supports different display technologies
: * Is lightweight - low memory usage and fast performance
Ok, so should we make the note that we can install lightdm with the specific greeter where?
If deepin does it this way too, lightdm will not push the deepin stuff anymore right?
Canonical is making the Note on their project as I block-quoted before.
I am not a new Linux user, but the whole thing made me almost crazy because of missing information about the greeter. I found out if you install just the greeter the rest where is needed get pushed as dependency.
What is best practice to communicate this then? I just thy to find a general solution for the majority of users.
Hello @ilikelinux , @vekruse ,
As @chrisawi has provided a solution to the original post I suggest @ilikelinux mark Chris’s post appropriately as the solution and make a new topic for the continued discussion about how to correct the greeter packaging since this discussion is sort of skewing from the original.