Ignore-Rules Textbox not responsive in Opensuse-Tumbleweed

1

I am using Opensuse-Tumbleweed.
Installed successfully.
Syncing proper.
Only issue is that Ignore-Rules text box does not accept keyboard input.
It only accept cut-paste (ctrl-c, ctrl-v)

It worked fine around 6 months back when fc36 version was installed. It started giving issues, and I moved to opensuse-leap. It is perfect there.
Again i checked with tumbleweed yesterday (this time fc39) and it behaved as I stated.

I even changed to fc41, (via pointed the repo to fedora/41), without any change.
All versions from fc38 to fc41 are behaving similarly.

Here is installation trail:

unning transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : insync-3.9.4.60020-fc39.x86_64 1/1
Running scriptlet: insync-3.9.4.60020-fc39.x86_64 1/1
Insync installation has finished. You may now start it.\n
fs.inotify.max_user_watches = 1048576

Installed:
insync-3.9.4.60020-fc39.x86_64

Complete!

2

That is interesting, my apologies for the trouble!

Can you let me know if this issue persists on 3.9.5? Try our fc41 builds: New Insync Version: 3.9.5

3

Thanks for quick takeup. This is indeed very interesting.
The issue still persist.
(removed the previous 3.9.4 version, and all traces from linux system, and installed 3.9.5 fc41)
even tried fc39, without any help.
Just to mention, non-character keys (cursor, bkspace, enter, pgup/dn, delete are working). Only typing is not working and even no cursor movement when press a,b,c etc.
I changed the keyboard also from US to UK to US international, etc.
Also, checked after reinstalling Opensuse TW, with no help.

1 Like
4

I’ll have our engineers test this on their end and get back to you as soon as I have more information at hand.

Thank you!

5

Hi,
One more piece of context I have discovered.
The issue is further narrowed-down, and now in X11 (usually xfce in opensuse-tw) the issue persist while in wayland (usually KDE in opensuse-tw), the issue is not there.

6

Thank you for sharing this! I will send it to our Linux Team for testing and replication, so that we can determine the fixes needed for it.