969155 – KDE Frameworks 5.19.0 Update makes the system unusable

Bug 969155 - KDE Frameworks 5.19.0 Update makes the system unusable

Summary: KDE Frameworks 5.19.0 Update makes the system unusable

Status:	RESOLVED DUPLICATE of bug 968877

Alias:	None

Product:	openSUSE Distribution
Classification:	openSUSE
Component:	KDE Workspace (Plasma) (show other bugs)
Version:	Leap 42.1
Hardware:	64bit openSUSE 42.1

Priority:	P5 - None Severity: Critical (vote)
Target Milestone:	---
Assignee:	E-Mail List
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2016-03-02 16:05 UTC by Forgotten User gmWlqx1p_8
Modified:	2016-03-02 16:34 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Forgotten User gmWlqx1p_8 2016-03-02 16:05:38 UTC

After installing the latest KDE Frameworks 5.19.0 Update, I cannot even restart or logout.
The system just freezes.
After a hard shutdown, the system stucks on the boot screen for long.
The loading bar eventually disappears and there is only a black screen and the mouse pointer (which is movable), thus making the system unusable.
If, let's say, I press ctrl+alt+backspace twice I get to logout correctly and try again (but with the same results).
I used snapper to go to a previous snapshot before the update and tried again, same thing happened.
I also did a fresh opensuse installation in a virtual machine.
Unfortunately, I got the same results after the update.

Comment 1 Andreas Stieger 2016-03-02 16:12:52 UTC

Please install the missing libqt5 update.

*** This bug has been marked as a duplicate of bug 968877 ***

Comment 2 Forgotten User gmWlqx1p_8 2016-03-02 16:34:28 UTC

(In reply to Andreas Stieger from comment #1)
> Please install the missing libqt5 update.
> 
> *** This bug has been marked as a duplicate of bug 968877 ***

Thank you very much.
Everything's good now.