The desktop file isn't working for me currently. It also has it's name set incorrectly. It's name text is "Login Window" instead of "LightDM Settings" and nothing comes up when I run it. If I run the contents of the Exec= line in a terminal it works fine though.
Search Criteria
Package Details: lightdm-settings 2.0.6-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/lightdm-settings.git (read-only, click to copy) |
---|---|
Package Base: | lightdm-settings |
Description: | A configuration tool for the LightDM display manager |
Upstream URL: | https://github.com/linuxmint/lightdm-settings |
Licenses: | GPL3 |
Submitter: | Santi-Burgos |
Maintainer: | Santi-Burgos |
Last Packager: | Santi-Burgos |
Votes: | 52 |
Popularity: | 0.25 |
First Submitted: | 2017-04-16 22:10 (UTC) |
Last Updated: | 2024-12-07 23:30 (UTC) |
Dependencies (7)
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- lightdm-slick-greeter (lightdm-slick-greeter-mint-themeAUR)
- polkit (polkit-gitAUR, polkit-consolekitAUR)
- python-gobject
- python-setproctitle
- python-xapp
- lightdm-guestAUR (optional) – Enable guest session options
Required by (2)
Sources (1)
Haystack commented on 2019-04-13 15:37 (UTC)
Magotchi commented on 2018-06-27 15:38 (UTC) (edited on 2018-06-27 15:43 (UTC) by Magotchi)
Before your most recent change, this package was clean and simple. It installed Linux Mint's program to edit Slick Greeter's settings.
Now it:
-
installs a systemd service which automatically forces an "autologin" group to exist and automatically adds all normal users to it
-
enables that systemd service, so that the above process happens on every boot
-
upon uninstallation, deletes that autologin group, even if it has users assigned to it
Please reconsider this change. LightDM autologin is already well-documented in the Arch wiki, plenty of people don't use autologin at all, your change of system-wide group configuration may not be what every user wants (and might even be detrimental upon uninstallation), even major packages like apache don't automatically enable their systemd services, and this process doesn't even fully enable autologin (as lightdm.conf still requires edits to finish the process). A simple package that just installs the software from upstream is great, and we can be free to configure our systems the way we want.
I'm sorry to nitpick. I know you're trying to help, and I appreciate that you keep these packages maintained.
Santi-Burgos commented on 2018-06-25 22:18 (UTC)
@joks @papa33: Thanks for the information, I created an incident on Github for Linuxmint related to this package, I hope that they can update it soon with the changes done on their side, else you might have to give me some time to test, check and update the PKGBUILD with the temporary patch, specially since I have been busy at work to check this
joks commented on 2018-06-16 12:26 (UTC)
yes, i also like papa33 use manjaro patch and its looks like all works good i can change background for lightdm-slick without any problem
papa33 commented on 2018-06-15 14:10 (UTC)
Hello, I have tried to modify your PKGBUILD to include the Manjaro patch, and it just worked.
Santi-Burgos commented on 2018-06-14 14:12 (UTC)
@joks: actually, I have checked the way on how manjaro team has handled things and we both have been working (unofficially) on changes made for each other. Although I have a pending task on handle things their way (both lightdm-slick-greeter and lightdm-settings) , because in their particular situation they assume that lightdm is already installed, whereas if I do that I encounter error while compiling or copying files.
I still might have to do some testing first, because if I pull an update without measuring consequences, you might end up with no being able to update or with a broken app, which is not something I want to do, also if you encounter the issue you can report it upstream to Linux Mint, so they can check this issue on their side as well
joks commented on 2018-06-14 05:57 (UTC)
hi, can you apply patch from manjaro to lightdm-settings from here:
https://github.com/manjaro/packages-community/blob/master/lightdm-settings/user_background.patch
because now arch users can`t change wallpaper for lightdm-slick-greeter at login screen. default with new lightdm-slick is shown wallpaper from desktop and in lightdm-settings missing option to turn this feature off. only manjaro team patch in their repo ligthdm-settings
Pinned Comments
Santi-Burgos commented on 2017-04-16 22:57 (UTC) (edited on 2018-07-09 15:59 (UTC) by Santi-Burgos)
A couple of things related to this package:
If you upgraded from version 1.2.2-1 to 1.2.2-2, check folders /etc/systemd/system/ and /usr/bin (both as root), you should see a file named "add-autologin-group.service" in the former and "add-autologin-group.script" in the latter, since this new upgrade reverts the changes from 1.2.1 to 1.2.2 after a lot of complains about it, you need to delete the files manually after stopping the systemd service first; it should mean no harm to any configuration on the system so you can delete them safely
If you upgraded from version 1.2.1 to 1.2.2, check the /etc/systemd/system/ folder (as root), you should see a file named "add-autologin-group.serv", rename it as "add-autologin-group.service", this is supposed to be a new service ported from the Manjaro team but somehow I slipped and I updated it with this issue, I already fixed it, but in case you see any "add-autologin-group.service not available" error, this is a manual solving situation. My apologies on this particular situation
It is the companion setting app for lightdm-slick-greeter (which I maintain also), if in the future it allows to check also on lightdm settings itself, I will remove or upgrade dependencies according to it
This package has nothing to do with the lightdm-gtk-greeter-settings, so you can have both installed (for now), if later I see that it allows to configure settings on any greeter (which I don't think that will be possible) I will think on making it a conflicting package
Any problems or bugs, you can explain it to me as detailed as possible so I can try to test it and/or report it to upstream