#8232 closed enhancement (fixed)
sddm-0.14.0
Reported by: | Douglas R. Reno | Owned by: | Douglas R. Reno |
---|---|---|---|
Priority: | normal | Milestone: | 8.0 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
New minor version
https://github.com/sddm/sddm/wiki/0.14.0-Release-Announcement
See above for changes. There are some ones in there for PAM fixes (Ken?)
Change History (17)
comment:1 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 9 years ago
It looks like there are some instructions and explanations, which are good only for the sysv version. I'll update (maybe only tomorrow), but I won't tag it until it's been reviewed by systemd editors.
comment:3 by , 9 years ago
Updated at r17712. Not closing because the instructions are not suitable for systemd, I think.
comment:4 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | assigned → new |
Hi Pierre,
Just looking at it, I'll build it ASAP. Not only are the instructions unsuitable, on a systemd system, they'll cause various issues relating to system stability (overwriting logs, trying to execute consolekit on a system that doesn't have it and hanging the boot process as a result since it'd be needed for graphical.target, etc). I'll take the ticket and build it.
comment:5 by , 9 years ago
Status: | new → assigned |
---|
comment:6 by , 9 years ago
Since you are working on this, it requires extra-cmake-modules.
For me, it still fails to get me to a working icewm-session and at the moment I have not built any desktop environments for testing other variants.
follow-up: 8 comment:7 by , 9 years ago
I'm going to be building LXQt to test this, but I'll have to build XFCE and Plasma5 to test that there are no issues on systemd systems with those as well (there are consolekit things in the dependencies and instructions for the DEs I just mentioned - I need to make those sysv only after seeing if anything else is needed).
What happens when you try to use icewm, out of curiosity?
follow-up: 9 comment:8 by , 9 years ago
Replying to renodr:
I'm going to be building LXQt to test this, but I'll have to build XFCE and Plasma5 to test that there are no issues on systemd systems with those as well (there are consolekit things in the dependencies and instructions for the DEs I just mentioned - I need to make those sysv only after seeing if anything else is needed).
What happens when you try to use icewm, out of curiosity?
I think I _briefly_ get a black screen (less than a second), then it drops me back to the greeter.
I had half-suspected it might be an icewm issue, but I've now installed xfce and the failure continues.
comment:9 by , 9 years ago
Replying to ken@…:
Replying to renodr:
What happens when you try to use icewm, out of curiosity?
I think I _briefly_ get a black screen (less than a second), then it drops me back to the greeter.
I had half-suspected it might be an icewm issue, but I've now installed xfce and the failure continues.
Ken, you must have seen that too, but just in case: I've read somewhere that if neither systemd nor PAM is used, the sddm user should be in the video group. That's all I can think of right now...
comment:10 by , 9 years ago
I have PAM, and I am in the video group. My UID is 500, so a long while ago I had to change a setting in /etc/sddm.conf
# Minimum user id for displayed users MinimumUid=500
(the default is 1000) : that correctly shows ken as the first user, but now he cannot login. However, my lfs user (UID 600) can login.
Changing that value to 499, and rebooting, did not help - I suspect something in the code doesn't expect such a low UID. But since my LFS user can login, the book for sysv is ok if extra-cmake-mod ules are added as a required dep.
I'll treat this as a local issue.
comment:11 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I commented out sddm from the systmed version of the book. Marking as fixed for now at revision 17736.
comment:12 by , 9 years ago
Milestone: | 7.10 → 7.11 |
---|---|
Resolution: | fixed |
Status: | closed → reopened |
Changed my mind. Reopening and moving to 7.11.
comment:14 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Fixed (finally!) at r17750
comment:15 by , 9 years ago
Congratulations, but I am worried about the removal (for systemd) of
-DDBUS_CONFIG_FILENAME=sddm_org.freedesktop.DisplayManager.conf
It seems to me that this file, which by default is named org.freedesktop.DisplayManager.conf, conflicts with the same file of other display managers. See https://bugs.archlinux.org/task/42445. And that does not depend whether systemd or SYS V is used.
comment:16 by , 9 years ago
I just took a look at that. As far as I can tell, neither LXDM or GDM provide that file. I could be wrong though, and I'll probably find that out sometime in the next two weeks (when GNOME-3.22 arrives). It seems that only LightDM includes that file (again, just going off the report... I just had to replace the hard disk in my development machine).
At least in the case of LightDM and SDDM, they both seem to define the same interface... I can imagine it being worse if any others install a conflicting version.
Since I've been relieved from libreoffice, I can take this one