I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
-- Rex
Patrick O'Callaghan wrote:
On Fri, 2016-03-11 at 13:13 -0600, Rex Dieter wrote:
I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
If sddm still doesn't support the Gnome keyring, then yes. That's the only reason I use it.
Good point, we don't seem to have any local bug tracking that. I'll make one.
-- Rex
Rex Dieter wrote:
Patrick O'Callaghan wrote:
On Fri, 2016-03-11 at 13:13 -0600, Rex Dieter wrote:
I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
If sddm still doesn't support the Gnome keyring, then yes. That's the only reason I use it.
Good point, we don't seem to have any local bug tracking that. I'll make one.
Tracked here, https://bugzilla.redhat.com/show_bug.cgi?id=1317066
-- Rex
Rex Dieter composed on 2016-03-11 13:13 (UTC-0600):
I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
I can't be a maintainer, but as it's the only DM I'm aware of that provides required functionality, I hope it need not be retired before something provides functionality equivalent to it.
Felix Miata wrote:
Rex Dieter composed on 2016-03-11 13:13 (UTC-0600):
I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
I can't be a maintainer, but as it's the only DM I'm aware of that provides required functionality, I hope it need not be retired before something provides functionality equivalent to it.
OK, I'll bite. What counts as "required functionality" for you?
In particular, what's missing from other dm's (sddm in particular)?
-- Rex
Rex Dieter composed on 2016-03-11 18:13 (UTC-0600):
Felix Miata wrote:
Rex Dieter composed on 2016-03-11 13:13 (UTC-0600):
I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
I can't be a maintainer, but as it's the only DM I'm aware of that provides required functionality, I hope it need not be retired before something provides functionality equivalent to it.
OK, I'll bite. What counts as "required functionality" for you?
In particular, what's missing from other dm's (sddm in particular)?
I don't remember the whole list of functionality missing when last I checked sddm or lightdm, but at the top of the list I distinctly remember missing remained the ability to specify a list of specific users to be *included* in the greeter's userlist. (I never even look at gdm, as I never install Gnome, and wish I could keep the entirely its support system uninstalled.)
Who is sddm's upstream? I don't see it as a possible product in searching https://bugs.kde.org/ and don't remember if I ever found a bug report anywhere asking for it.
Felix Miata wrote:
Rex Dieter composed on 2016-03-11 18:13 (UTC-0600):
Felix Miata wrote:
Rex Dieter composed on 2016-03-11 13:13 (UTC-0600):
I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
I can't be a maintainer, but as it's the only DM I'm aware of that provides required functionality, I hope it need not be retired before something provides functionality equivalent to it.
OK, I'll bite. What counts as "required functionality" for you?
In particular, what's missing from other dm's (sddm in particular)?
I don't remember the whole list of functionality missing when last I checked sddm or lightdm, but at the top of the list I distinctly remember missing remained the ability to specify a list of specific users to be *included* in the greeter's userlist.
That's something that only kdm can do as far as I'm aware.
Who is sddm's upstream?
-- Rex
Rex Dieter composed on 2016-03-11 19:05 (UTC+0600):
Felix Miata wrote:
Rex Dieter composed on 2016-03-11 18:13 (UTC-0600):
Felix Miata wrote:
Rex Dieter composed on 2016-03-11 13:13 (UTC-0600):
I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
I can't be a maintainer, but as it's the only DM I'm aware of that provides required functionality, I hope it need not be retired before something provides functionality equivalent to it.
OK, I'll bite. What counts as "required functionality" for you?
In particular, what's missing from other dm's (sddm in particular)?
I don't remember the whole list of functionality missing when last I checked sddm or lightdm, but at the top of the list I distinctly remember missing remained the ability to specify a list of specific users to be *included* in the greeter's userlist.
That's something that only kdm can do as far as I'm aware.
Who is sddm's upstream?
I've never been able to figure out how to search and get non-zero results reasonably less than infinity in any github tracker. :-(
Hi,
I'm currently using kdm on my home desktop computer because of multiseat support.
Looking at https://github.com/sddm/sddm/issues/78 , it looks like it should be possible to have multiseat support in the sddm. I will try to migrate to it and let you know about the result.
Radek Novacek
On Friday 11 of March 2016 13:13:09 Rex Dieter wrote:
I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
-- Rex _______________________________________________ kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org
Hi,
it seems that multiseat is not operational in the sddm yet. I was not able to make it work so far.
Nevertheless I don't think multiseat is considered supported feature and it requires some hacks in udev and kdm configuration anyway. Feel free to EOL kdm, I'll figure out some other solution (compiling kdm myself maybe).
Thanks,
Radek
On Tuesday 15 of March 2016 08:31:56 Radek Novacek wrote:
Hi,
I'm currently using kdm on my home desktop computer because of multiseat support.
Looking at https://github.com/sddm/sddm/issues/78 , it looks like it should be possible to have multiseat support in the sddm. I will try to migrate to it and let you know about the result.
Radek Novacek
On Friday 11 of March 2016 13:13:09 Rex Dieter wrote:
I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
-- Rex _______________________________________________ kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org
kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org
Sérgio Basto wrote:
On Sex, 2016-03-11 at 13:13 -0600, Rex Dieter wrote:
I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
How I change the default DM from kdm to ssdm ?
systemctl enable kdm --force
(to enable it for all future boots)
-- Rex
I'm confused. Shouldn't that be:
systemctl enable ssdm --force or systemctl disable kdm --force?
On Fri, Apr 1, 2016 at 9:58 AM, Rex Dieter rdieter@math.unl.edu wrote:
Sérgio Basto wrote:
On Sex, 2016-03-11 at 13:13 -0600, Rex Dieter wrote:
I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
How I change the default DM from kdm to ssdm ?
systemctl enable kdm --force
(to enable it for all future boots)
-- Rex
kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org
Mark Haney wrote:
I'm confused. Shouldn't that be:
systemctl enable ssdm --force or systemctl disable kdm --force?
Oops, I read that backwards, so yeah only:
systemctl enable ssdm --force
On Fri, Apr 1, 2016 at 9:58 AM, Rex Dieter rdieter@math.unl.edu wrote:
Sérgio Basto wrote:
On Sex, 2016-03-11 at 13:13 -0600, Rex Dieter wrote:
I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
How I change the default DM from kdm to ssdm ?
systemctl enable kdm --force
(to enable it for all future boots)
\
Huh. This is odd. When I run that command I get this: (withor without the --force option)
@aurelian ~]$ systemctl enable ssdm Failed to execute operation: No such file or directory
@aurelian ~]$ systemctl enable ssdm.service Failed to execute operation: No such file or directory
Granted, I'm on a new Fedora 23 install, so I am not sure if this is expected in that case or not.
On Fri, Apr 1, 2016 at 10:05 AM, Rex Dieter rdieter@math.unl.edu wrote:
Mark Haney wrote:
I'm confused. Shouldn't that be:
systemctl enable ssdm --force or systemctl disable kdm --force?
Oops, I read that backwards, so yeah only:
systemctl enable ssdm --force
On Fri, Apr 1, 2016 at 9:58 AM, Rex Dieter rdieter@math.unl.edu wrote:
Sérgio Basto wrote:
On Sex, 2016-03-11 at 13:13 -0600, Rex Dieter wrote:
I am considering finally EOL'ing kdm in time for fedora 24, anyone still interested in keeping it alive?
How I change the default DM from kdm to ssdm ?
systemctl enable kdm --force
(to enable it for all future boots)
\ _______________________________________________ kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org
On Sex, 2016-04-01 at 10:10 -0400, Mark Haney wrote:
Huh. This is odd. When I run that command I get this: (withor without the --force option)
@aurelian ~]$ systemctl enable ssdm Failed to execute operation: No such file or directory
@aurelian ~]$ systemctl enable ssdm.service Failed to execute operation: No such file or directory
systemctl disable kdm systemctl enable sddm
Granted, I'm on a new Fedora 23 install, so I am not sure if this is expected in that case or not.
On Fri, Apr 1, 2016 at 10:05 AM, Rex Dieter rdieter@math.unl.edu wrote:
Mark Haney wrote:
I'm confused. Shouldn't that be:
systemctl enable ssdm --force or systemctl disable kdm --force?
Oops, I read that backwards, so yeah only:
systemctl enable ssdm --force
On Fri, Apr 1, 2016 at 9:58 AM, Rex Dieter rdieter@math.unl.edu wrote:
Sérgio Basto wrote:
On Sex, 2016-03-11 at 13:13 -0600, Rex Dieter wrote:
I am considering finally EOL'ing kdm in time for fedora 24,
anyone
still interested in keeping it alive?
How I change the default DM from kdm to ssdm ?
systemctl enable kdm --force
(to enable it for all future boots)
\ _______________________________________________ kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject. org
-- Mark Haney ::: Senior Systems Engineer VIF International Education P.O. Box 3566 ::: Chapel Hill, N.C. 27515 ::: USA 919-265-5006 office
Global learning for all. www.vifprogram.com Find VIF on Facebook | Twitter | LinkedIn Recognized as a ‘Best for the World’ B Corp! _______________________________________________ kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.or g
Sérgio Basto wrote:
On Sex, 2016-04-01 at 10:10 -0400, Mark Haney wrote:
Huh. This is odd. When I run that command I get this: (withor without the --force option)
@aurelian ~]$ systemctl enable ssdm Failed to execute operation: No such file or directory
@aurelian ~]$ systemctl enable ssdm.service Failed to execute operation: No such file or directory
systemctl disable kdm systemctl enable sddm
The explicit disable is not needed, but you *do* need to run any of those systemctl commands with priviledge (as root)
This should be sufficient:
sudo systemctl enable sddm --force
-- Rex
Which, when I ran them as my user I was prompted (graphically) to enter the root password, which I duly supplied. But, I did try it using sudo and as root directly:
[mark.haney@aurelian ~]$ sudo systemctl enable ssdm Failed to execute operation: No such file or directory [mark.haney@aurelian ~]$ sudo systemctl enable ssdm --force Failed to execute operation: No such file or directory [mark.haney@aurelian ~]$ sudo su [root@aurelian mark.haney]# systemctl enable ssdm Failed to execute operation: No such file or directory [root@aurelian mark.haney]# systemctl enable ssdm --force Failed to execute operation: No such file or directory
On Fri, Apr 1, 2016 at 10:20 AM, Rex Dieter rdieter@math.unl.edu wrote:
Sérgio Basto wrote:
On Sex, 2016-04-01 at 10:10 -0400, Mark Haney wrote:
Huh. This is odd. When I run that command I get this: (withor without the --force option)
@aurelian ~]$ systemctl enable ssdm Failed to execute operation: No such file or directory
@aurelian ~]$ systemctl enable ssdm.service Failed to execute operation: No such file or directory
systemctl disable kdm systemctl enable sddm
The explicit disable is not needed, but you *do* need to run any of those systemctl commands with priviledge (as root)
This should be sufficient:
sudo systemctl enable sddm --force
-- Rex _______________________________________________ kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org
sddm , not ssdm :-)
On 04/01/2016 11:26 AM, Mark Haney wrote:
Which, when I ran them as my user I was prompted (graphically) to enter the root password, which I duly supplied. But, I did try it using sudo and as root directly:
[mark.haney@aurelian ~]$ sudo systemctl enable ssdm Failed to execute operation: No such file or directory [mark.haney@aurelian ~]$ sudo systemctl enable ssdm --force Failed to execute operation: No such file or directory [mark.haney@aurelian ~]$ sudo su [root@aurelian mark.haney]# systemctl enable ssdm Failed to execute operation: No such file or directory [root@aurelian mark.haney]# systemctl enable ssdm --force Failed to execute operation: No such file or directory
On Fri, Apr 1, 2016 at 10:20 AM, Rex Dieter <rdieter@math.unl.edu mailto:rdieter@math.unl.edu> wrote:
Sérgio Basto wrote: > On Sex, 2016-04-01 at 10:10 -0400, Mark Haney wrote: >> Huh. This is odd. When I run that command I get this: (withor >> without the --force option) >> >> @aurelian ~]$ systemctl enable ssdm >> Failed to execute operation: No such file or directory >> >> @aurelian ~]$ systemctl enable ssdm.service >> Failed to execute operation: No such file or directory > > systemctl disable kdm > systemctl enable sddm The explicit disable is not needed, but you *do* need to run any of those systemctl commands with priviledge (as root) This should be sufficient: sudo systemctl enable sddm --force -- Rex _______________________________________________ kde mailing list kde@lists.fedoraproject.org <mailto:kde@lists.fedoraproject.org> http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org--
Mark Haney ::: Senior Systems Engineer
*VIF*International Education P.O. Box 3566 ::: Chapel Hill, N.C. 27515 ::: USA 919-265-5006office
Global learning for all. www.vifprogram.com http://www.vifprogram.com/?utm_source=signature&utm_medium=email&utm_campaign=VIF Find VIF onFacebook http://facebook.com/VIFInternationalEducation|Twitter https://twitter.com/vifglobaled |LinkedIn http://www.linkedin.com/company/vif-international-education
Recognized as a‘Best for the World’ http://bestfortheworld.bcorporation.net/B Corp!
kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org
Okay, so I'm an idiot. It's Friday. Thanks for catching that.
On Fri, Apr 1, 2016 at 10:30 AM, Patrick Boutilier boutilpj@ednet.ns.ca wrote:
sddm , not ssdm :-)
On 04/01/2016 11:26 AM, Mark Haney wrote:
Which, when I ran them as my user I was prompted (graphically) to enter the root password, which I duly supplied. But, I did try it using sudo and as root directly:
[mark.haney@aurelian ~]$ sudo systemctl enable ssdm Failed to execute operation: No such file or directory [mark.haney@aurelian ~]$ sudo systemctl enable ssdm --force Failed to execute operation: No such file or directory [mark.haney@aurelian ~]$ sudo su [root@aurelian mark.haney]# systemctl enable ssdm Failed to execute operation: No such file or directory [root@aurelian mark.haney]# systemctl enable ssdm --force Failed to execute operation: No such file or directory
On Fri, Apr 1, 2016 at 10:20 AM, Rex Dieter <rdieter@math.unl.edu mailto:rdieter@math.unl.edu> wrote:
Sérgio Basto wrote: > On Sex, 2016-04-01 at 10:10 -0400, Mark Haney wrote: >> Huh. This is odd. When I run that command I get this: (withor >> without the --force option) >> >> @aurelian ~]$ systemctl enable ssdm >> Failed to execute operation: No such file or directory >> >> @aurelian ~]$ systemctl enable ssdm.service >> Failed to execute operation: No such file or directory > > systemctl disable kdm > systemctl enable sddm The explicit disable is not needed, but you *do* need to run any of those systemctl commands with priviledge (as root) This should be sufficient: sudo systemctl enable sddm --force -- Rex _______________________________________________ kde mailing list kde@lists.fedoraproject.org <mailto:kde@lists.fedoraproject.org>http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org
--
Mark Haney ::: Senior Systems Engineer
*VIF*International Education P.O. Box 3566 ::: Chapel Hill, N.C. 27515 ::: USA 919-265-5006office
Global learning for all. www.vifprogram.com < http://www.vifprogram.com/?utm_source=signature&utm_medium=email&utm...
Find VIF onFacebook http://facebook.com/VIFInternationalEducation|Twitter https://twitter.com/vifglobaled |LinkedIn http://www.linkedin.com/company/vif-international-education
Recognized as a‘Best for the World’ http://bestfortheworld.bcorporation.net/B Corp!
kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org
kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org
Am 01.04.2016 um 16:26 schrieb Mark Haney:
Which, when I ran them as my user I was prompted (graphically) to enter the root password, which I duly supplied. But, I did try it using sudo and as root directly:
[mark.haney@aurelian ~]$ sudo systemctl enable ssdm Failed to execute operation: No such file or directory
so just install it before try to enable it
On Sex, 2016-04-01 at 09:20 -0500, Rex Dieter wrote:
Sérgio Basto wrote:
On Sex, 2016-04-01 at 10:10 -0400, Mark Haney wrote:
Huh. This is odd. When I run that command I get this: (withor without the --force option)
@aurelian ~]$ systemctl enable ssdm Failed to execute operation: No such file or directory
@aurelian ~]$ systemctl enable ssdm.service Failed to execute operation: No such file or directory
systemctl disable kdm systemctl enable sddm
The explicit disable is not needed, but you *do* need to run any of those systemctl commands with priviledge (as root)
This should be sufficient:
sudo systemctl enable sddm --force
OK ,
Anyway, the latest updates in F24 breaks my kdm, i.e. X doesn't start when I got kdm as DM, now with sddm started working again . I don't know if you like open a bug report but I'm happy with sddm as DM, so I will not open it. I found another issue with sddm, doesn't offer to use MATE desktop .
Thanks,
-- Rex _______________________________________________ kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.or g
Is KDM actually working for anyone using F24? When I try, (sddm not installed; systemctl enable kdm.service, otherwise graphical.target doesn't start X at all) it starts in what looks like maybe a 4-bit color mode, showing only the upper left section 800x600 or maybe 640x480 of a (native) 1680x1050 theme.
Felix Miata wrote:
Is KDM actually working for anyone using F24?
Yes, testing this update worked for me: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e8ad31da94
(previously default theming was broken, perhaps that was what you were experiencing)
-- Rex
Rex Dieter composed on 2016-06-15 06:05 (UTC-0500):
Felix Miata wrote:
Is KDM actually working for anyone using F24?
Yes, testing this update worked for me: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e8ad31da94
(previously default theming was broken, perhaps that was what you were experiencing)
I no longer recall which F24 host led to my OP, but on F24 host hpg33 with no dm installed except kdm, and default target multi-user, neither 5 on kernel cmdline nor 'systemctl isolate graphical.target' starts the kdm greeter. Plasma apparently does work normally via startx. There are inexplicably 3 kdm-themes installed, F22 (-), F23 (-) and F24 (-core) (plus 4 kde themes).
Am 01.04.2016 um 16:00 schrieb Mark Haney:
I'm confused. Shouldn't that be:
systemctl enable ssdm --force or systemctl disable kdm --force
think logical:
* disable means disable and needs no force * you are not required to run a DM at all * so switching can only be enable * force because they exclude each other
-
Felix Miata -
Mark Haney -
Patrick Boutilier -
Patrick O'Callaghan -
Radek Novacek -
Reindl Harald -
Rex Dieter -
Sérgio Basto