Bug 481986 - Plasma6 with nvidia optimus fails to launch on wayland
Summary: Plasma6 with nvidia optimus fails to launch on wayland
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.93.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-02-29 02:33 UTC by randamunanamae
Modified: 2024-03-26 15:23 UTC (History)
4 users (show)

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


Attachments
journalctl excerpt (7.33 KB, text/plain)
2024-02-29 02:35 UTC, randamunanamae
Details
new user, first time login in wayland (82.59 KB, image/jpeg)
2024-03-01 04:41 UTC, John Salatas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description randamunanamae 2024-02-29 02:33:52 UTC
SUMMARY
***
When logging into wayland session, plasma will fail to start. I get a black screen and the applications I had open. Trying to open krunner from a konsole also fails with "wayland protocol error".
See attachment for an excerpt from journalctl with logs from kwin and plasmashell
***


STEPS TO REPRODUCE
1. Log into wayland session

OBSERVED RESULT
There's no plasmashell, and can't launch anything related to kde except for Dolphin, which shows up without any icons.

EXPECTED RESULT
System functional, as it is under Xorg


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.0.0
(available in About System)
KDE Plasma Version: 6.0.0 
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Distro: KDE Neon
Laptop ThinkPad P1 Gen 4i.
GPU: NVIDIA GeForce RTX 3080 Laptop GPU
Optimus, profile "on demand", but fails equally under always nvidia
Nvidia driver: 550.54.14, but same result under 545 and 540
Kernel 6.7.6-x64v4-xanmod1

Extra note: I've had this exact behavior with kde5 as well, it basically never worked.
Comment 1 randamunanamae 2024-02-29 02:35:29 UTC
Created attachment 166179 [details]
journalctl excerpt
Comment 2 randamunanamae 2024-02-29 12:59:31 UTC
Some additional information, when under the broken wayland session, this is what happens if I try to launch krunner from a konsole:

warning: queue 0x5857bcff4c70 destroyed while proxies still attached:
  wl_registry@37 still attached
kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.plasma.core: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.plasma.core: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
QObject::startTimer: Timers cannot be started from another thread
[destroyed object]: error 7: importing the supplied dmabufs failed
The Wayland connection experienced a fatal error: Protocol error
Comment 3 John Salatas 2024-03-01 04:40:02 UTC
I'm on a desktop with nvidia. The desktop is unusable in wayland (see attachement on how it looks like and it also flicks when moving any windows) but I believe I should add the following info: If I have a previously x11 session which gets restored, applications like konsole, kate and even firefox seem to have no issues. I believe the issue is related to applications which I think (please forgive my ignorance here, it's been some time since I messed with the plasma source code) are based on kirigami (???) or qml (???) I mean stuff like systemsettings, discover, elisa and spectacle (these are the apps I tried). When I launch these through konsole, I get the same error as reported by the other user

warning: queue 0x5857bcff4c70 destroyed while proxies still attached:
  wl_registry@37 still attached

The number of the queue changes each time but the " wl_registry@37 still attached" is always the same. 

Hope that it helps. 

PS: Thanks for your efforts! :)
Comment 4 John Salatas 2024-03-01 04:41:05 UTC
Created attachment 166232 [details]
new user, first time login in wayland
Comment 5 Vlad Zahorodnii 2024-03-01 09:01:51 UTC
> [destroyed object]: error 7: importing the supplied dmabufs failed

