If anybody want to try to hunt down the wayland black screen in plasma 6 with nvidia, look here

Help
,
1

I want to see if I can help the community with figuring out if we can get nvidia cards to play nice with plasma 6 and wayland.

I suspect this can become a mess of a thread, so I might intentionally ignore posts if they are not helpful.

I do not use KDE neon, so it might not be the best method, but I think it is a better method than just constantly typing “just use x11”.
Someone with a bit of linux knowledge is preferred over a user that “is brand new to linux”.
Maybe it works, maybe not, I have no idea.
So here goes:

I want to try to use nvidia-xconfig to get a config file setup and see if that helps.
https://manpages.ubuntu.com/manpages/trusty/man1/alt-nvidia-173-xconfig.1.html

Can someone on neon that uses Nvidia AND gets a black screen please post the output of:
tree /etc/X11

Edit
Now that I thnk about it.
If you have a setup with nvidia that does NOT get a black screen, please feel free to run above command and post output. But make sure to include what category of user you are, ie if you get a black screen or not.

ONLY KDE NEON USERS!!!

2 Likes
2

Is the black screen issue not due to plasma-desktop-data missing?

1 Like
3

IDK, all I see is tons of reports where x11 works but not wayland with nvidia cards.

This is nothing new tbh, I see it on other distros too but here I want to focus on KDE Neon only.
I am not even sure it has anything to do with plasma 6 other than it introduced wayland as default.

If nobody has problems, I guess we will see it by the lack of response here AND the lack of further reports of it not working on the forum.
Nothing would make me happier. :slight_smile:

Edit
I just realized after looking a little deeper that the package I referenced to is a SUPER OLD binary.
Seems like Ubuntu does not provide the config utilities for nvidia, and then there is not much to do.
I will drop this unless someone can tell me if a nvidia config application exist on ubuntu.
nvidia-settings is great and all, but nvidia-xconfig is just on another level.

I might have to admit defeat here, I just wanted to help the community, but it is probably a dud to even try. :frowning:

Edit 2
Nvm, found it…
Holy cr*p Ubuntu makes it hard… Searching for xconfig on their page returned nothing, but nvidia-xconfig does. :crazy_face:

https://manpages.ubuntu.com/manpages/noble/en/man1/nvidia-xconfig.1.html

THIS is what we want to try with.

So if anybody feels like going on a journey, hit me up, I have a little extra time I can invest in this.

4

After I first installed Plasma 6, I immediately switched to X11 before logging in, never even triggering Wayland once, and I still ended up with a black screen and cursor only. It seems the packaging for Plasma Desktop and Plasma Desktop Data is still broken and you need to force an install.

sudo apt autoremove
sudo pkcon refresh
sudo pkcon install libdecor-0-0
sudo pkcon install libsdl2-2.0-0
sudo pkcon install plasma-desktop
sudo pkcon install plasma-desktop-data

5

Well, good for you, but that is not what THIS thread is about.

My hope is zero more posts in this thread, ie that NOBODY has problems unrelated to f.ex what you just referenced. :slight_smile:

6

I may be wrong, but I do not think the issue with Wayland is due to Nvidia’s X config, which is for X, not Wayland.

As you discovered, there is a second issue, in that Ubuntu does not use a standard xconf file. It is automated and dynamic, not static. So typically we are going to add config options by using or adding conf files in /usr/share/X11/xorg.conf.d/. For example, to add overclocking ability I added a file “20-nvidia.conf” with the appropriate options.

My guess at the moment is that the problems are due to a long standing issue with instability within Wayland’s backend; it looses client connections. This was reportedly solved six months ago, but it appears it really has not been.

7

You are wrong. Heard of xwayland?
Why don’t you reboot, log into wayland, run cat /var/log/Xorg.0.log and tell me again that it is not being used.

I lost interest in trying to help now, this was not why I offered my help.

8

If you are upset that everybody did not jump onto your bandwagon, don’t blame me. I am just trying to figure out what it is you think you are trying to solve. If you were talking about the Nvidia EGL stack, I might understand where you are coming from as this is where Wayland typically fell down in the past (due to Nvidias incomplete implementation of it in their driver), but that was supposedly solved a year ago. What we do know is that Wayland had, in the recent past, a problem maintaining client connections. This was still a major bug a few months ago. Again, this was supposedly solved… but… perhaps it was not? Is that what you are trying to determine?

