[GH-ISSUE #651] dragging objects cause linux client to freeze #518

Closed
opened 2026-05-05 06:34:56 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @steverweber on GitHub (May 4, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/651

Operating Systems

Server: windows 7
Client: Linux ubuntu 20.04 KDE

Barrier Version

2.3.2

Steps to reproduce bug

Client side:

  1. Start a drag-drop and move file or a text block around for ~1 to ~4 seconds.
  2. app seems to lockup for ~10seconds
  3. error log:
# note: server advanced option is set to check client every: 9000ms
[2020-05-04T10:02:29] DEBUG1: recv mouse down id=1
[2020-05-04T10:02:40] DEBUG1: recv mouse up id=1
[2020-05-04T10:02:40] DEBUG1: ignoring X error: 3
[2020-05-04T10:02:40] DEBUG1: flagging X error: 3 - BadWindow
# Another example with check client every: 9000ms
[2020-05-04T10:09:02] DEBUG1: recv mouse down id=1
[2020-05-04T10:09:14] DEBUG1: recv mouse up id=1
[2020-05-04T10:09:14] DEBUG1: flagging X error: 3 - BadWindow
# debug level verbose
[2020-05-04T10:19:50] DEBUG2: wrote 4 bytes
[2020-05-04T10:19:50] DEBUG2: can't read property 610 on window 0x03a03c34
[2020-05-04T10:20:00] DEBUG2: msg from server: DMMV
[2020-05-04T10:20:00] DEBUG2: readf(%2i%2i)
[2020-05-04T10:20:00] DEBUG2: readf: read 2 byte integer: 1874 (0x752)
[2020-05-04T10:20:00] DEBUG2: readf: read 2 byte integer: 333 (0x14d)
[2020-05-04T10:20:00] DEBUG2: recv mouse move 1874,333
[2020-05-04T10:20:00] DEBUG2: writef(CNOP)

Other info

  • changing server advanced option check client every: to 1000ms make the freeze shorter. I assume the server notices something seems off and causes the session to "reinit"
  • set server advanced option to false for : drag drop file does not help.
Originally created by @steverweber on GitHub (May 4, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/651 ### Operating Systems ### Server: windows 7 Client: Linux ubuntu 20.04 KDE ### Barrier Version ### 2.3.2 ### Steps to reproduce bug ### Client side: 1. Start a drag-drop and move file or a text block around for ~1 to ~4 seconds. 2. app seems to lockup for ~10seconds 2. error log: ``` # note: server advanced option is set to check client every: 9000ms [2020-05-04T10:02:29] DEBUG1: recv mouse down id=1 [2020-05-04T10:02:40] DEBUG1: recv mouse up id=1 [2020-05-04T10:02:40] DEBUG1: ignoring X error: 3 [2020-05-04T10:02:40] DEBUG1: flagging X error: 3 - BadWindow # Another example with check client every: 9000ms [2020-05-04T10:09:02] DEBUG1: recv mouse down id=1 [2020-05-04T10:09:14] DEBUG1: recv mouse up id=1 [2020-05-04T10:09:14] DEBUG1: flagging X error: 3 - BadWindow # debug level verbose [2020-05-04T10:19:50] DEBUG2: wrote 4 bytes [2020-05-04T10:19:50] DEBUG2: can't read property 610 on window 0x03a03c34 [2020-05-04T10:20:00] DEBUG2: msg from server: DMMV [2020-05-04T10:20:00] DEBUG2: readf(%2i%2i) [2020-05-04T10:20:00] DEBUG2: readf: read 2 byte integer: 1874 (0x752) [2020-05-04T10:20:00] DEBUG2: readf: read 2 byte integer: 333 (0x14d) [2020-05-04T10:20:00] DEBUG2: recv mouse move 1874,333 [2020-05-04T10:20:00] DEBUG2: writef(CNOP) ``` ### Other info ### - changing server advanced option check client every: to 1000ms make the freeze shorter. I assume the server notices something seems off and causes the session to "reinit" - set server advanced option to false for : drag drop file does not help.
Author
Owner

@steverweber commented on GitHub (May 4, 2020):

perhaps related to:
a324957e2d

<!-- gh-comment-id:623510175 --> @steverweber commented on GitHub (May 4, 2020): perhaps related to: https://github.com/symless/synergy-core/commit/a324957e2da7822e08e754eea62279d924e97dad
Author
Owner

@github-actions[bot] commented on GitHub (Sep 23, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

<!-- gh-comment-id:697070214 --> @github-actions[bot] commented on GitHub (Sep 23, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.
Author
Owner

@p12tic commented on GitHub (Jan 10, 2021):

Let's not close valid bug reports.

<!-- gh-comment-id:757539363 --> @p12tic commented on GitHub (Jan 10, 2021): Let's not close valid bug reports.
Author
Owner

@p12tic commented on GitHub (Jan 10, 2021):

After further review I agree that this is likely related to an existing problem (forgot issue number) that has been fixed in 2.3.3. So I'm closing this issue.

@steverweber If you see this bug on Barrier 2.3.3 please reopen this issue again. Thanks!

<!-- gh-comment-id:757539663 --> @p12tic commented on GitHub (Jan 10, 2021): After further review I agree that this is likely related to an existing problem (forgot issue number) that has been fixed in 2.3.3. So I'm closing this issue. @steverweber If you see this bug on Barrier 2.3.3 please reopen this issue again. Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#518
No description provided.