Copy Paste functions suddenly stop working

[PeterBorisenko]

Steps to reproduce

1. Actively use group chat, switch languages (by Option+Space keys), use "```" formatting
2. Copy paste something from Eclipse

Expected behaviour

Works fine from launch till closing

Actual behaviour

After some use Ctrl+V stopped working, As well a context menu look like following

Operating system

Ubuntu 22.04

Version of Telegram Desktop

Telegram v4.4.1

Installation source

Snap

Logs

No response

[ilya-fedin]

Is there a way to reproduce without Eclipse? I'm not an Eclipse user.

[PeterBorisenko]

As for now I haven't noticed any other ways.

[ilya-fedin]

Are you sure Telegram is at fault? Couldn't this be compositor or XWayland?

[PeterBorisenko]

Is there a way to check it? I am able to paste it anywhere else but Telegram.

[ilya-fedin]

Is there a way to check it?

Well, first check whether Eclipse is running via native Wayland or via XWayland, then check whether Telegram is running via native Wayland or XWayland (this is specified in the session list from the Privacy & Security section). It's not a rare situation when compositors have bugs in the clipboard synchronization between native Wayland and XWayland applications.

[PeterBorisenko]

From Eclipse info:

XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.F4D7R1
XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg
XDG_CURRENT_DESKTOP=ubuntu:GNOME
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
XDG_MENU_PREFIX=gnome-
XDG_RUNTIME_DIR=/run/user/1000
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=ubuntu
XDG_SESSION_TYPE=wayland
XMODIFIERS=@im=ibus
_=/usr/bin/gnome-session

From Telegram session:

It is not clear for me but seems both run on Wayland.

[ilya-fedin]

From Eclipse info:

It's just your environment variables, you can also get them with env command in Terminal, this has nothing to do with what Eclipse uses. You can try to check whether xeyes or xwininfo detect Eclipse window.

[github-actions[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.