9 
Mar 06 15:35:33 hostname systemd-networkd[1482]: wlp70s0: Lost carrier
Mar 06 15:35:33 hostname wpa_supplicant[2335]: wlp70s0: CTRL-EVENT-DISCONNECTED bssid=a6:11:fc:b0:63:b3 reason=3 locally_generated=1
Mar 06 15:35:33 hostname wpa_supplicant[2335]: wlp70s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
Mar 06 15:35:33 hostname rtkit-daemon[2535]: The canary thread is apparently starving. Taking action.
Mar 06 15:35:33 hostname systemd-resolved[2325]: Clock change detected. Flushing caches.
Mar 06 15:35:33 hostname rtkit-daemon[2535]: Demoting known real-time threads.
Mar 06 15:35:33 hostname systemd-networkd[1482]: wlp70s0: DHCPv6 lease lost
Mar 06 15:35:33 hostname rtkit-daemon[2535]: Successfully demoted thread 3561 of process 3016.
Mar 06 15:35:33 hostname systemd-sleep[8817]: System returned from sleep operation 'suspend'.
Mar 06 15:35:33 hostname rtkit-daemon[2535]: Successfully demoted thread 3048 of process 3030.
Mar 06 15:35:33 hostname systemd-timesyncd[2326]: No network connectivity, watching for changes.
Mar 06 15:35:33 hostname rtkit-daemon[2535]: Successfully demoted thread 3030 of process 3030.
Mar 06 15:35:33 hostname rtkit-daemon[2535]: Successfully demoted thread 2557 of process 2551.
Mar 06 15:35:33 hostname rtkit-daemon[2535]: Successfully demoted thread 2551 of process 2551.
Mar 06 15:35:33 hostname rtkit-daemon[2535]: Successfully demoted thread 2553 of process 2550.
Mar 06 15:35:33 hostname rtkit-daemon[2535]: Successfully demoted thread 2550 of process 2550.
Mar 06 15:35:33 hostname rtkit-daemon[2535]: Demoted 7 threads.
Mar 06 15:35:35 hostname systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 06 15:35:35 hostname systemd[1]: Finished System Suspend.
Mar 06 15:35:35 hostname systemd[1]: systemd-suspend.service: Consumed 2.697s CPU time.
Mar 06 15:35:35 hostname systemd[1]: Stopped target Sleep.
Mar 06 15:35:35 hostname systemd[1]: Reached target Suspend.
Mar 06 15:35:35 hostname systemd-logind[2334]: Operation 'suspend' finished.
Mar 06 15:35:35 hostname systemd-networkd[1482]: wlp70s0: Reconfiguring with /etc/systemd/network/25-wireless.network.
Mar 06 15:35:35 hostname systemd-networkd[1482]: wlp70s0: DHCPv6 lease lost
Mar 06 15:35:35 hostname kdeconnectd[2978]: 2024-03-06T15:35:35 default: Error sending UDP packet: QAbstractSocket::NetworkError
Mar 06 15:35:35 hostname systemd-networkd[1482]: enp68s0: Reconfiguring with /etc/systemd/network/20-wired.network.
Mar 06 15:35:35 hostname systemd-networkd[1482]: lo: Unmanaging interface.
Mar 06 15:35:35 hostname systemd-networkd[1482]: enp69s0: Reconfiguring with /etc/systemd/network/21-wired.network.
Mar 06 15:35:35 hostname systemd[1]: Starting NVIDIA system resume actions...
Mar 06 15:35:35 hostname systemd[1]: Stopped target Suspend.
Mar 06 15:35:35 hostname suspend[9181]: nvidia-resume.service
Mar 06 15:35:35 hostname logger[9181]: <13>Mar  6 15:35:35 suspend: nvidia-resume.service
Mar 06 15:35:35 hostname systemd[1]: nvidia-resume.service: Deactivated successfully.
Mar 06 15:35:36 hostname systemd[1]: Finished NVIDIA system resume actions.
Mar 06 15:35:36 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:36 hostname wpa_supplicant[2335]: wlp70s0: SME: Trying to authenticate with a8:11:fc:b0:63:b0 (SSID='Tek9ine' freq=2412 MHz)
Mar 06 15:35:36 hostname kernel: wlp70s0: 80 MHz not supported, disabling VHT
Mar 06 15:35:36 hostname wpa_supplicant[2335]: wlp70s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Mar 06 15:35:36 hostname kernel: wlp70s0: authenticate with a8:11:fc:b0:63:b0 (local address=94:e6:f7:2c:ce:41)
Mar 06 15:35:36 hostname kernel: wlp70s0: send auth to a8:11:fc:b0:63:b0 (try 1/3)
Mar 06 15:35:36 hostname wpa_supplicant[2335]: wlp70s0: Trying to associate with a8:11:fc:b0:63:b0 (SSID='Tek9ine' freq=2412 MHz)
Mar 06 15:35:36 hostname kernel: wlp70s0: authenticated
Mar 06 15:35:36 hostname kernel: wlp70s0: associate with a8:11:fc:b0:63:b0 (try 1/3)
Mar 06 15:35:36 hostname kernel: wlp70s0: RX AssocResp from a8:11:fc:b0:63:b0 (capab=0x411 status=0 aid=25)
Mar 06 15:35:36 hostname systemd-networkd[1482]: wlp70s0: Connected WiFi access point: Tek9ine (a8:11:fc:b0:63:b0)
Mar 06 15:35:36 hostname wpa_supplicant[2335]: wlp70s0: Associated with a8:11:fc:b0:63:b0
Mar 06 15:35:36 hostname wpa_supplicant[2335]: wlp70s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mar 06 15:35:36 hostname kernel: wlp70s0: associated
Mar 06 15:35:36 hostname kernel: wlp70s0: Limiting TX power to 30 (30 - 0) dBm as advertised by a8:11:fc:b0:63:b0
Mar 06 15:35:36 hostname wpa_supplicant[2335]: wlp70s0: WPA: Key negotiation completed with a8:11:fc:b0:63:b0 [PTK=CCMP GTK=CCMP]
Mar 06 15:35:36 hostname wpa_supplicant[2335]: wlp70s0: CTRL-EVENT-CONNECTED - Connection to a8:11:fc:b0:63:b0 completed [id=0 id_str=]
Mar 06 15:35:36 hostname systemd-networkd[1482]: wlp70s0: Gained carrier
Mar 06 15:35:36 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:36 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:36 hostname kactivitymanagerd[2777]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname polkit-kde-authentication-agent-1[2780]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname kded6[2618]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname DiscoverNotifier[2995]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname kdeconnectd[2978]: 2024-03-06T15:35:36 qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname kmix[3005]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname kclockd[2977]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_akonotes_resource[3250]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_maildir_resource[3257]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname kalendarac[3000]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_migration_agent[3261]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_ical_resource[3255]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_contacts_resource[3253]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_newmailnotifier_agent[3262]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_birthdays_resource[3252]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_mailmerge_agent[3260]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_archivemail_agent[3251]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_notes_agent[3263]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_indexing_agent[3256]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_maildispatcher_agent[3258]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname kded5[3107]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname konsole[3875]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_followupreminder_agent[3254]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname konsole[3787]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname org_kde_powerdevil[2781]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_unifiedmailbox_agent[3265]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_mailfilter_agent[3259]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_sendlater_agent[3264]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname systemsettings[7083]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname akonadi_control[3126]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname kscreenlocker_greet[8581]: qt.qpa.wayland.textinput: virtual void QtWaylandClient::QWaylandTextInputv3::zwp_text_input_v3_leave(wl_surface*) Got leave event for surface 0x0 focused surface 0x5f6da0e1a950
Mar 06 15:35:36 hostname kscreenlocker_greet[8581]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname kwin_wayland[2484]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
Mar 06 15:35:36 hostname plasmashell[2636]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname plasmashell[2636]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Mar 06 15:35:36 hostname plasmashell[2636]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Mar 06 15:35:36 hostname plasmashell[2636]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Mar 06 15:35:36 hostname systemd-timesyncd[2326]: Network configuration changed, trying to establish connection.
Mar 06 15:35:36 hostname xdg-desktop-portal-kde[2782]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Mar 06 15:35:36 hostname kwin_wayland[2484]: kwin_core: Could not find window with uuid "{087191af-632f-403f-a136-ea8df5f6996d}"
Mar 06 15:35:36 hostname kwin_wayland[2484]: kwin_core: Could not find window with uuid "{087191af-632f-403f-a136-ea8df5f6996d}"
Mar 06 15:35:36 hostname kwin_wayland[2484]: kwin_core: Could not find window with uuid "{087191af-632f-403f-a136-ea8df5f6996d}"
Mar 06 15:35:37 hostname systemd-resolved[2325]: Clock change detected. Flushing caches.
Mar 06 15:35:37 hostname systemd-timesyncd[2326]: Contacted time server 152.70.159.102:123 (1.arch.pool.ntp.org).
Mar 06 15:35:39 hostname wireplumber[2551]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner
Mar 06 15:35:39 hostname kmix[3005]: adding 4 mixers
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Playback_Devices:1" "Playback Devices"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 0 devices
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Capture_Devices:1" "Capture Devices"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 0 devices
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Playback_Streams:1" "Playback Streams"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 1 devices
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Capture_Streams:1" "Capture Streams"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 0 devices
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-usb"
Mar 06 15:35:39 hostname kmix[3005]: adding 4 mixers
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Playback_Devices:1" "Playback Devices"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 1 devices
Mar 06 15:35:39 hostname kmix[3005]: adding "alsa_output.usb-Generic_USB_Audio-00.iec958-stereo" "USB Audio Digital Stereo (IEC958)"
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Capture_Devices:1" "Capture Devices"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 0 devices
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Playback_Streams:1" "Playback Streams"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 1 devices
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Capture_Streams:1" "Capture Streams"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 0 devices
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-usb"
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-usb"
Mar 06 15:35:39 hostname kmix[3005]: adding 4 mixers
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Playback_Devices:1" "Playback Devices"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 1 devices
Mar 06 15:35:39 hostname kmix[3005]: adding "alsa_output.usb-Generic_USB_Audio-00.iec958-stereo" "USB Audio Digital Stereo (IEC958)"
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Capture_Devices:1" "Capture Devices"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 1 devices
Mar 06 15:35:39 hostname kmix[3005]: adding "alsa_input.usb-Generic_USB_Audio-00.iec958-stereo" "USB Audio Digital Stereo (IEC958)"
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Playback_Streams:1" "Playback Streams"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 1 devices
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Capture_Streams:1" "Capture Streams"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 0 devices
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-usb"
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-usb"
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-usb"
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-pci"
Mar 06 15:35:39 hostname kmix[3005]: adding 4 mixers
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Playback_Devices:1" "Playback Devices"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 2 devices
Mar 06 15:35:39 hostname kmix[3005]: adding "alsa_output.usb-Generic_USB_Audio-00.iec958-stereo" "USB Audio Digital Stereo (IEC958)"
Mar 06 15:35:39 hostname kmix[3005]: adding "alsa_output.pci-0000_01_00.1.hdmi-stereo" "TU102 High Definition Audio Controller Digital Stereo (HDMI)"
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Capture_Devices:1" "Capture Devices"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 1 devices
Mar 06 15:35:39 hostname kmix[3005]: adding "alsa_input.usb-Generic_USB_Audio-00.iec958-stereo" "USB Audio Digital Stereo (IEC958)"
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Playback_Streams:1" "Playback Streams"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 1 devices
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Capture_Streams:1" "Capture Streams"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 0 devices
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-usb"
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-pci"
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-usb"
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-usb"
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-pci"
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-usb"
Mar 06 15:35:39 hostname kmix[3005]: adding 4 mixers
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Playback_Devices:1" "Playback Devices"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 3 devices
Mar 06 15:35:39 hostname kmix[3005]: adding "alsa_output.usb-Generic_USB_Audio-00.iec958-stereo" "USB Audio Digital Stereo (IEC958)"
Mar 06 15:35:39 hostname kmix[3005]: adding "alsa_output.pci-0000_01_00.1.hdmi-stereo" "TU102 High Definition Audio Controller Digital Stereo (HDMI)"
Mar 06 15:35:39 hostname kmix[3005]: adding "alsa_output.usb-Generic_USB_Audio-00.2.iec958-stereo" "USB Audio Digital Stereo (IEC958)"
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Capture_Devices:1" "Capture Devices"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 1 devices
Mar 06 15:35:39 hostname kmix[3005]: adding "alsa_input.usb-Generic_USB_Audio-00.iec958-stereo" "USB Audio Digital Stereo (IEC958)"
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Playback_Streams:1" "Playback Streams"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 1 devices
Mar 06 15:35:39 hostname kmix[3005]: mixer "PulseAudio::Capture_Streams:1" "Capture Streams"
Mar 06 15:35:39 hostname kmix[3005]: PulseAudio adding 0 devices
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-usb"
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-pci"
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-usb"
Mar 06 15:35:39 hostname kmix[3005]: org.kde.kmix: No such icon "audio-card-analog-usb"
Mar 06 15:35:42 hostname sshd[9272]: Received disconnect from 109.167.200.10 port 56292:11: Bye Bye [preauth]
Mar 06 15:35:42 hostname sshd[9272]: Disconnected from authenticating user root 109.167.200.10 port 56292 [preauth]
Mar 06 15:35:46 hostname systemd-resolved[2325]: DNSSEC validation failed for question l.google.com IN SOA: failed-auxiliary
Mar 06 15:35:46 hostname systemd-resolved[2325]: DNSSEC validation failed for question youtube-ui.l.google.com IN DS: failed-auxiliary
Mar 06 15:35:46 hostname systemd-resolved[2325]: DNSSEC validation failed for question youtube-ui.l.google.com IN SOA: failed-auxiliary
Mar 06 15:35:46 hostname systemd-resolved[2325]: DNSSEC validation failed for question youtube-ui.l.google.com IN A: failed-auxiliary
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
Mar 06 15:35:47 hostname kwin_wayland[2484]: QObject::startTimer: Timers cannot have negative intervals
10

