[GH-ISSUE #690] Barrier doesn't work if there's a full-screened/maximized Window #548

Open
opened 2026-05-05 06:39:38 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @n0toose on GitHub (May 24, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/690

Operating Systems

Server: Debian Sid [Desktop environment: GNOME]

Client: Gentoo Linux (amd64 17.1) [Desktop environment: i3]

Barrier Version

2.3.2

Steps to reproduce bug

  1. Maximize window in GNOME or go full screen in any window in i3.
  2. Moving the mouse between screens is now impossible.

Other info

  • When did the problem start to occur? See "Steps to reproduce bug"
  • Is there a way to work around it? No, unless if you choose to undo the actions described in 1
  • Does this bug prevent you from using Barrier entirely? No. (I find the bug a deal-breaker which renders Barrier inconvenient to use, however.)

Since the bug isn't always reproducible, in the case of i3, I was using the kitty terminal I was using the GNOME Terminal.

Originally created by @n0toose on GitHub (May 24, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/690 ### Operating Systems ### Server: Debian Sid [Desktop environment: GNOME] Client: Gentoo Linux (amd64 17.1) [Desktop environment: i3] ### Barrier Version ### 2.3.2 ### Steps to reproduce bug ### 1. Maximize window in GNOME **or** go full screen in any window in i3. 2. Moving the mouse between screens is now impossible. ### Other info ### * When did the problem start to occur? **See "Steps to reproduce bug"** * Is there a way to work around it? **No, unless if you choose to undo the actions described in *1*** * Does this bug prevent you from using Barrier entirely? **No. (I find the bug a deal-breaker which renders Barrier inconvenient to use, however.)** Since the bug isn't always reproducible, in the case of i3, I was using the [kitty terminal](https://sw.kovidgoyal.net/kitty/) I was using the [GNOME Terminal](https://wiki.gnome.org/Apps/Terminal).
gitea-mirror added the
bug
linux
labels 2026-05-05 06:39:38 -06:00
Author
Owner

@henningkayser-bayer commented on GitHub (Jul 1, 2020):

Same here: Server Ubuntu 18.04.4 LTS GNOME Client: Windows 10.0.17763.1217 64bit

<!-- gh-comment-id:652488615 --> @henningkayser-bayer commented on GitHub (Jul 1, 2020): Same here: Server Ubuntu 18.04.4 LTS GNOME Client: Windows 10.0.17763.1217 64bit
Author
Owner

@github-actions[bot] commented on GitHub (Sep 21, 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:695867508 --> @github-actions[bot] commented on GitHub (Sep 21, 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:757535634 --> @p12tic commented on GitHub (Jan 10, 2021): Let's not close valid bug reports.
Author
Owner

@n0toose commented on GitHub (Jan 11, 2021):

For the record, my setup has changed since I made the issue report. Therefore, I won't be able to help any further by reproducing the issue.

<!-- gh-comment-id:757965453 --> @n0toose commented on GitHub (Jan 11, 2021): For the record, my setup has changed since I made the issue report. Therefore, I won't be able to help any further by reproducing the issue.
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#548
No description provided.