search

microsoft / wslg

Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
MIT License
10.1k stars 304 forks source link

Unable to copy content from Windows 10 to Google Chrome, Idea, or Gedit #1066

Closed gf9276 closed 1 year ago

gf9276 commented 1 year ago

Windows build number:

19045.2965

Your Distribution version:

22.04

Your WSL versions:

WSL version: 1.2.5.0
Kernel version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131-1002-220531-1700. rs one core base 2 hyp
Windows version: 10.0.19045.2965

Steps to reproduce:

  1. Copy a large amount of text (over 65536 characters) at once in Windows 10
  2. Paste into Google Chrome, Idea, or Gedit
  3. After this, you will not be able to paste anything from Windows 10 into wslg applications

WSL logs:

pulseaudio.log

W: [pulseaudio] authkey.c: Failed to open cookie file '/home/wslg/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key '/home/wslg/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to open cookie file '/home/wslg/.pulse-cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key '/home/wslg/.pulse-cookie': No such file or directory
E: [pulseaudio] module-console-kit.c: GetSessionsForUnixUser() call failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
E: [pulseaudio] module.c: Failed to load module "module-console-kit" (argument: ""): initialization failed.
E: [rdp-sink] module-rdp-sink.c: RDP Sink - Trying to connect to /mnt/wslg/PulseAudioRDPSink
E: [rdp-sink] module-rdp-sink.c: Connected failed
E: [rdp-sink] module-rdp-sink.c: RDP Sink - Trying to connect to /mnt/wslg/PulseAudioRDPSink
E: [rdp-sink] module-rdp-sink.c: RDP Sink - Connected to fd 12

weston.log

RDP clipboard_data_source_send new (0x7fa268001330:failed:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:28:49.857] read fd:96 0 (available 65536, mask 0x4)
[20:28:49.857] non-incr transfer read complete
[20:29:01.840]

RDP clipboard_data_source_send new (0x7fa268000bf0:published:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:01.841] xfixes selection notify event: owner 2097153
[20:29:01.841] our window, skipping
[20:29:01.841] selection request, CLIPBOARD, target UTF8_STRING, property FCITX_X11_SEL_CLIPBOARD
[20:29:01.841]

RDP clipboard_data_source_send new (0x7fa268000bf0:failed:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:01.841] read fd:96 0 (available 65536, mask 0x4)
[20:29:01.841] non-incr transfer read complete
[20:29:01.841]

RDP clipboard_data_source_send new (0x7fa268001330:published:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:01.841] xfixes selection notify event: owner 2097153
[20:29:01.841] our window, skipping
[20:29:01.841] selection request, CLIPBOARD, target UTF8_STRING, property FCITX_X11_SEL_CLIPBOARD
[20:29:01.841]

RDP clipboard_data_source_send new (0x7fa268001330:failed:fd 106) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:01.841] read fd:105 0 (available 65536, mask 0x4)
[20:29:01.841] non-incr transfer read complete
[20:29:25.346]

RDP clipboard_data_source_send new (0x7fa268000bf0:published:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:25.346] xfixes selection notify event: owner 2097153
[20:29:25.346] our window, skipping
[20:29:25.346] selection request, CLIPBOARD, target UTF8_STRING, property FCITX_X11_SEL_CLIPBOARD
[20:29:25.346]

RDP clipboard_data_source_send new (0x7fa268000bf0:failed:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:25.346] read fd:96 0 (available 65536, mask 0x4)
[20:29:25.346] non-incr transfer read complete
[20:29:30.754]

RDP clipboard_data_source_send new (0x7fa268001330:published:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:30.754] xfixes selection notify event: owner 2097153
[20:29:30.754] our window, skipping
[20:29:30.754] selection request, CLIPBOARD, target UTF8_STRING, property FCITX_X11_SEL_CLIPBOARD
[20:29:30.754]

