Bug 944821

Summary: Upgrade from 13.2 KDE to 42.1 M2 fails
Product: [openSUSE] openSUSE Distribution Reporter: Takashi Iwai <tiwai>
Component: Upgrade ProblemsAssignee: E-mail List <kde-maintainers>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: dimstar, tiwai, wbauer
Version: Leap 42.1 Milestone2   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 944843    
Attachments: Error message #1 during upgrade
Error message #2 during upgrade
yast2 logs

Description Takashi Iwai 2015-09-08 12:05:18 UTC
I tried upgrading a fresh installed 13.2 KDE image to leap M2.  During the upgrade, two error messages appeared (attached below).  Other than that, the upgrade went smooth.

However, after boot, the user can't login on the installed system.  It goes back to KDM.
Comment 1 Takashi Iwai 2015-09-08 12:05:44 UTC
Created attachment 646503 [details]
Error message #1 during upgrade
Comment 2 Takashi Iwai 2015-09-08 12:06:09 UTC
Created attachment 646504 [details]
Error message #2 during upgrade
Comment 3 Takashi Iwai 2015-09-08 12:13:09 UTC
Created attachment 646506 [details]
yast2 logs
Comment 4 Takashi Iwai 2015-09-08 12:19:49 UTC
It seems that the missing krandrstartup makes KDE login failing.
After creating a dummy exec file ($HOME/bin/krandrstartup), I can login.
Comment 5 Takashi Iwai 2015-09-08 13:39:42 UTC
Note that there are multiple issues in this bug: the first two screenshots show YaST problems, and this should be handled by YaST people.  The login failure after migration is KDE problem.  This should be handled by KDE people.

So I'll clone the bug to handle the first two bugs.  Keep this only for KDE migration problem.
Comment 6 Stephan Kulow 2015-09-09 07:27:14 UTC
I don't think the KDE bug would happen if yast worked flawless - we have a KDE update test in openqa, e.g. https://openqa.opensuse.org/tests/81657
Comment 7 Takashi Iwai 2015-09-09 07:45:18 UTC
(In reply to Stephan Kulow from comment #6)
> I don't think the KDE bug would happen if yast worked flawless - we have a
> KDE update test in openqa, e.g. https://openqa.opensuse.org/tests/81657

Did openQA test login on 13.2 system before upgrading?

kscreen5 obsoletes kscreen that contains krandrstartup script.  I guess kscreen5 should keep providing the same dummy script.
Comment 8 Takashi Iwai 2015-09-09 10:00:50 UTC
It looks like the result of the incomplete upgrade.  After manual "zypper dup" (and resolving by keeping "synaptik"), it starts working.
Comment 9 Wolfgang Bauer 2015-09-09 11:43:46 UTC
(In reply to Takashi Iwai from comment #7)
> kscreen5 obsoletes kscreen that contains krandrstartup script.  I guess
> kscreen5 should keep providing the same dummy script.

Plasma 5 doesn't use/call krandrstartup.
It seems you still have (had) the KDE4 version of startkde, i.e. kdebase4-workspace hasn't been replaced by plasma5-workspace as it should have been.

(In reply to Takashi Iwai from comment #8)
> It looks like the result of the incomplete upgrade.  After manual "zypper
> dup" (and resolving by keeping "synaptik"), it starts working.

synaptiks is the KDE4 version and should be removed.
It is obsoleted by plasma5-desktop.
Comment 10 Wolfgang Bauer 2015-09-09 11:48:35 UTC
(In reply to Wolfgang Bauer from comment #9)
> synaptiks is the KDE4 version and should be removed.
> It is obsoleted by plasma5-desktop.

PS: That "Obsoletes: synaptiks" is still missing in the plasma5-desktop-5.3.2 package in Milestone2, but it is there in the current 5.4.0 package in openSUSE:Leap:42.1.
Changelog entry:
Mon Aug 31 19:03:50 UTC 2015 - tittiatcoke@gmail.com

- Also obsolete the synaptiks package, so that we can install 
  correctly on openSUSE:42
Comment 11 Dominique Leuenberger 2015-09-25 11:57:59 UTC
Leap 42.1 beta1 has been shipped with plasma5-desktop 5.4.0 if all is right.

Can it please be verified / confirmed, that this is all in order now?
Comment 12 Takashi Iwai 2015-09-25 14:24:22 UTC
Yes, the migration works on beta1.