You can see above that I get a kwin_core error saying window cannot be found with uuid.

11

The only thing I am going to answer in this thread is if someone provides this, and has problems with nvidia and wayland.

12

I’m using the Arch-based EndeavourOS, but I’m having this issue using Plasma 6 + Wayland. After logging into Wayland the displays die and not even switching TTYs brings them back. I’m then forced to reboot the system.

$ tree /etc/X11

/etc/X11
|-- xinit
|   |-- xinitrc
|   |-- xinitrc.d
|   |   |-- 40-libcanberra-gtk-module.sh
|   |   `-- 50-systemd-user.sh
|   `-- xserverrc
|-- xorg.conf
|-- xorg.conf.d
|   `-- 00-keyboard.conf
`-- xorg.conf.nvidia-xconfig-original

4 directories, 7 files

FWIW the Wayland session was working on 5.27.10, before the upgrade.

13

Well, this was intended for KDE Neon, but to me it looks like you have no config at all, so that might be your problem.
But have ran nvidia-xconfig at some point it seems since xorg.conf.nvidia-xconfig-original looks like a backup it makes when creating a conf.

After looking at the install script on the link below, your config should be /etc/X11/xorg.conf.d/20-nvidia.conf

Never used that os, but a quick search shows there is a specific nvidia installer for Endeavouros: Nvidia – Discovery

