this is more a feature request than a issue report.
Currently i'm thinking about to use sddm for mate desktop in f20 as mate maintainer.
Adding support for mate-keyring is very easy.
Simply change the pam file to
auth [success=done ignore=ignore default=bad] pam_selinux_permit.so
auth required pam_env.so
auth substack system-auth
-auth optional pam_gnome_keyring.so
-auth optional pam_mate_keyring.so
auth include postlogin
account required pam_nologin.so
account include system-auth
password include system-auth
session required pam_selinux.so close
session required pam_loginuid.so
session optional pam_console.so
-session optional pam_ck_connector.so
session required pam_selinux.so open
session optional pam_keyinit.so force revoke
session required pam_namespace.so
session include system-auth
-session optional pam_gnome_keyring.so auto_start
-session optional pam_mate_keyring.so auto_start
session include postlogin
It would be very nice to do this for rawhide/f19/f18
thanks for your report. I pushed the change (commit 195b5eb95c) to all three repositories.
It will be included in the next update some time this week.
thank you. i've a off topic question.
If i use sddm, the .xseessionerror log won't be updated anymore, means no new information if seesion is started is written.
Is this a known issue?
Tested with rawhide and f18.
No, this exactly isn't known to me. I know there are some issues with the initial environment settings and session configuration. I haven't really investigated it in-depth so far unfortunately.
Could you please open an other bug with this? Please include as much information as you can.
sddm-0.2.0-0.130821.git.e707e229.fc18 has been submitted as an update for Fedora 18.
sddm-0.2.0-0.130821.git.e707e229.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing sddm-0.2.0-0.130821.git.e707e229.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
sddm-0.2.0-0.1.20130821gite707e229.fc18 has been submitted as an update for Fedora 18.
sddm-0.2.0-0.1.20130821gite707e229.fc19 has been submitted as an update for Fedora 19.
I just repushed the package, please note you'll have to run yum distro-sync or yum downgrade to get this version.
Sorry for the confusion.
np, but the issue is that the old version is in f20 stable and rawhide (f20 is branched today)
Why not using sddm-0.2.0-0.2.20130821gite707e229.fc19 to get higher version (0.2 instead 0.1 before date). This should update the old version
It does not, unfortunately. The number would have to be higher than 130821 which would be very confusing...
It is an issue we there is a "newer" version in fc20 and fc21 though. This will be resolved either by users manually installing this (I doubt the wrong version is widespread) and the further packages or after release of the actual sddm-0.2.0 which will make the package's release just 1 instead of 0 and checkout information, thus updating it automatically.
I untagged the f20 and f21 builds in Koji yesterday, as soon as I noticed the wrong versioning, so I'm not sure they even entered a compose (I hope not). In any case, today's compose for f20 has the correctly-versioned build, Rawhide the old 0.1.5 build altogether (the new one was built and should be in tomorrow's compose).
sddm-0.2.0-0.4.20130821gite707e229.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
sddm-0.2.0-0.4.20130821gite707e229.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.