Bug 428874 - Sidebar OR main KCM view Blacked Out (Nvidia)
Summary: Sidebar OR main KCM view Blacked Out (Nvidia)
Status: RESOLVED DUPLICATE of bug 424592
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.20.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-09 08:54 UTC by Jens Reuterberg
Modified: 2020-11-09 18:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Reuterberg 2020-11-09 08:54:36 UTC
SUMMARY
Opening the Systemsettings shows either the main view and a black sidebar (which can't be clicked) or if you open a specific KCM, the sidebars and the main kcm is blacked out.

STEPS TO REPRODUCE
1. Open System Settings from Krunner, Konsole or Kickoff
2. -


OBSERVED RESULT
Sidebar Blacked out if you launch systemsettings, active KCM blacked out if you launch that KCM specifically.

EXPECTED RESULT
That they are visible.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Opensuse Tumbleweed 20201106
(available in About System)
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
Nvidia Driver 450.80.02
Kernel: 5.9.1-1-default

This is after installing the proprietary Nvidia drivers and I vaguely expect that to be the issue hence including Kernel and Nvidia Driver version.
Comment 1 Jens Reuterberg 2020-11-09 08:55:05 UTC
When launched from Konsole this is the output:

Cyclic dependency detected between "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
Cyclic dependency detected between "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
QQuickWidget: Failed to make context current
QQuickWidget::resizeEvent() no OpenGL context
QQuickWidget: Failed to make context current
QQuickWidget: Attempted to render scene with no context
Cyclic dependency detected between "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///usr/share/kpackage/kcms/kcm_kscreen/contents/ui/Panel.qml:137:13: Unable to assign [undefined] to int
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ActionToolBar.qml:141:21: QML PrivateActionToolButton: Binding loop detected for property "checkable"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth"
QQuickWidget: Attempted to render scene with no context
QQuickWidget: Attempted to render scene with no context
QQuickWidget::invalidateRenderControl could not make context current
Comment 2 Nate Graham 2020-11-09 17:54:06 UTC

*** This bug has been marked as a duplicate of bug 424592 ***
Comment 3 Nate Graham 2020-11-09 17:54:35 UTC
Supposedly fixed in the latest version of the Nvidia driver.
Comment 4 Jens Reuterberg 2020-11-09 17:57:08 UTC
(In reply to Nate Graham from comment #3)
> Supposedly fixed in the latest version of the Nvidia driver.

Thank you! Sry I dug like crazy to make sure it wasn't a duplicate - my bugzilla game isn't all there
Comment 5 Nate Graham 2020-11-09 18:55:41 UTC
No problem. :)