Otherwise there is always arch: NVIDIA - ArchWiki

14

it looks like you have no config at all

right, it’s been several years since the last time I needed to mess around with this config file (which includes a few Ubuntu flavors I used before Endeavour).

The Arch Wiki says

The proprietary NVIDIA graphics card driver does not need any Xorg server configuration file.

and this most definitely works, as I can log into the X11 session without a problem and NVIDIA hardware is detected and used under X11 (I don’t even have another graphics unit, integrated to the CPU or not).

Anyways - I thought it was worth asking even though I’m not using Neon, as this seems like a similar - perhaps the same - problem some Neon users are having. Thanks.

15

I have mentioned it again in the past: in kde neon you don’t need to have an xorg.conf and everything works out-of-the-box, as expected.

I’m not sure why you are insisting on this thing, especially since you don’t even use KDE Neon. Try it at least and see for yourself :slight_smile:

16

I insist because I see absolutely no proof of what you are saying is true.
On the contrary, reading Ubuntu documentation, that KDE neon is based on, you absolutely have an nvidia config, the question is WHERE KDE Neon puts this.
Symlink to userspace or directly in xorg.conf.d
If you have nothing of value to provide, please refrain from commenting.

Did you use x11 or wayland before?
X11 is very forgiving, wayland, not so much.