this one is relevant. it means that krunner can't create a graphics buffer so the compositor could display it. Not sure why nvidia would refuse to import a graphics buffer. If your laptop has an intel gpu, try switching to it instead.
Comment 6 randamunanamae 2024-03-01 23:48:05 UTC
(In reply to Vlad Zahorodnii from comment #5)
> > [destroyed object]: error 7: importing the supplied dmabufs failed
> 
> this one is relevant. it means that krunner can't create a graphics buffer
> so the compositor could display it. Not sure why nvidia would refuse to
> import a graphics buffer. If your laptop has an intel gpu, try switching to
> it instead.

Under intel:

```
mar 01 20:24:12 zephyr kwin_wayland[2267]: OpenGL vendor string:                   Intel
mar 01 20:24:12 zephyr kwin_wayland[2267]: OpenGL renderer string:                 Mesa Intel(R) UHD Graphics (TGL GT1)
mar 01 20:24:12 zephyr kwin_wayland[2267]: OpenGL version string:                  4.6 (Core Profile) Mesa 24.1~git2403010600.6e33b3~oibaf~j (git-6e33b39 2024-03-01 jammy-oibaf-ppa)
mar 01 20:24:12 zephyr kwin_wayland[2267]: OpenGL shading language version string: 4.60
mar 01 20:24:12 zephyr kwin_wayland[2267]: Driver:                                 Intel
mar 01 20:24:12 zephyr kwin_wayland[2267]: GPU class:                              Tiger Lake
mar 01 20:24:12 zephyr kwin_wayland[2267]: OpenGL version:                         4.6
mar 01 20:24:12 zephyr kwin_wayland[2267]: GLSL version:                           4.60
mar 01 20:24:12 zephyr kwin_wayland[2267]: Mesa version:                           24.1
mar 01 20:24:12 zephyr kwin_wayland[2267]: Requires strict binding:                no
mar 01 20:24:12 zephyr kwin_wayland[2267]: Virtual Machine:                        no
mar 01 20:24:12 zephyr kwin_wayland[2267]: Timer query support:                    yes
...
mar 01 20:24:13 zephyr ksplashqml[2272]: warning: queue 0x624a4bac8cb0 destroyed while proxies still attached:
mar 01 20:24:13 zephyr ksplashqml[2272]:   wl_registry@37 still attached
mar 01 20:24:13 zephyr ksplashqml[2272]: kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 01 20:24:13 zephyr ksplashqml[2272]: kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 01 20:24:13 zephyr ksplashqml[2272]: kf.plasma.core: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 01 20:24:13 zephyr ksplashqml[2272]: kf.plasma.core: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 01 20:24:13 zephyr ksplashqml[2272]: QQmlComponent: Component is not ready
mar 01 20:24:13 zephyr ksplashqml[2272]: kf.plasma.quick: "file:///home/userhome/.local/share/plasma/look-and-feel/degears/contents/splash/Splash.qml" 
                                          "Error loading QML file.\n23: module \"QtGraphicalEffects\" is not installed\n"
mar 01 20:24:13 zephyr ksplashqml[2272]: org.kde.plasma.ksplashqml: Failed loading QUrl("file:///home/userhome/.local/share/plasma/look-and-feel/degears/contents/splash/Splash.qml")
mar 01 20:24:13 zephyr ksplashqml[2272]: org.kde.plasma.ksplashqml: QList(file:///home/userhome/.local/share/plasma/look-and-feel/degears/contents/splash/Splash.qml:23:1: module "QtGraphicalEffects" is not installed
                                             import QtGraphicalEffects 1.0
                                             ^)
mar 01 20:24:13 zephyr kwin_wayland[2267]: qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
mar 01 20:24:13 zephyr systemd[2210]: Starting Accessibility services bus...
mar 01 20:24:13 zephyr systemd[2210]: plasma-ksplash.service: Main process exited, code=exited, status=1/FAILURE
...
mar 01 20:24:14 zephyr plasmashell[2422]: warning: queue 0x5e829d339db0 destroyed while proxies still attached:
mar 01 20:24:14 zephyr plasmashell[2422]:   wl_registry@37 still attached
mar 01 20:24:14 zephyr dbus-daemon[2223]: [session uid=1000 pid=2223] Activating via systemd: service name='org.kde.ActivityManager' unit='plasma-kactivitymanagerd.service' requested by ':1.28' (uid=1000 pid=2422 comm="/usr/bin/plasmashell --no-res>
mar 01 20:24:14 zephyr plasmashell[2422]: kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 01 20:24:14 zephyr plasmashell[2422]: kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 01 20:24:14 zephyr plasmashell[2422]: kf.plasma.core: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 01 20:24:14 zephyr plasmashell[2422]: kf.plasma.core: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 01 20:24:14 zephyr plasmashell[2422]: starting invalid corona "org.kde.plasma.desktop"
mar 01 20:24:14 zephyr systemd[2210]: Starting KActivityManager Activity manager Service...
mar 01 20:24:14 zephyr systemd[2210]: plasma-plasmashell.service: Main process exited, code=exited, status=1/FAILURE

```
Comment 7 randamunanamae 2024-03-02 00:04:24 UTC
Under intel, launching krunner, and then using it to launch System Info reported this

```
/home/randa> krunner
warning: queue 0x5e3640527060 destroyed while proxies still attached:
  wl_registry@35 still attached
kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.plasma.core: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.plasma.core: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
QObject::startTimer: Timers cannot be started from another thread
warning: queue 0x61989b0a7840 destroyed while proxies still attached:
  wl_registry@35 still attached
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
```

Both had no icons, and system info had 0 information, no entries at all.
Comment 8 John Salatas 2024-03-02 22:48:10 UTC
Apparently my issue was the dual nvidia GPU. I have a workstation with an RTX5000 and an RTX2000. If I remove either of these wayland works perfectly. 

I'll create another bug report.
Comment 9 Nicolas 2024-03-05 15:15:01 UTC
I'm having the same issue, tried nvidia drivers 535, 545, 550 with NVIDIA GeForce GTX 1650 and enabled/disabled "on demand" in nvidia-settings.

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-21-generic (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Manufacturer: LENOVO
Product Name: 20QVCTO1WW
System Version: ThinkPad X1 Extreme 2nd
Comment 10 Zamundaaa 2024-03-06 16:40:50 UTC
(In reply to randamunanamae from comment #7)
> Under intel, launching krunner, and then using it to launch System Info
> reported this
> 
> ```
> /home/randa> krunner
> warning: queue 0x5e3640527060 destroyed while proxies still attached:
>   wl_registry@35 still attached
> kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider
> contacting the author and asking them update it to use the newer JSON format.
> kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider
> contacting the author and asking them update it to use the newer JSON format.
> kf.plasma.core: The theme "Adapta" uses the legacy metadata.desktop.
> Consider contacting the author and asking them update it to use the newer
> JSON format.
> kf.plasma.core: The theme "Adapta" uses the legacy metadata.desktop.
> Consider contacting the author and asking them update it to use the newer
> JSON format.
> kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider
> contacting the author and asking them update it to use the newer JSON format.
> QObject::startTimer: Timers cannot be started from another thread
> warning: queue 0x61989b0a7840 destroyed while proxies still attached:
>   wl_registry@35 still attached
> qt.qml.typeresolution.cycle: Cyclic dependency detected between
> "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and
> "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
> ```
> 
> Both had no icons, and system info had 0 information, no entries at all.

That sounds like your install is broken; are you sure you have the latest updates from Neon? Also, does it work on a different distro?
Comment 11 randamunanamae 2024-03-06 16:58:41 UTC
(In reply to Zamundaaa from comment #10)
> (In reply to randamunanamae from comment #7)
> > Under intel, launching krunner, and then using it to launch System Info
> > reported this
> > 
> > ```
> > /home/randa> krunner
> > warning: queue 0x5e3640527060 destroyed while proxies still attached:
> >   wl_registry@35 still attached
> > kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider
> > contacting the author and asking them update it to use the newer JSON format.
> > kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider
> > contacting the author and asking them update it to use the newer JSON format.
> > kf.plasma.core: The theme "Adapta" uses the legacy metadata.desktop.
> > Consider contacting the author and asking them update it to use the newer
> > JSON format.
> > kf.plasma.core: The theme "Adapta" uses the legacy metadata.desktop.
> > Consider contacting the author and asking them update it to use the newer
> > JSON format.
> > kf.svg: The theme "Adapta" uses the legacy metadata.desktop. Consider
> > contacting the author and asking them update it to use the newer JSON format.
> > QObject::startTimer: Timers cannot be started from another thread
> > warning: queue 0x61989b0a7840 destroyed while proxies still attached:
> >   wl_registry@35 still attached
> > qt.qml.typeresolution.cycle: Cyclic dependency detected between
> > "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and
> > "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
> > ```
> > 
> > Both had no icons, and system info had 0 information, no entries at all.
> 
> That sounds like your install is broken; are you sure you have the latest
> updates from Neon? Also, does it work on a different distro?

As sure as a fresh install from KDE Neon provides, and that my current install works fine under Xorg.
Comment 12 randamunanamae 2024-03-06 22:54:04 UTC
> Also, does it work on a different distro?

Testing on a different distro is something that I can't do right now, sadly.
Comment 13 Zamundaaa 2024-03-08 15:28:33 UTC
(In reply to Nicolas from comment #9)
> I'm having the same issue, tried nvidia drivers 535, 545, 550 with NVIDIA
> GeForce GTX 1650 and enabled/disabled "on demand" in nvidia-settings.

Please attach your plasmashell log
> journalctl --user-unit plasma-plasmashell --boot 0
after triggering the issue
Comment 14 Nicolas 2024-03-08 18:03:04 UTC
Mär 08 19:00:34 x1-extreme systemd[3321]: Starting KDE Plasma Workspace...
Mär 08 19:00:34 x1-extreme plasmashell[3525]: warning: queue 0x62af84bf2950 destroyed while proxies still attached:
Mär 08 19:00:34 x1-extreme plasmashell[3525]:   wl_registry@36 still attached
Mär 08 19:00:34 x1-extreme systemd[3321]: Started KDE Plasma Workspace.
Mär 08 19:00:34 x1-extreme plasmashell[3525]: KPackageStructure of KPluginMetaData(pluginId:"org.kde.merkuro.contact", fileName: "/usr/share/plasma/plasmoids/org.kde.merkuro.contact/metadata.json") does not match requested format "Plasma/Applet"
Mär 08 19:00:34 x1-extreme plasmashell[3525]: kde.plasmashell: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Mär 08 19:00:34 x1-extreme plasmashell[3525]: kde.plasmashell: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
Mär 08 19:00:34 x1-extreme plasmashell[3525]: kde.plasmashell: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Mär 08 19:00:34 x1-extreme plasmashell[3525]: kde.plasmashell: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
Mär 08 19:00:34 x1-extreme plasmashell[3525]: kf.plasma.quick: Applet preload policy set to 1
Mär 08 19:00:34 x1-extreme plasmashell[3525]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:196:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
Mär 08 19:00:34 x1-extreme plasmashell[3525]: qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
Mär 08 19:00:35 x1-extreme plasmashell[3525]: [destroyed object]: error 7: importing the supplied dmabufs failed
Mär 08 19:00:36 x1-extreme plasmashell[3525]: org.kde.plasma.kicker: Entry is not valid "kontact.desktop" 0x62af86cef0f0
Mär 08 19:00:36 x1-extreme plasmashell[3525]: org.kde.plasma.kicker: Entry is not valid "ktp-contactlist.desktop" 0x62af86ced8d0
Mär 08 19:00:36 x1-extreme plasmashell[3525]: org.kde.plasma.kicker: Entry is not valid "kontact.desktop" 0x62af86cefc50
Mär 08 19:00:36 x1-extreme plasmashell[3525]: org.kde.plasma.kicker: Entry is not valid "ktp-contactlist.desktop" 0x62af86cef5e0
Mär 08 19:00:36 x1-extreme plasmashell[3525]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:162:21: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
Mär 08 19:00:36 x1-extreme plasmashell[3525]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:162:21: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
Mär 08 19:00:36 x1-extreme plasmashell[3525]: qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/con>
Mär 08 19:00:36 x1-extreme plasmashell[3525]: qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/con>
Mär 08 19:00:36 x1-extreme plasmashell[3525]: qml: SystemTray ItemLoader: Invalid state, cannot determine source!
Mär 08 19:00:36 x1-extreme plasmashell[3525]: qt.dbus.integration: Could not connect "org.cups.cupsd.Notifier" to PrinterFinishingsChanged(QString, QString, QString, uint, QString, bool) :
Mär 08 19:00:38 x1-extreme plasmashell[3525]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
Mär 08 19:00:38 x1-extreme plasmashell[3525]: The Wayland connection broke. Did the Wayland compositor die?
Mär 08 19:00:39 x1-extreme systemd[3321]: plasma-plasmashell.service: Main process exited, code=exited, status=255/EXCEPTION
Mär 08 19:00:39 x1-extreme systemd[3321]: plasma-plasmashell.service: Failed with result 'exit-code'.
Mär 08 19:00:39 x1-extreme systemd[3321]: plasma-plasmashell.service: Consumed 3.188s CPU time.
Mär 08 19:00:39 x1-extreme systemd[3321]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 1.
Mär 08 19:00:39 x1-extreme systemd[3321]: Stopped KDE Plasma Workspace.
Mär 08 19:00:39 x1-extreme systemd[3321]: plasma-plasmashell.service: Consumed 3.188s CPU time.
Mär 08 19:00:39 x1-extreme systemd[3321]: Starting KDE Plasma Workspace...
Mär 08 19:00:39 x1-extreme plasmashell[4637]: warning: queue 0x5a3de24ea760 destroyed while proxies still attached:
Mär 08 19:00:39 x1-extreme plasmashell[4637]:   wl_registry@36 still attached
Mär 08 19:00:40 x1-extreme systemd[3321]: Started KDE Plasma Workspace.
Mär 08 19:00:40 x1-extreme plasmashell[4637]: KPackageStructure of KPluginMetaData(pluginId:"org.kde.merkuro.contact", fileName: "/usr/share/plasma/plasmoids/org.kde.merkuro.contact/metadata.json") does not match requested format "Plasma/Applet"
Mär 08 19:00:40 x1-extreme plasmashell[4637]: kf.plasma.quick: Applet preload policy set to 1
Mär 08 19:00:40 x1-extreme plasmashell[4637]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:196:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
Mär 08 19:00:41 x1-extreme plasmashell[4637]: qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
Mär 08 19:00:41 x1-extreme plasmashell[4637]: [destroyed object]: error 7: importing the supplied dmabufs failed
Mär 08 19:00:41 x1-extreme plasmashell[4637]: The Wayland connection experienced a fatal error: Protokollfehler
Mär 08 19:00:41 x1-extreme systemd[3321]: plasma-plasmashell.service: Main process exited, code=exited, status=255/EXCEPTION
Mär 08 19:00:41 x1-extreme systemd[3321]: plasma-plasmashell.service: Failed with result 'exit-code'.
Mär 08 19:00:41 x1-extreme systemd[3321]: plasma-plasmashell.service: Consumed 1.684s CPU time.
Mär 08 19:00:41 x1-extreme systemd[3321]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 2.
Mär 08 19:00:41 x1-extreme systemd[3321]: Stopped KDE Plasma Workspace.
Mär 08 19:00:41 x1-extreme systemd[3321]: plasma-plasmashell.service: Consumed 1.684s CPU time.
Mär 08 19:00:41 x1-extreme systemd[3321]: Starting KDE Plasma Workspace...
Mär 08 19:00:42 x1-extreme plasmashell[5092]: warning: queue 0x613ce51b6840 destroyed while proxies still attached:
Mär 08 19:00:42 x1-extreme plasmashell[5092]:   wl_registry@36 still attached
Mär 08 19:00:42 x1-extreme systemd[3321]: Started KDE Plasma Workspace.


As said, "[destroyed object]: error 7: importing the supplied dmabufs failed" indicates the the same issue
Comment 15 Zamundaaa 2024-03-08 18:19:15 UTC
Yeah, I'm afraid we can't do anything about that. Please report this to NVidia at https://forums.developer.nvidia.com/c/gpu-graphics/linux/148
Comment 16 Nicolas 2024-03-08 18:32:16 UTC
(In reply to Zamundaaa from comment #15)
> Yeah, I'm afraid we can't do anything about that. Please report this to
> NVidia at https://forums.developer.nvidia.com/c/gpu-graphics/linux/148

What exactly should one report there? Just this error message? Is it universally understandable?

Though I didnt try wayland often, I remember that it kind of worked before with kde 5..
Comment 17 John Salatas 2024-03-08 18:40:25 UTC
@Nicolas
> What exactly should one report there? Just this error message? Is it universally understandable?

Just describe your problem, any logs/error messages and also point them to this bug report. You need also to provide them the file that is generated if you run 

sudo nvidia-bug-report.sh

They will ask you if they need any further details.
Comment 18 Nicolas 2024-03-26 11:36:33 UTC
Some people have reported [1] that an upgrade of egl-wayland helped them, would it be possible to provide newer packages of egl-wayland on neon, instead of 1.1.9? Upstream is 1.1.13.


[1]https://github.com/NVIDIA/egl-wayland/issues/61
Comment 19 Nicolas 2024-03-26 15:23:13 UTC
manually upgrading to egl-wayland 1.13 fixed the problem for me