Bug ID 1203095
Summary Dual monitor not detected after the latest Tumbleweed update on 20YQ009TUS with NVIDIA RTX A4000
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware x86-64
OS openSUSE Tumbleweed
Status NEW
Severity Normal
Priority P5 - None
Component KDE Workspace (Plasma)
Assignee opensuse-kde-bugs@opensuse.org
Reporter alexstol@live.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101
Firefox/104.0
Build Identifier: 

1. After installing latest Tumbleweed with distribution with KDE Plasma end of
Aug, 2022 the dual monitor was detected, displaying background, but
non-responsive, not showing any windows.
2. Updated using zyper dup, now the second monitor is not detected at all.
3. Tried installing NVIDIA drivers from
https://download.nvidia.com/opensuse/tumbleweed, pulled using Yast (see
https://ibb.co/Hh47r9P), However, after the installation Tumbleweed loads in a
black screen, therefore I am being cautious installing it again.
4. systemsettings5 

kf.coreaddons: "Could not load plugin from kcm_kscreen: The shared library was
not found." 
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML
MouseArea: Binding loop detected for property "implicitHeight" 
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML
MouseArea: Binding loop detected for property "implicitHeight" 
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML
MouseArea: Binding loop detected for property "implicitHeight" 
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML
MouseArea: Binding loop detected for property "implicitHeight" 
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML
MouseArea: Binding loop detected for property "implicitHeight" 
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML
MouseArea: Binding loop detected for property "implicitHeight" 
file:///usr/share/kpackage/kcms/kcm_nightcolor/contents/ui/main.qml:42:
TypeError: Cannot call method 'destroy' of undefined 
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML
MouseArea: Binding loop detected for property "implicitHeight" 
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML
MouseArea: Binding loop detected for property "implicitHeight" 
file:///usr/share/kpackage/kcms/kcm_nightcolor/contents/ui/main.qml:263:
TypeError: Cannot read property 'latitude' of undefined 
file:///usr/share/kpackage/kcms/kcm_nightcolor/contents/ui/main.qml:383:
TypeError: Cannot read property 'longitude' of undefined 
file:///usr/share/kpackage/kcms/kcm_nightcolor/contents/ui/main.qml:382:
TypeError: Cannot read property 'latitude' of undefined

5. sudo prime-select nvidia

nvidia catched
Preparing first configuration
bbswitch not loaded

If you want energy saving bbswitch should be loaded in intel mode.
For this package 'bbswitch' needs to be installed on your system.
Or make use of DynamicPowerManagement on Turing GPUs or later by
switching to suse-prime's 'offload' or 'nvidia' mode.
Logout to switch graphics

> exit

> /usr/sbin/prime-select get-current
No driver configured.

NVIDIA/Intel video card selection for NVIDIA Optimus laptops.

usage: prime-select          
nvidia|intel|intel2|amd|offload|unset|get-current|get-boot|offload-set|log-view|log-clean
usage: prime-select boot      nvidia|intel|intel2|amd|offload|last
usage: prime-select next-boot nvidia|intel|intel2|amd|offload|abort
usage: prime-select service   check|disable|restore

nvidia:      use the NVIDIA proprietary driver
intel:       use the Intel card with the "modesetting" driver
intel2:      use the Intel card with the "intel" Open Source driver
(xf86-video-intel)
amd:         use the Amd card with the "amd" Open Source driver
(xf86-video-amdgpu)
offload      PRIME Render Offload possible with >= 435.xx NVIDIA driver
offload-set  choose which intel driver use in PRIME Render Offload
unset:       disable effects of this script and let Xorg decide what driver to
use
get-current: display driver currently configured
log-view:    view logfile
log-clean:   clean logfile
boot:        select default card at boot or set last used
             supports kernel parameter
nvidia.prime=intel|intel2|nvidia|amd|offload
next-boot:   select card ONLY for next boot, it not touches your boot
preference. abort: restores next boot to default
get-boot:    display default card at boot
service:     disable, check or restore prime-select service.

bbswitch not loaded

If you want energy saving bbswitch should be loaded in intel mode.
For this package 'bbswitch' needs to be installed on your system.
Or make use of DynamicPowerManagement on Turing GPUs or later by
switching to suse-prime's 'offload' or 'nvidia' mode.

> sudo prime-select nvidia
[sudo] password for root: 
nvidia catched
Error: a switch operation already in execution
You can undo it using sudo killall prime-select

Reproducible: Always

Steps to Reproduce:
1. Install new Tumbleweed on 0YQ009TUS with NVIDIA RTX A4000, KDE Plasma
2. Update using zypper dup
3. Install NVIDIA drivers

Actual Results:  
4. After 2-3 dual monitor not detected
5. After 3 Tumbleweed loads with the black screen.

Expected Results:  
Dual monitor detected and configurable.


You are receiving this mail because: