|
Bugzilla – Full Text Bug Listing |
| Summary: | Black KDE screen after the latest update | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Silviu Marin-Caea <silviu_marin-caea> |
| Component: | KDE Workspace (Plasma) | Assignee: | E-Mail List <opensuse-kde-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | astieger, forgotten_uSwwH2cvav, O.Stahl, wbauer |
| Version: | Leap 42.1 | ||
| Target Milestone: | Leap 42.1 | ||
| Hardware: | 64bit | ||
| OS: | openSUSE 42.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Silviu Marin-Caea
2016-03-01 11:35:15 UTC
Hi I can confirm the problem with the latest upgrade. Login to plasma does not work. A login with gnome works, but kde applications do not start anymore. E.g.: # konsole QCoreApplication::arguments: Please instantiate the QApplication object first QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. ostahl@lx16:~> konsole: relocation error: /usr/lib64/libKF5KDELibs4Support.so.5: symbol _ZN15QGuiApplication35setFallbackSessionManagementEnabledEb, version Qt_5 not defined in file libQt5Gui.so.5 with link time reference Otmar See other bug *** This bug has been marked as a duplicate of bug 968877 *** Got same issue. After clean installed on 2 PCs and applied updates got the same black screen after log in and KDE loading screen. I can see only the mouse cursor on a black screen. Got same issue. After clean installed on 2 PCs and applied updates got the same black screen after log in and KDE loading screen. I can see only the mouse cursor on a black screen. (In reply to Radu M from comment #4) > Got same issue. After clean installed on 2 PCs and applied updates got the > same black screen after log in and KDE loading screen. I can see only the > mouse cursor on a black screen. This should be fixed already, just update your system again. And rather see Bug#968877, this one has been marked as duplicate. |