RDP clipboard_data_source_send new (0x7fa268001330:failed:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

stderr.log

[19:47:19.942] <5>WSLGd: FontFolder:14: FontMonitor: start monitoring /mnt/wslg/distro/usr/share/fonts
[19:47:19.942] <5>WSLGd: FontFolder:14: FontMonitor: start monitoring /mnt/wslg/distro/usr/share/fonts/X11
[19:47:19.943] <5>WSLGd: FontFolder:14: FontMonitor: start monitoring /mnt/wslg/distro/usr/share/fonts/X11/encodings
[19:47:19.944] <5>WSLGd: FontFolder:14: FontMonitor: start monitoring /mnt/wslg/distro/usr/share/fonts/X11/encodings/large
[19:47:19.944] <5>WSLGd: FontFolder:14: FontMonitor: start monitoring /mnt/wslg/distro/usr/share/fonts/X11/util
[19:47:19.944] <5>WSLGd: FontFolder:14: FontMonitor: start monitoring /mnt/wslg/distro/usr/share/fonts/X11/misc
/usr/share/icons/hicolor/scalable/apps/com.gexperts.Tilix.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
/usr/share/icons/hicolor/scalable/apps/org.gnome.Nautilus.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
libpng warning: iCCP: known incorrect sRGB profile
/usr/share/icons/hicolor/scalable/apps/org.gnome.gedit.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
glamor: 'wl_drm' not supported
Missing Wayland requirements for glamor GBM backend
Failed to initialize glamor, falling back to sw
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error:   Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server
[19:47:22.944] <5>WSLGd: ExecuteShellCommand:85: FontMonitor: pid:364 exited with success, /usr/bin/xset +fp /mnt/wslg/distro/usr/share/fonts/X11/misc

[19:47:22.945] <5>WSLGd: ExecuteShellCommand:85: FontMonitor: pid:570 exited with success, /usr/bin/xset fp rehash
[19:47:22.945] <5>WSLGd: FontMonitorThread:228: FontMonitor: monitoring thread started.
[19:47:22.946] <5>WSLGd: DumpMonitorFolders:125: FontMonitor: monitoring /mnt/wslg/distro/usr/share/fonts, and it is *not* added to X11 font path
[19:47:22.946] <5>WSLGd: DumpMonitorFolders:125: FontMonitor: monitoring /mnt/wslg/distro/usr/share/fonts/X11, and it is *not* added to X11 font path
[19:47:22.946] <5>WSLGd: DumpMonitorFolders:125: FontMonitor: monitoring /mnt/wslg/distro/usr/share/fonts/X11/encodings, and it is *not* added to X11 font path
[19:47:22.946] <5>WSLGd: DumpMonitorFolders:125: FontMonitor: monitoring /mnt/wslg/distro/usr/share/fonts/X11/encodings/large, and it is *not* added to X11 font path
[19:47:22.946] <5>WSLGd: DumpMonitorFolders:125: FontMonitor: monitoring /mnt/wslg/distro/usr/share/fonts/X11/misc, and it is added to X11 font path
[19:47:22.946] <5>WSLGd: DumpMonitorFolders:125: FontMonitor: monitoring /mnt/wslg/distro/usr/share/fonts/X11/util, and it is *not* added to X11 font path
dbus[574]: Unknown username "pulse" in message bus configuration file
/usr/share/icons/hicolor/scalable/apps/com.gexperts.Tilix.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
/usr/share/icons/hicolor/scalable/apps/org.gnome.Nautilus.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
libpng warning: iCCP: known incorrect sRGB profile
/usr/share/icons/hicolor/scalable/apps/org.gnome.gedit.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 569, clipping.
>                   X11 cannot support keycodes above 255.
> Internal error:   Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error:   Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server
could not load cursor 'grabbing'
could not load cursor 'dnd-move'
could not load cursor 'dnd-copy'
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error:   Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server

WSL dumps:

No response

Expected behavior:

I hope to copy and paste between Windows and wslg normally. Now it seems like he's stuck on the RDP transmission

Actual behavior:

When copying a large amount of text from Windows at once to wslg, wslg will not be able to paste any content, and after that, it will not be possible to paste any length of content from Windows into wslg.

gf9276 commented 1 year ago

I have looked at many issues records and it seems that this issue has existed for a long time, even dating back to 2020. I want to know if anyone is dealing with this issue?

gf9276 commented 1 year ago

So no one saw or noticed this problem? As long as you copy thousands of characters at once, wslg cannot copy anything from Windows.

gf9276 commented 1 year ago

anyone help?

Kermit commented 1 year ago

I have this problem since 2020 and I just use workaround - save file with copied content on Windows side and open it with anything you want on WSL side. But I'm pretty sure you are doing the same now :)

hideyukn88 commented 1 year ago

@gf9276, thanks for reporting the issue, I believe this is the issue reported at https://github.com/microsoft/wslg/issues/743, thanks!

gf9276 commented 1 year ago

@gf9276, thanks for reporting the issue, I believe this is the issue reported at #743, thanks!

@hideyukn88, I just tried and the problem still exists. This problem has existed for at least two years or more, so why hasn't it been resolved yet?

thiagojramos commented 11 months ago

@gf9276, thanks for reporting the issue, I believe this is the issue reported at #743, thanks!

@hideyukn88, I just tried and the problem still exists. This problem has existed for at least two years or more, so why hasn't it been resolved yet?

It's because this place is abandoned.

Masamune3210 commented 11 months ago

No it's not? Just because this issue isn't getting obvious and constant work reported in this exact issue report, you claim its abandoned?

hideyukn88 commented 11 months ago

@gf9276, thanks for inquiry. The reason of the delay for that issue, #743, is inherited from upstream branch, which normally doesn't make specific fix at local downstream branch, unless it's coordinated with its upstream maintainer. Let us understand what's going on, and will update here or at #743, thanks!