Bug 450710 - Some functionality becomes unusable after running `vulkaninfo`
Summary: Some functionality becomes unusable after running `vulkaninfo`
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.24.1
Platform: Arch Linux All
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2022-02-22 16:40 UTC by Jürgen Richtsfeld
Modified: 2022-03-02 18:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jürgen Richtsfeld 2022-02-22 16:40:15 UTC
SUMMARY
A few seconds after login, things stop working (this means, they work  ~1 minute after login), to be precise:
* hitting ctrl-alt-del doesn't show the fullscreen logout window anymore (nothing happens) - therefore I currently shutdown/reboot by entering those commands to konsole)
* electron apps don't start anymore (at least visualstudio-code) (again, this works the first few seconds after login
* eglinfo get's stuck at connecting to /tmp/.X11-unix/X1 (it seems X0 works) - therefore it produces quite some output



STEPS TO REPRODUCE
1. login to plasma-wayland session
2. wait some time (actually, my session is restored, basically firefox and thunderbird get loaded)
3. e.g. open 'Info Center' / Graphics Section - except wayland no single entry gives output (vulkaninfo also only returns errors: 
---
$ vulkaninfo
ERROR: [Loader Message] Code 0 : loader_scanned_icd_add: Driver /usr/lib/libvulkan_radeon.so supports Vulkan 1.2, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
ERROR: [Loader Message] Code 0 : loader_scanned_icd_add: Driver /usr/lib/libvulkan_intel.so supports Vulkan 1.2, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0

not sure if this is related.

OBSERVED RESULT
until the update of kde 5.24.0 the whole system worked like a charm, already on wayland (I'm there for quite a while). Btw, all those problems don't exist on a very similar setup machine (same arch linux) where I still have to use xorg.


SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.15.8-arch1-1 (64-bit) (also happens with some 5.16.x kernels)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8705G CPU @ 3.10GHz
Memory: 15,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630

At the beginning I just noticed the issues after the computer fell asleep, therefore I commented on #450069 - but I tried to find if some processes got stuck or crashed, so I discovered that this isn't related to sleep/suspend.
Comment 1 Jürgen Richtsfeld 2022-02-22 16:55:54 UTC
just rebooted once more trying out a few things - it seem it doesn't _stop working on it's own_ but it seems I can trigger the problem by just invoking 

$ vulkaninfo
which gives me

ERROR: [Loader Message] Code 0 : loader_scanned_icd_add: Driver /usr/lib/libvulkan_radeon.so supports Vulkan 1.2, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
ERROR: [Loader Message] Code 0 : loader_scanned_icd_add: Driver /usr/lib/libvulkan_intel.so supports Vulkan 1.2, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0

ERROR at /build/vulkan-tools/src/Vulkan-Tools-1.2.203/vulkaninfo/vulkaninfo.h:1432:vkGetPhysicalDeviceSurfaceSupportKHR failed with ERROR_OUT_OF_HOST_MEMORY

on the first run.

further executions don't show the last line but get stuck after the the line starting with MESA-INTEL.
Comment 2 Nate Graham 2022-02-22 18:06:13 UTC
Well that's odd
Comment 3 Jürgen Richtsfeld 2022-02-23 16:12:00 UTC
after a reboot, login and launching visual studio code via krunner journalctl shows:

eb 23 17:08:05 juergen krunner[2632]: QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
Feb 23 17:08:05 juergen krunner[2632]: kf.sonnet.core: No language dictionaries for the language: "en_US" trying to load en_US as default
Feb 23 17:08:05 juergen krunner[2632]: kf.sonnet.core: No language dictionaries for the language: "en_US"
Feb 23 17:08:05 juergen krunner[2632]: kf.plasma.quick: Couldn't create KWindowShadow for View(0x7fff8c6c3330)
Feb 23 17:08:05 juergen krunner[2632]: kf.plasma.quick: Couldn't create KWindowShadow for View(0x7fff8c6c3330)
Feb 23 17:08:05 juergen krunner[2632]: kf.plasma.quick: Couldn't create KWindowShadow for View(0x7fff8c6c3330)
Feb 23 17:08:05 juergen krunner[2632]: kf.plasma.quick: Couldn't create KWindowShadow for View(0x7fff8c6c3330)
Feb 23 17:08:05 juergen krunner[2632]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Feb 23 17:08:09 juergen systemd[830]: Started Visual Studio Code - Text Editor.
Feb 23 17:08:12 juergen kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
Feb 23 17:08:12 juergen kernel: [drm] UVD and UVD ENC initialized successfully.
Feb 23 17:08:12 juergen kernel: [drm] VCE initialized successfully.
Feb 23 17:08:12 juergen kdeinit5[885]: kdeinit5: Fatal IO error: client killed
Feb 23 17:08:12 juergen kdeinit5[885]: kdeinit5: sending SIGHUP to children.
Feb 23 17:08:12 juergen kdeinit5[885]: kdeinit5: sending SIGTERM to children.
Feb 23 17:08:12 juergen kdeinit5[885]: kdeinit5: Exit.
Comment 4 Jürgen Richtsfeld 2022-02-23 19:40:46 UTC
I tried a few things, first: everything works in the X11 session (vulkaninfo gives results, visual studio seems to work as expected).

when launching visual studio code in the wayland session with some logging, I get:

❯ code --verbose --log=TRACE --enable-features=UseOzonePlatform --ozone-platform=wayland
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'ozone-platform' is not in the list of known options, but still passed to Electron/Chromium.
[23399:0223/203533.778005:WARNING:wayland_drm.cc(68)] Failed to get drm magic
[main 2022-02-23T19:35:33.925Z] [File Watcher (node.js)] Request to start watching: /home/juergen/.config/Code/User (excludes: <none>),/home/juergen/.config/Code/User/settings.json (excludes: <none>)
[main 2022-02-23T19:35:33.937Z] Starting VS Code
[main 2022-02-23T19:35:33.937Z] from: /opt/visual-studio-code/resources/app

<striped details>

[main 2022-02-23T19:35:33.939Z] Resolving machine identifier...
[main 2022-02-23T19:35:33.939Z] Resolved machine identifier: 8c310ebc08583c32225be885ff139f2b27028a65b67b1a43ab61098f4e36d068
[main 2022-02-23T19:35:33.940Z] Main->SharedProcess#connect
[main 2022-02-23T19:35:33.944Z] [File Watcher (node.js)] Started watching: '/home/juergen/.config/Code/User'
[main 2022-02-23T19:35:33.944Z] [File Watcher (node.js)] Started watching: '/home/juergen/.config/Code/User/settings.json'
[main 2022-02-23T19:35:33.947Z] StorageMainService: creating global storage
[main 2022-02-23T19:35:33.951Z] lifecycle (main): phase changed (value: 2)
[main 2022-02-23T19:35:33.952Z] windowsManager#open
[main 2022-02-23T19:35:33.952Z] windowsManager#open pathsToOpen [
  {
    backupPath: '/home/juergen/.config/Code/Backups/1645644612337',
    remoteAuthority: undefined
  }
]
[main 2022-02-23T19:35:33.952Z] windowsManager#doOpenEmpty {
  restore: true,
  remoteAuthority: undefined,
  filesToOpen: undefined,
  forceNewWindow: true
}
[main 2022-02-23T19:35:33.953Z] IPC Object URL: Registered new channel vscode:bce02355-d662-4628-b3c5-63d605e6267b.
[main 2022-02-23T19:35:33.953Z] window#validateWindowState: validating window state on 1 display(s) { mode: 0, x: 448, y: 188, width: 1024, height: 769 }
[main 2022-02-23T19:35:33.953Z] window#validateWindowState: 1 monitor working area { x: 0, y: 0, width: 1920, height: 1080 }
[main 2022-02-23T19:35:33.953Z] window#ctor: using window state { mode: 0, x: 448, y: 188, width: 1024, height: 769 }
[23399:0223/203533.954101:WARNING:wayland_surface.cc(63)] Server doesn't support zwp_linux_explicit_synchronization_v1.
[23399:0223/203533.954483:ERROR:cursor_loader.cc(107)] Failed to load a platform cursor of type kNull
[main 2022-02-23T19:35:33.988Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 1, emptyToOpen: 0)
[main 2022-02-23T19:35:33.988Z] lifecycle (main): phase changed (value: 3)
[main 2022-02-23T19:35:33.988Z] update#setState idle
[main 2022-02-23T19:35:33.988Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[main 2022-02-23T19:35:34.024Z] ExtensionHostStarterWorker created
[main 2022-02-23T19:35:34.094Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
X connection to :1 broken (explicit kill or server shutdown).
[23433:0100/000000.773120:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is egl
Comment 5 David Edmundson 2022-02-23 23:34:19 UTC
This would not be a plasma issue. Please report to mesa
Comment 6 Jürgen Richtsfeld 2022-03-02 18:33:41 UTC
reported at mesa: https://gitlab.freedesktop.org/mesa/mesa/-/issues/6086