Bug 21431

Summary:	Upgrade from Mageia5&KDE4 to Mageia6&Plasma5 - not successfull
Product:	Mageia	Reporter:	Jüri Ivask <jyri2000>
Component:	Installer	Assignee:	KDE maintainers <kde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins, fri, mageia, marja11
Version:	6
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Bug Depends on:
Bug Blocks:	21340
Attachments:	lspci and lsusb journals of upgrade and afterupgrade boots

Description Jüri Ivask 2017-08-01 10:05:42 CEST

Description of problem: Upgrade from Mageia5&KDE4 to Mageia6&Plasma5 - not successfull

Real hardware; "ancient" PC (Pentium 4HT; 1.5 GB RAM; i865G), still was OK at Mageia5&KDE4.
Performed upgrade as recommended when KDE was not running at non-graphical terminal. Upgrade went OK. Removed orphans. Reboot.
First boot was OK with Mageia6 Plymouth screen until sddm -> black screen with mouse cursor. The cursor changed its shape and was semi-operational - I was able to shutdown blindly.
Next boot -> same result. Switched to vt2, created new user, killed X with init3, logged in as new user, "startx startkde" -> got Mageia default background with mouse cursor, no panel. Was able to open desktopfolder in Dolphin and several Plasma applications until desktop crashed. Next Plasma start was not as successfull - was only able to display task manager, nothing more.
Installed lxdm, switched to it, restarted prefdm and got lxdm working. Was able to login & start icewm but plasma desktop start from lxdm resulted still only mageia background with mouse cursor.
Installed lxqt desktop and was able to use it with kwin window manager (instead default openbox) and plasma applications ran ok in lxqt session.

Comment 1 Jüri Ivask 2017-08-01 10:06:47 CEST

Created attachment 9549 [details]
lspci and lsusb

Comment 2 Jüri Ivask 2017-08-01 10:08:29 CEST

Created attachment 9550 [details]
journals of upgrade and afterupgrade boots

Marja Van Waes 2017-08-01 16:36:14 CEST

CC: (none) => marja11
Assignee: bugsquad => kde

Rémi Verschelde 2017-08-02 08:32:15 CEST

Blocks: (none) => 21340

Comment 3 Dave Hodgins 2018-06-07 04:59:49 CEST

From one upgrade test ...
selecting lib64kf5managesieve5-17.12.2-5.mga6.x86_64
no packages match libksieve[== 2:16.12.3] (it is either in skip.list or already rejected)
adding a reason to already rejected package lib64kf5ksieveui_5-16.12.3-1.mga6.x86_64: unsatisfied libksieve[== 2:16.12.3]

That appears to be triggering a cascade error which aborts the upgrade.

CC: (none) => davidwhodgins

Comment 4 Morgan Leijström 2018-06-07 08:24:18 CEST

Hmm... do that message say it thinks it need libksieve[== 2:16.12.3] for lib64kf5managesieve5-17.12.2, if so it looks like a version dependency error to me.

But why is it OK in a installed mga6 system then...?

On my mga6 with all updates including updates_testing:

$ rpm -qa lib64kf5managesieve5 libksieve
lib64kf5managesieve5-17.12.2-5.mga6
libksieve-17.12.2-5.mga6

Did you run the upgrade with updates repos enabled?

CC: (none) => fri

Comment 5 Martin Whitaker 2018-06-07 10:04:52 CEST

(In reply to Morgan Leijström from comment #4)
> Hmm... do that message say it thinks it need libksieve[== 2:16.12.3] for
> lib64kf5managesieve5-17.12.2, if so it looks like a version dependency error
> to me.

I've answered this in bug 23037 comment 40, where I think it belongs. The original bug reported here looks different to me.

CC: (none) => mageia

Comment 6 Dave Hodgins 2018-06-19 15:08:15 CEST

Working ok after perl-URPM fixes here. Between that and the grand update of the plasma/qt packages, it's likely the cause of this one is fixed too. 

Closing as fixed. Please reopen if you see it again.

Status: NEW => RESOLVED
Resolution: (none) => FIXED