[opensuse-kde] Overview of current Staging I wrt Plasma 5 transition
Hi All, Many of you may already know I'm working on a pre-integration work relate to Plasma 5 in Staging Project - Switch Plasma 5 to default KDE desktop. The goal is make sure we can smoothly move to Plasma 5 as default KDE desktop before those changes get into Factory(Tumbleweed). This mail is a short report, give you a quick overview of the current status, and understand where we are now. All works is in Staging I[1] currently, so it would not effect the rest of stagings or even Factory. Thanks openSUSE KDE Team, the packages are almost ready, and few issues also got fixed when we observed it in openQA, now, what things already done(or almost done)? * PLasma 5 packages and its deps are ready[1] * update patterns[2] * skelcd-control update been submitted, waiting for merge[3] * a fresh installation can pass openQA test[4] - all green now! Everything looks quite well. But during adjusting openQA tests, I discover we still have some more work need to do to get this transition pass Staging Project, * Update test can not pass openQA: it tested update from a Tumbleweed snapshot to current Staging I, according to the result[5], it seems still need some more work, 1) kdm still there! and since DISPLAYMANAGER param doesn't change, system is launch kdm indeed. 2) per above, if user enabled autologin, kdm may bring user to whatever desktop session after update, because kdebase4-session got removed already, and if more than one desktop session(eg. icewm) installed there, it may boot into wrong session than what you expect - plasma5 session. So I think we need a better way to handle update. * Improve sddm: sddm may better to handle with AUTOLOGIN, the installer provides a autologin option there, but it will not work with sddm. This is the current status of Staging I. If you checked Staging I and think I'm missing something there, please let me know! And any feedback welcome :) Note: I'll random rebase Staging I, ie. re-build Staging I with the latest souce from Factory at some point, make sure Staging I not so far from current Tumbleweed snapshot. Best regards, Max [1] https://build.opensuse.org/project/show/openSUSE:Factory:Staging:I [2] https://build.opensuse.org/request/show/304878 [3] https://github.com/yast/skelcd-control-openSUSE/pull/31 [4] https://openqa.opensuse.org/tests/60112 [5] https://openqa.opensuse.org/tests/60110 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Just my 2 cents here, for the moment... Am Montag, 4. Mai 2015, 17:03:57 schrieb Max Lin:
1) kdm still there! and since DISPLAYMANAGER param doesn't change, system is launch kdm indeed.
Well, IMHO we cannot just replace kdm yet. SDDM still misses a lot of features, especially regarding remote login, which is non-existent there. See the TODO list: https://github.com/sddm/sddm/wiki/TODO That doesn't mean I'm against SSDM for default, if it works. It doesn't really work on 13.2 (which I am still using), in particular logout doesn't work. But as I understand it, this is fixed with a newer version of gnome-keyring- pam.
2) per above, if user enabled autologin, kdm may bring user to whatever desktop session after update, because kdebase4-session got removed already, and if more than one desktop session(eg. icewm) installed there, it may boot into wrong session than what you expect - plasma5 session. So I think we need a better way to handle update.
Yes, /etc/sysconfig/windowmanager needs to be updated. No idea how to handle this though. Maybe replace "kde-plasma" with "plasma5" (or whatever) with sed in a postinstall script of sddm?
* Improve sddm: sddm may better to handle with AUTOLOGIN, the installer provides a autologin option there, but it will not work with sddm.
That should be done anyway, I suppose. We need a patch here IMHO (like for every other DM), we cannot just ignore the old way. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 04 of May 2015 14:33:04 Wolfgang Bauer wrote:
Just my 2 cents here, for the moment...
Am Montag, 4. Mai 2015, 17:03:57 schrieb Max Lin:
1) kdm still there! and since DISPLAYMANAGER param doesn't change, system is launch kdm indeed.
Well, IMHO we cannot just replace kdm yet. SDDM still misses a lot of features, especially regarding remote login, which is non-existent there. See the TODO list: https://github.com/sddm/sddm/wiki/TODO I agree here that sddm can't obsolete kdm.
That doesn't mean I'm against SSDM for default, if it works. It doesn't really work on 13.2 (which I am still using), in particular logout doesn't work. But as I understand it, this is fixed with a newer version of gnome-keyring- pam. AFAIK, correct.
2) per above, if user enabled autologin, kdm may bring user to whatever desktop session after update, because kdebase4-session got removed already, and if more than one desktop session(eg. icewm) installed there, it may boot into wrong session than what you expect - plasma5 session. So I think we need a better way to handle update.
Yes, /etc/sysconfig/windowmanager needs to be updated. No idea how to handle this though.
Maybe replace "kde-plasma" with "plasma5" (or whatever) with sed in a postinstall script of sddm? I'm not sure this matters though, the problem is more AFAICS, missing session desktop file (as plasma5-session obsoletes kdebase4-session). We will get this fixed somehow though. =)
* Improve sddm: sddm may better to handle with AUTOLOGIN, the installer provides a autologin option there, but it will not work with sddm.
That should be done anyway, I suppose. We need a patch here IMHO (like for every other DM), we cannot just ignore the old way. Yep, i should come up with a patch today to handle autologin user...
Cheers, Hrvoje
Kind Regards, Wolfgang
Am Montag, 4. Mai 2015, 14:48:59 schrieb šumski:
I agree here that sddm can't obsolete kdm.
Fine. Thanks for your confirmation... I wanted to bring that one up already for quite some time. Btw, I am volunteering for maintaining the packages, if necessary. ;)
That doesn't mean I'm against SSDM for default, if it works. It doesn't really work on 13.2 (which I am still using), in particular logout doesn't work. But as I understand it, this is fixed with a newer version of gnome-keyring- pam.
AFAIK, correct.
There are upstream bugreports about this (which I've been following) which haven't seen any real action unfortunately. And there are Kubuntu bugreports about this, which would confirm that it is fixed with newer GNOME updates, So if you don't see the problem now (I can still reproduce it here on 13.2), I'd rather believe this is fixed in Tumbleweed... ;)
2) per above, if user enabled autologin, kdm may bring user to whatever desktop session after update, because kdebase4-session got removed already, and if more than one desktop session(eg. icewm) installed there, it may boot into wrong session than what you expect - plasma5 session. So I think we need a better way to handle update.
Yes, /etc/sysconfig/windowmanager needs to be updated. No idea how to handle this though.
Maybe replace "kde-plasma" with "plasma5" (or whatever) with sed in a postinstall script of sddm?
I'm not sure this matters though, the problem is more AFAICS, missing session desktop file (as plasma5-session obsoletes kdebase4-session). We will get this fixed somehow though. =)
Well, it does matter (still) AFAICT. ATM, we still have the displaymanager startup script, that evaluates /etc/sysconfig/windowmanager. It falls back to xdm if it cannot find the one .desktop file specified as DEFAULT_WM (i.e. kde-plasma.desktop in this case). If SDDM is enabled via "systemctl enable sddm", it doesn't matter though. So if you are using it this way, you are right of course. But that's not the default yet, or have I missed something? Another option would be to rename Plasma5's .desktop file of course, but I don't think we should go that way. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
In data lunedì 4 maggio 2015 15:30:55, Wolfgang Bauer ha scritto:
So if you don't see the problem now (I can still reproduce it here on 13.2), I'd rather believe this is fixed in Tumbleweed... ;)
As far as I can see here in Tumbleweed (3 machines), logout works as expected using SDDM.
If SDDM is enabled via "systemctl enable sddm", it doesn't matter though. So if you are using it this way, you are right of course.
IIRC the SDDM package uses display-manager.service, so the one which reads from /etc/sysconfig/displaymanager. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79
Am Montag, 4. Mai 2015, 15:34:10 schrieb Luca Beltrame:
In data lunedì 4 maggio 2015 15:30:55, Wolfgang Bauer ha scritto:
So if you don't see the problem now (I can still reproduce it here on 13.2), I'd rather believe this is fixed in Tumbleweed... ;)
As far as I can see here in Tumbleweed (3 machines), logout works as expected using SDDM.
Yes, that's what I was expecting. Therefore my smiley. But thanks for confirming. ;)
If SDDM is enabled via "systemctl enable sddm", it doesn't matter though. So if you are using it this way, you are right of course.
IIRC the SDDM package uses display-manager.service, so the one which reads from /etc/sysconfig/displaymanager.
Right. But I don't know sumski's setup. With the original displaymanager.service I do see this as a problem though, and I do think it matters, as mentioned. If I am mistaken, please correct me. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (4)
-
Luca Beltrame -
Max Lin -
Wolfgang Bauer -
šumski