Check your /var/log/Xorg.0.log if you do not believe me.
Besides, read what it says on Endeavouros webpage, you should absolutely have a config, I even showed you where according to your distros documentation.

17

What evidence do you need in order to convince yourself?

What is the name of that file?

18

Both. As I mentioned, both were working before the upgrade. Some visual glitches on Wayland because NVIDIA, I guess, but they were both usable.

you should absolutely have a config

And I do, generated by nvidia-xconfig, still no ball. In fact the only reason I have a config at all is because I was trying to fix this.

My question though is how an Xorg config is supposed to make Wayland work.

19

Why are you not using your distributions installer?

It uses xwayland.
If you do what I suggested, and check /var/log/Xorg.0.log it would all become much clearer. xD

You can also use f.ex use inxi -G and look at Display.
Example on mine:

Graphics:
  Device-1: NVIDIA GA102 [GeForce RTX 3090] driver: nvidia v: 550.54.14
  Device-2: AMD Raphael driver: amdgpu v: kernel
  Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4
    compositor: kwin_wayland driver: X: loaded: amdgpu,nvidia
    unloaded: modesetting,nouveau dri: radeonsi gpu: nvidia,amdgpu
    resolution: 1920x1080
  API: EGL v: 1.5 drivers: nvidia,radeonsi,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: amd mesa v: 24.0.2-manjaro1.1
    renderer: AMD Radeon Graphics (radeonsi raphael_mendocino LLVM 16.0.6 DRM
    3.57 6.7.7-1-MANJARO)
  API: Vulkan v: 1.3.279 drivers: nvidia surfaces: xcb,xlib,wayland
20

@bedna what is the supposed nvidia config file named? What should I look for? How can I convince you? :slight_smile: