microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.34k stars 814 forks source link

Issues with QT Paint Device and the Platform plugin. #2429

Closed weirdbeardgame closed 3 years ago

weirdbeardgame commented 7 years ago

Window's Version: 16257 OS: Open Suse

When I try to use QT apps I sometimes get Errors related to the QT paint device. As well a subsequently related error is error can't load Platform Plugin. Could not find any platform plugin - This occurs with kwin_wayland, but occurs with other QT apps as well

The Strace: https://gist.github.com/kenshen112/86bf48fa26ca7aa8028b1e3d4bc7db39#file-kwin-strace

therealkenc commented 7 years ago

Link a gist. But reading the tea leaves above, KGlobalAccel is probably looking for a raw keyboard device that doesn't exist (guess). EWONTWORK. Way forward would be to turn it off, if there is such a thing in KDE.

weirdbeardgame commented 7 years ago

@therealkenc that was because I hadn't installed plasma session5. I have updated the strace

therealkenc commented 7 years ago

That weird. The strace isn't showing path names:

[pid    38] open(0x1eff718, O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid    38] stat(0x1eff648, {...})      = 0

Haven't seen that before.

Often those open() / access() / stat() fails are by design; files get looked up, don't exist, and then the program looks for another (think $PATH walking for example). The ones closer to the bottom, like line 2300 onward (pid 38) are probably fatal. I just can't tell you what it can't find because the path is missing. There is also an ENOSYS in there, but that isn't your problem.

I'd be mildly (but only very mildly) curious if this scenario works in a remote X session with Real SUSE, given the nature of KGlobalAccel. Path forward would be to post repro steps and maybe someone will bite.

weirdbeardgame commented 7 years ago

Steps to reproduce.

  1. export XDG_RUNTIME_DIR to either your own temp dir or system dir.
  2. sudo zypper install kwin
  3. sudo zypper install kwayland
  4. sudo zypper install plasma5-session.
  5. sudo zypper install libqt5-qtwayland
  6. run kwin_wayland --drm --windowed
therealkenc commented 7 years ago

run kwin_wayland --drm --windowed

That won't fly because there is no DRM in WSL. You could try --xwayland --x11-display=localhost:0 with VcXsrv and see if that gets you further. You'll probably also have to have your dbus session ducks in line.

weirdbeardgame commented 7 years ago

@therealkenc https://www.reddit.com/r/bashonubuntuonwindows/comments/6ndity/z/dk96aam?context=3&sort=confidence

I made a post awhile back, that also doesn't work, xwayland won't start

therealkenc commented 7 years ago
strace -ff kwin_wayland --windowed --xwayland --x11-display=localhost:0 2> kwin_wayland.strace

[Assuming that's the right way to start kwin_wayland to run in a remote X session.]

therealkenc commented 7 years ago
'libQt5WaylandCompositor5' not found in package names. Trying capabilities.
No provider of 'libQt5WaylandCompositor5' found.
Resolving package dependencies...

Problem: plasma5-session-5.8.6-7.1.noarch requires plasma5-workspace >= 5.8.6, but this requirement cannot be provided
  uninstallable providers: plasma5-workspace-5.8.6-8.1.x86_64[oss_update]
 Solution 1: Following actions will be done:
  do not install plasma5-session-5.8.6-7.1.noarch
  do not install kwin-4.11.22-3.24.x86_64
 Solution 2: deinstallation of krb5-mini-1.12.5-5.2.x86_64
 Solution 3: break plasma5-session-5.8.6-7.1.noarch by ignoring some of its dependencies

...which is where I stopped.

weirdbeardgame commented 7 years ago

https://gist.github.com/kenshen112/6d616618d1edf7cc64b6d75d3fe2f96e - xwayland strace

therealkenc commented 3 years ago

run kwin_wayland --drm --windowed

There is no DRM on WSL1 (or strictly speaking, WSL2 either). This is /dupe #882.

ghost commented 3 years ago

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!